CyberRota Analysis
AI-GeneratedThe vulnerability affects OpenEXRUtil versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.12, where the TypedDeepImageChannel<T>::row() API can return an out-of-bounds pointer due to conflicting coordinate models, leading to potential heap out-of-bounds reads and application crashes, with a risk of information disclosure. Organizations in the motion picture industry using these specific versions should prioritize updating to versions 3.3.13 or 3.4.13 to mitigate the risk associated with this high-severity flaw.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In OpenEXRUtil versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.12, the documented TypedDeepImageChannel<T>::row() API can return an out-of-bounds pointer when a deep image has a non-zero dataWindow origin, resulting in a heap out-of-bounds read and crash, with potential information disclosure under a controlled heap layout. The flaw arises because ImfDeepImageChannel uses two conflicting coordinate models: at(x, y) uses absolute coordinates (with _base offset by dataWindow.min), while row(r) is documented as 0-based logical access. For a non-zero dataWindow.min, row(0) therefore points outside the _sampleListPointers allocation instead of at the first logical row. This issue is fixed in versions 3.3.13 and 3.4.13.