Memory exhaustion via incomplete scanline size check
Published Mar 31, 2021 · Updated Aug 3, 2024
Resource exhaustion in OpenEXR 2.4.0 through 2.4.2 and 2.5.0 through 2.5.3 allows attackers to exhaust process memory. ScanLineInputFile::initialize checks lineOffsetSize alone before allocating lineOffsets and bytesPerLine tables, omitting the linesInBuffer multiplier needed for the latter. Processing a crafted EXR file is required, and the excessive allocation can terminate or stall the consuming application without affecting confidentiality or integrity.
Summary
What happened
Resource exhaustion in OpenEXR 2.4.0 through 2.4.2 and 2.5.0 through 2.5.3 allows attackers to exhaust process memory. ScanLineInputFile::initialize checks lineOffsetSize alone before allocating lineOffsets and bytesPerLine tables, omitting the linesInBuffer multiplier needed for the latter. Processing a crafted EXR file is required, and the excessive allocation can terminate or stall the consuming application without affecting confidentiality or integrity.
The record
- CVE
- CVE-2021-3478
- Published
- Mar 31, 2021
- Updated
- Aug 3, 2024
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-770, 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