Process crash via headerless multipart EXR file
Published Mar 16, 2022 · Updated Aug 3, 2024
NULL pointer dereference in OpenEXR before 2.5.4 allows attackers to crash an application with a multipart EXR file containing no parts. MultiPartInputFile::initialize accepts an empty _headers vector and continues without rejecting the missing part header, leaving later header handling to dereference a null pointer. Any process that passes an untrusted multipart EXR file into the library can terminate; no confidentiality or integrity impact is reported.
Summary
What happened
NULL pointer dereference in OpenEXR before 2.5.4 allows attackers to crash an application with a multipart EXR file containing no parts. MultiPartInputFile::initialize accepts an empty _headers vector and continues without rejecting the missing part header, leaving later header handling to dereference a null pointer. Any process that passes an untrusted multipart EXR file into the library can terminate; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2021-20299
- Published
- Mar 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-476
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 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=Affected before v2.5.4
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