OpenEXR has a signed 32-bit Overflow in PIZ Decoder Leads to OOB Read/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.7, 3.3.9, 3.4.9
- 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. From 3.1.0 to before 3.2.7, 3.3.9, and 3.4.9, internal_exr_undo_piz() advances the working wavelet pointer with signed 32-bit arithmetic. Because nx, ny, and wcount are int, a crafted EXR file can make this product overflow and wrap. The next channel then decodes from an incorrect address. The wavelet decode path operates in place, so this yields both out-of-bounds reads and out-of-bounds writes. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- AcademySoftwareFoundation openexr
From 3.1.0 · through 3.1.13; From 3.2.0 · fixed in 3.2.7; From 3.3.0 · fixed in 3.3.9; From 3.4.0 · fixed in 3.4.9
- openexrPyPI
From 3.1.0 · fixed in 3.2.7
- openexrPyPI
From 3.3.0 · fixed in 3.3.9
- openexrPyPI
From 3.4.0 · fixed in 3.4.9
- openexrPyPI
From 3.1.0 · fixed in 3.2.7; From 3.3.0 · fixed in 3.3.9; From 3.4.0 · fixed in 3.4.9