Local service interruption via crafted TIFF file
Published Mar 22, 2023 · Updated Nov 22, 2024
Buffer overflow in TinyTIFF 3.0.0.0 allows local users to interrupt a consuming application by processing a crafted TIFF file. The public record identifies tinytiffreader.c in the File Handler but does not disclose the specific parsing operation or missing bounds check. User interaction is required, and the reported impact is limited to an application crash without data disclosure or modification.
Summary
What happened
Buffer overflow in TinyTIFF 3.0.0.0 allows local users to interrupt a consuming application by processing a crafted TIFF file. The public record identifies tinytiffreader.c in the File Handler but does not disclose the specific parsing operation or missing bounds check. User interaction is required, and the reported impact is limited to an application crash without data disclosure or modification.
The record
- CVE
- CVE-2023-1560
- Published
- Mar 22, 2023
- Updated
- Nov 22, 2024
- Vendor
- Jan W. Krieger
- Product
- TinyTIFF
- Classifications
- CWE-120, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 22, 2023CVE publishedPublication date reported by the CVE source.
- Nov 22, 2024Record 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=3.0.0.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.
Weakness, pattern, technique
Public exploit references
- id8 crafted TIFF proof of conceptproof of concept · unverified
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