Application crash via unchecked deep-image channel sampling
Published Dec 31, 2021 · Updated Aug 4, 2024
Heap-based buffer overflow in OpenEXR 3.1.0 through 3.1.3 allows context-dependent attackers to crash applications via a crafted deep image. CompositeDeepScanLine accepts framebuffer channels with non-unit xSampling or ySampling values, causing LineCompositeTask::execute to composite deep scanline data into an incompatible layout and write past a heap buffer. A victim application must open the crafted image; the published assessment limits the consequence to a crash, with no confidentiality or integrity impact.
Summary
What happened
Heap-based buffer overflow in OpenEXR 3.1.0 through 3.1.3 allows context-dependent attackers to crash applications via a crafted deep image. CompositeDeepScanLine accepts framebuffer channels with non-unit xSampling or ySampling values, causing LineCompositeTask::execute to composite deep scanline data into an incompatible layout and write past a heap buffer. A victim application must open the crafted image; the published assessment limits the consequence to a crash, with no confidentiality or integrity impact.
The record
- CVE
- CVE-2021-45942
- Published
- Dec 31, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 31, 2021CVE 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.
Public exploit references
- OSS-Fuzz issue 41416 crash reproducerproof 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