Memory exhaustion via absent-channel buffer allocation
Published Mar 31, 2021 · Updated Aug 3, 2024
Uncontrolled resource consumption in OpenEXR before 3.0.0-beta allows attackers to exhaust memory through a crafted EXR file. InputFile::setFrameBuffer allocates a tile-row cache for every requested channel, including fill channels absent from the image. Processing the file through the Scanline API is required, and the resulting allocation pressure can terminate or stall the consuming application.
Summary
What happened
Uncontrolled resource consumption in OpenEXR before 3.0.0-beta allows attackers to exhaust memory through a crafted EXR file. InputFile::setFrameBuffer allocates a tile-row cache for every requested channel, including fill channels absent from the image. Processing the file through the Scanline API is required, and the resulting allocation pressure can terminate or stall the consuming application.
The record
- CVE
- CVE-2021-3479
- Published
- Mar 31, 2021
- Updated
- Aug 3, 2024
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-400, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 2021CVE 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=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