Application crash via unallocated DPX output buffer
Published Dec 23, 2022 · Updated Apr 14, 2025
Null pointer dereference in OpenImageIO 2.4.4.2 allows remote attackers to crash an application through a crafted image specification. DPXOutput::prep_subimage returns before allocating m_buf for two-channel or five-to-eight-channel DPX output, but close() still passes the null buffer to WriteElement. Reachability requires an application to generate DPX output from an attacker-controlled input file or specification; the documented consequence is an application crash.
Summary
What happened
Null pointer dereference in OpenImageIO 2.4.4.2 allows remote attackers to crash an application through a crafted image specification. DPXOutput::prep_subimage returns before allocating m_buf for two-channel or five-to-eight-channel DPX output, but close() still passes the null buffer to WriteElement. Reachability requires an application to generate DPX output from an attacker-controlled input file or specification; the documented consequence is an application crash.
The record
- CVE
- CVE-2022-43593
- Published
- Dec 23, 2022
- Updated
- Apr 14, 2025
- Vendor
- Academy Software Foundation
- Product
- OpenImageIO
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record 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=v2.4.4.2
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