OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. OpenEXR versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13 are vulnerable to a heap out-of-bounds write when exrmetrics reads a crafted deep scanline EXR. This occurs with pixel conversion options such as --pixelmode float or --bench because DeepSlice requests FLOAT output while the backing sample buffers are allocated using the input HALF element size. The issue is fixed in versions 3.3.13 and 3.4.14.

OpenEXR, the reference implementation for the EXR image format widely used in the motion picture industry, is affected by a heap out-of-bounds write vulnerability. The flaw impacts versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13. The vulnerability is triggered when the exrmetrics tool reads a specially crafted deep scanline EXR file using pixel conversion options such as --pixelmode float or --bench. The root cause is a size mismatch: DeepSlice requests FLOAT output while the backing sample buffers are allocated using the smaller HALF element size, leading to memory corruption. An attacker could potentially exploit this by supplying a malicious EXR file to a vulnerable application. The issue has been patched in versions 3.3.13 and 3.4.14. Users are strongly advised to upgrade to the fixed versions immediately.