Contributors to the OpenEXR Project

9 exploits Active since Apr 2020
CVE-2020-15304 WRITEUP MEDIUM WRITEUP
OpenEXR < 2.5.2 - NULL Pointer Dereference in TiledInputFile Constructor
An issue was discovered in OpenEXR before 2.5.2. An invalid tiled input file could cause invalid memory access in TiledInputFile::TiledInputFile() in IlmImf/ImfTiledInputFile.cpp, as demonstrated by a NULL pointer dereference.
CVSS 5.5
CVE-2020-15305 WRITEUP MEDIUM WRITEUP
OpenEXR < 2.5.2 - Use-After-Free in DeepScanLineInputFile
An issue was discovered in OpenEXR before 2.5.2. Invalid input could cause a use-after-free in DeepScanLineInputFile::DeepScanLineInputFile() in IlmImf/ImfDeepScanLineInputFile.cpp.
CVSS 5.5
CVE-2020-15306 WRITEUP MEDIUM WRITEUP
OpenEXR < 2.5.2 - Heap Buffer Overflow via Invalid ChunkCount Attribute
An issue was discovered in OpenEXR before v2.5.2. Invalid chunkCount attributes could cause a heap buffer overflow in getChunkOffsetTableSize() in IlmImf/ImfMisc.cpp.
CVSS 5.5
CVE-2020-11759 WRITEUP MEDIUM WRITEUP
OpenEXR < 2.4.1 - Integer Overflow via Deep Frame Buffer Handling
An issue was discovered in OpenEXR before 2.4.1. Because of integer overflows in CompositeDeepScanLine::Data::handleDeepFrameBuffer and readSampleCountForLineBlock, an attacker can write to an out-of-bounds pointer.
CVSS 5.5
CVE-2020-11762 WRITEUP MEDIUM WRITEUP
OpenEXR < 2.4.1 - Out-of-bounds Read and Write in DwaCompressor
An issue was discovered in OpenEXR before 2.4.1. There is an out-of-bounds read and write in DwaCompressor::uncompress in ImfDwaCompressor.cpp when handling the UNKNOWN compression case.
CVSS 5.5
CVE-2020-11763 WRITEUP MEDIUM WRITEUP
OpenEXR < 2.4.1 - Out-of-bounds Read and Write in ImfTileOffsets
An issue was discovered in OpenEXR before 2.4.1. There is an std::vector out-of-bounds read and write, as demonstrated by ImfTileOffsets.cpp.
CVSS 5.5
CVE-2020-15306 WRITEUP MEDIUM WRITEUP
OpenEXR < 2.5.2 - Heap Buffer Overflow via Invalid ChunkCount Attribute
An issue was discovered in OpenEXR before v2.5.2. Invalid chunkCount attributes could cause a heap buffer overflow in getChunkOffsetTableSize() in IlmImf/ImfMisc.cpp.
CVSS 5.5
CVE-2025-64182 WRITEUP HIGH WRITEUP
OpenEXR 3.2.0-3.2.4 3.3.0-3.3.5 3.4.0-3.4.2 - Heap Overflow via Legacy Python InputFile Wrapper
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.
CVSS 7.8
CVE-2025-64183 WRITEUP HIGH WRITEUP
OpenEXR 3.2.0-3.2.4 3.3.0-3.3.5 3.4.0-3.4.2 - Use-After-Free in PyObject_StealAttrString
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.
CVSS 7.5