OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13, a crafted tiled EXR can trigger a heap out-of-bounds write on 32-bit/ILP32 builds when read through the public TiledRgbaInputFile RGBA API. The file uses a small 40x40 dataWindow but a 65537x65537 tile size. On ILP32, the Array2D<Rgba> tile-conversion buffer size calculation overflows, allocates a much smaller heap buffer, and tile decode writes past that allocation. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.

A heap out-of-bounds write vulnerability exists in OpenEXR, the reference implementation for the EXR image format used widely in the motion picture industry. The flaw affects versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 on 32-bit/ILP32 builds. A specially crafted tiled EXR file with a small 40x40 dataWindow but an oversized 65537x65537 tile size can trigger the vulnerability through the TiledRgbaInputFile RGBA API. On ILP32 systems, the Array2D tile-conversion buffer size calculation overflows, causing allocation of a much smaller heap buffer than required. Tile decode operations then write past the allocated buffer boundary, resulting in heap memory corruption. The vulnerability has been patched in versions 3.2.11, 3.3.13, and 3.4.14. Exploitation requires an attacker to supply a maliciously crafted EXR file to a vulnerable application running on a 32-bit/ILP32 platform.