Service interruption via wrong segment buffer size
Published Jan 23, 2023 · Updated Apr 3, 2025
Heap-based buffer overflow in LibTIFF tiffcrop through 4.5.0 allows local users to crash the utility via a crafted TIFF image. processCropSelections reads each segment's size from seg_buffs[0] rather than seg_buffs[i], so required reallocation can be skipped before _TIFFmemset writes the crop buffer. Execution requires a user to run tiffcrop on the malicious file; the demonstrated consequence is a segmentation fault and service interruption.
Summary
What happened
Heap-based buffer overflow in LibTIFF tiffcrop through 4.5.0 allows local users to crash the utility via a crafted TIFF image. processCropSelections reads each segment's size from seg_buffs[0] rather than seg_buffs[i], so required reallocation can be skipped before _TIFFmemset writes the crop buffer. Execution requires a user to run tiffcrop on the malicious file; the demonstrated consequence is a segmentation fault and service interruption.
The record
- CVE
- CVE-2022-48281
- Published
- Jan 23, 2023
- Updated
- Apr 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2023CVE publishedPublication date reported by the CVE source.
- Apr 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- LibTIFF tiffcrop issue 488 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