Application interruption via oversized B44 temporary buffer
Published Aug 23, 2022 · Updated Aug 3, 2024
Uncontrolled resource consumption in OpenEXR before 3.0.0-beta allows attackers to interrupt applications processing crafted EXR files. B44Compressor sizes its unsigned-short temporary buffer with a byte count, allocating two bytes for each byte of uncompressed scanline data. An attacker must cause an application to process a crafted file; the oversized allocation can exhaust available memory and terminate or stall that application.
Summary
What happened
Uncontrolled resource consumption in OpenEXR before 3.0.0-beta allows attackers to interrupt applications processing crafted EXR files. B44Compressor sizes its unsigned-short temporary buffer with a byte count, allocating two bytes for each byte of uncompressed scanline data. An attacker must cause an application to process a crafted file; the oversized allocation can exhaust available memory and terminate or stall that application.
The record
- CVE
- CVE-2021-20298
- Published
- Aug 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-400, CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 23, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in OpenEXR 3.0.0-beta
What conditions does exploitation require?
What is affected?
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