CyberRota Analysis
AI-GeneratedThe HTJ2K decoder in OpenEXR versions 3.4.0 to 3.4.12 is vulnerable to an out-of-bounds read due to inadequate validation of the header-length field (PLEN) from compressed data, allowing attackers to exploit this flaw through specially crafted EXR files. This vulnerability could lead to potential information disclosure or application crashes during the decoding process. Users and organizations utilizing affected versions of OpenEXR, particularly in the motion picture industry, should prioritize upgrading to version 3.4.13 to mitigate this risk.
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. From version 3.4.0 through 3.4.12, the HTJ2K decoder parses a header-length field (PLEN) from a chunk's compressed data but never checks that this value fits within the available buffer before using it. When decoding, it advances the codestream pointer by the attacker-supplied header size and passes the resulting offset and remaining length to the OpenJPH memory-input path, so a crafted value pushes the pointer past the end of the buffer and causes an out-of-bounds read. Because this field comes straight from attacker-controlled EXR chunk data, the flaw is reachable during normal decoding of an untrusted file. This issue is fixed in version 3.4.13.