Application crash via unterminated DWA suffix
Published Apr 14, 2020 · Updated Aug 4, 2024
Out-of-bounds read in OpenEXR before 2.4.1 allows context-dependent attackers to crash an application via a crafted image file. DwaCompressor::Classifier::Classifier stores a maximum-length DWA suffix in a fixed stack buffer without preserving its null terminator, so std::string reads beyond the buffer. Processing attacker-controlled EXR data is required, and the documented result is an application crash rather than data modification.
Summary
What happened
Out-of-bounds read in OpenEXR before 2.4.1 allows context-dependent attackers to crash an application via a crafted image file. DwaCompressor::Classifier::Classifier stores a maximum-length DWA suffix in a fixed stack buffer without preserving its null terminator, so std::string reads beyond the buffer. Processing attacker-controlled EXR data is required, and the documented result is an application crash rather than data modification.
The record
- CVE
- CVE-2020-11765
- Published
- Apr 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-193, CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 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
- Project Zero issue 1987 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