Application crash via trusted chunkCount attribute
Published Jun 26, 2020 · Updated Aug 4, 2024
Heap buffer overflow in OpenEXR before 2.5.2 allows local users to crash an application by supplying an EXR file with an invalid chunkCount. getChunkOffsetTableSize() trusts that header value for supported image types instead of deriving the offset-table size from the image layout, allowing later table processing to write beyond the allocation. Exploitation requires local access to make an application process the crafted file; published impact is limited to a crash, with no confidentiality or integrity effect.
Summary
What happened
Heap buffer overflow in OpenEXR before 2.5.2 allows local users to crash an application by supplying an EXR file with an invalid chunkCount. getChunkOffsetTableSize() trusts that header value for supported image types instead of deriving the offset-table size from the image layout, allowing later table processing to write beyond the allocation. Exploitation requires local access to make an application process the crafted file; published impact is limited to a crash, with no confidentiality or integrity effect.
The record
- CVE
- CVE-2020-15306
- Published
- Jun 26, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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
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