Application crash via DWA buffer-size integer overflow
Published Jun 8, 2021 · Updated Aug 3, 2024
Integer overflow in OpenEXR before 3.0.1 allows attackers to crash applications that process crafted DWA-compressed EXR files. DwaCompressor::initializeBuffers stores its maximum output-buffer calculation in a signed int and casts size terms to int, allowing large values to wrap before heap allocation. Processing the crafted image through a linked application is required; the published impact is an application crash, not code execution.
Summary
What happened
Integer overflow in OpenEXR before 3.0.1 allows attackers to crash applications that process crafted DWA-compressed EXR files. DwaCompressor::initializeBuffers stores its maximum output-buffer calculation in a signed int and casts size terms to int, allowing large values to wrap before heap allocation. Processing the crafted image through a linked application is required; the published impact is an application crash, not code execution.
The record
- CVE
- CVE-2021-26260
- Published
- Jun 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-190, CWE-400, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 8, 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.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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