Process crash via unchecked ICC tag bounds
Published Jan 23, 2025 · Updated Jan 24, 2025
Denial of service in OpenImageIO 3.1.0.0dev allows remote attackers to crash iconvert by supplying a crafted image file. The ICC decoder trusts corrupted tag offsets or lengths and compares bytes outside the profile allocation, triggering an invalid read. Processing a crafted JPEG, TIFF, or another ICC-bearing image requires user interaction and terminates the affected process.
Summary
What happened
Denial of service in OpenImageIO 3.1.0.0dev allows remote attackers to crash iconvert by supplying a crafted image file. The ICC decoder trusts corrupted tag offsets or lengths and compares bytes outside the profile allocation, triggering an invalid read. Processing a crafted JPEG, TIFF, or another ICC-bearing image requires user interaction and terminates the affected process.
The record
- CVE
- CVE-2024-55193
- Published
- Jan 23, 2025
- Updated
- Jan 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2025CVE publishedPublication date reported by the CVE source.
- Jan 24, 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
No public exploit references are available in this record.
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