Utility crash via undersized extraction buffers
Published May 19, 2023 · Updated Jan 21, 2025
Heap buffer overflow in tiffcrop in LibTIFF 4.4.0 allows local users to crash the utility by processing a crafted TIFF file. extractContigSamples32bits reads beyond an exactly sized heap buffer because callers allocate no padding for its 32-bit extraction. Execution requires invoking the command-line tool on attacker-controlled input; published evidence demonstrates a crash, not code execution.
Summary
What happened
Heap buffer overflow in tiffcrop in LibTIFF 4.4.0 allows local users to crash the utility by processing a crafted TIFF file. extractContigSamples32bits reads beyond an exactly sized heap buffer because callers allocate no padding for its 32-bit extraction. Execution requires invoking the command-line tool on attacker-controlled input; published evidence demonstrates a crash, not code execution.
The record
- CVE
- CVE-2023-30775
- Published
- May 19, 2023
- Updated
- Jan 21, 2025
- Vendor
- LibTIFF Project
- Product
- LibTIFF
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2023CVE publishedPublication date reported by the CVE source.
- Jan 21, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.0
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- tiffcrop heap-buffer-overflow proof of conceptproof 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