Application crash via unchecked RLE input length
Published Apr 14, 2020 · Updated Aug 4, 2024
Out-of-bounds read in OpenEXR before 2.4.1 allows context-dependent attackers to crash applications via crafted RLE-compressed EXR files. In rleUncompress in ImfRle.cpp, the literal-run branch calls memcpy after the remaining input length becomes negative. A consuming application must decode an attacker-supplied file to reach the flaw, which can terminate the decoding process.
Summary
What happened
Out-of-bounds read in OpenEXR before 2.4.1 allows context-dependent attackers to crash applications via crafted RLE-compressed EXR files. In rleUncompress in ImfRle.cpp, the literal-run branch calls memcpy after the remaining input length becomes negative. A consuming application must decode an attacker-supplied file to reach the flaw, which can terminate the decoding process.
The record
- CVE
- CVE-2020-11760
- Published
- Apr 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004
- 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.
Public exploit references
- Project Zero issue 1987 OpenEXR crash reportproof 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