Service crash via FarmHash heap over-read
Published Jan 23, 2025 · Updated Feb 5, 2025
Heap-buffer overflow in OpenImageIO 3.1.0.0dev allows attackers to crash image-processing tools through a crafted image file. Fetch64 reads eight bytes past the heap allocation while ImageInput::open hashes crafted input during image-plugin selection. The published proof of concept requires iconvert or oiiotool to process the file and demonstrates an AddressSanitizer-detected abort, not code execution.
Summary
What happened
Heap-buffer overflow in OpenImageIO 3.1.0.0dev allows attackers to crash image-processing tools through a crafted image file. Fetch64 reads eight bytes past the heap allocation while ImageInput::open hashes crafted input during image-plugin selection. The published proof of concept requires iconvert or oiiotool to process the file and demonstrates an AddressSanitizer-detected abort, not code execution.
The record
- CVE
- CVE-2024-55192
- Published
- Jan 23, 2025
- Updated
- Feb 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2025CVE publishedPublication date reported by the CVE source.
- Feb 5, 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.
Weakness, pattern, technique
Public exploit references
- poc1iconvertproof of concept · demonstrated
- poc1oiioproof 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