OpenEXR has use after free in PyObject_StealAttrString
- 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: partial
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, there is a use-after-free in PyObject_StealAttrString of pyOpenEXR_old.cpp. The legacy adapter defines PyObject_StealAttrString that calls PyObject_GetAttrString to obtain a new reference, immediately decrefs it, and returns the pointer. Callers then pass this dangling pointer to APIs like PyLong_AsLong/PyFloat_AsDouble, resulting in a use-after-free. This is invoked in multiple places (e.g., reading PixelType.v, Box2i, V2f, etc.) Versions 3.2.5, 3.3.6, and 3.4.3 fix the issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- 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; 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