Memory read or write via unchecked sample counts
Published Feb 1, 2024 · Updated Nov 4, 2025
Heap overflow in OpenEXR 3.1.0 through 3.1.11 and 3.2.0 through 3.2.1 allows attackers to read or write process memory via crafted files. generic_unpack_deep uses input-derived deep-scanline sample counts as UNPACK_SAMPLES loop bounds without validating them against the destination buffer. Library consumers that parse deep scanline data reach the vulnerable path, while bundled exr utilities skip deep storage by default.
Summary
What happened
Heap overflow in OpenEXR 3.1.0 through 3.1.11 and 3.2.0 through 3.2.1 allows attackers to read or write process memory via crafted files. generic_unpack_deep uses input-derived deep-scanline sample counts as UNPACK_SAMPLES loop bounds without validating them against the destination buffer. Library consumers that parse deep scanline data reach the vulnerable path, while bundled exr utilities skip deep storage by default.
The record
- CVE
- CVE-2023-5841
- Published
- Feb 1, 2024
- Updated
- Nov 4, 2025
- Vendor
- Academy Software Foundation
- Product
- OpenEXR
- Classifications
- CWE-787, CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 1, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 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=0 <=3.2.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
- AHA! crafted EXR proof of conceptproof of concept · validated
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