CyberRota Analysis
AI-GeneratedVersions 3.4.0 through 3.4.12 of OpenEXR are vulnerable to a denial of service due to an assertion failure in the HTJ2K decode path, which can be triggered by a specially crafted HTJ2K-compressed EXR file. This flaw allows an attacker to cause an unconditional process abort when the exr_start_read() function is called with untrusted input, impacting any application utilizing this library. Organizations using OpenEXR in their workflows, 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. In versions 3.4.0 through 3.4.12, a reachable assertion failure in the HTJ2K decode path allows a crafted HTJ2K-compressed EXR file to cause an unconditional process abort in any application that calls exr_start_read() on untrusted input, resulting in denial of service. The crash is triggered by a QCD marker whose lower five bits are zero, which OpenEXR passes into the vendored OpenJPH library while constructing the codestream and evaluating its quantization delta parameters. OpenJPH uses an assertion rather than a recoverable error to validate those bits, so any invalid value calls abort() directly and cannot be intercepted by surrounding error handling, a problem compounded by OpenEXR wrapping only its internal HT header parser in error handling while leaving the later codestream read and construction calls unprotected. This issue has been resolved in version 3.4.13.