Local tiffcrop crash via unreleased input buffer
Published Oct 4, 2023 · Updated Jun 23, 2026
Memory leak in tiffcrop on Red Hat Enterprise Linux 8 and 9 allows local users to crash the utility with a crafted TIFF file. The loadImage function allocates an input buffer through limitMalloc, and a failure path leaves that allocation unreleased after processing malformed image data. Processing the crafted file is required; the reported consequence is memory exhaustion that crashes tiffcrop, with no confidentiality or integrity impact.
Summary
What happened
Memory leak in tiffcrop on Red Hat Enterprise Linux 8 and 9 allows local users to crash the utility with a crafted TIFF file. The loadImage function allocates an input buffer through limitMalloc, and a failure path leaves that allocation unreleased after processing malformed image data. Processing the crafted file is required; the reported consequence is memory exhaustion that crashes tiffcrop, with no confidentiality or integrity impact.
The record
- CVE
- CVE-2023-3576
- Published
- Oct 4, 2023
- Updated
- Jun 23, 2026
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-119, CWE-401, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 4, 2023CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Merge request 475 proof-of-concept TIFFproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo