OpenEXR has buffer overflow in PyOpenEXR_old's channels() and channel()
- 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.5, 3.3.6, 3.4.3
- 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: poc
- 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 versions 3.2.0 through 3.2.4, 3.3.0 through 3.3.5, and 3.4.0 through 3.4.2, a memory safety bug in the legacy OpenEXR Python adapter (the deprecated OpenEXR.InputFile wrapper) allow crashes and likely code execution when opening attacker-controlled EXR files or when passing crafted Python objects. Integer overflow and unchecked allocation in InputFile.channel() and InputFile.channels() can lead to heap overflow (32 bit) or a NULL deref (64 bit). Versions 3.2.5, 3.3.6, and 3.4.3 contain a patch for the issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- AcademySoftwareFoundation openexr
From 3.2.0 · fixed in 3.2.5; From 3.3.0 · fixed in 3.3.6; From 3.4.0 · fixed in 3.4.3
- openexrPyPI
From 3.2.0 · fixed in 3.2.5
- openexrPyPI
From 3.3.0 · fixed in 3.3.6
- openexrPyPI
From 3.4.0 · fixed in 3.4.3
- openexrPyPI
From 3.2.0 · fixed in 3.2.5; From 3.3.0 · fixed in 3.3.6; From 3.4.0 · fixed in 3.4.3