OpenEXR CompositeDeepScanLine integer-overflow leads to heap OOB write
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.2.6, 3.3.8, 3.4.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. In CompositeDeepScanLine::readPixels, per-pixel totals are accumulated in vector<unsigned int> total_sizes for attacker-controlled large counts across many parts, total_sizes[ptr] wraps modulo 2^32. overall_sample_count is then derived from wrapped totals and used in samples[channel].resize(overall_sample_count). Decode pointer setup/consumption proceeds with true sample counts, and write operations in core unpack (generic_unpack_deep_pointers) overrun the undersized composite sample buffer. This vulnerability is fixed in v3.2.6, v3.3.8, and v3.4.6.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- AcademySoftwareFoundation openexr
From 2.3.0 · fixed in 3.2.6; From 3.3.0 · fixed in 3.3.8; From 3.4.0 · fixed in 3.4.6
- openexrPyPI
From 2.3.0 · fixed in 3.2.6; From 3.3.0 · fixed in 3.3.8; From 3.4.0 · fixed in 3.4.6
- openexrPyPI
From 2.3.0 · fixed in 3.2.6
- openexrPyPI
From 3.3.0 · fixed in 3.3.8
- openexrPyPI
From 3.4.0 · fixed in 3.4.6