An issue was discovered in OpenEXR before 2.4.1. Because of integer overflows in CompositeDeepScanLine::Data::handleDeepFrameBuffer and readSampleCountForLineBlock, an attacker can write to an out-of-bounds pointer. References: https://bugs.chromium.org/p/project-zero/issues/detail?id=1987 https://github.com/AcademySoftwareFoundation/openexr/blob/master/CHANGES.md#version-241-february-11-2020
Created OpenEXR tracking bugs for this issue: Affects: fedora-all [bug 1829019] Created mingw-OpenEXR tracking bugs for this issue: Affects: fedora-all [bug 1829018]
Upstream patch: https://github.com/AcademySoftwareFoundation/openexr/commit/b9997d0c045fa01af3d2e46e1a74b07cc4519446#diff-c94c7f60fd67c758b01f35b05c753bab
Other associated patches: https://github.com/AcademySoftwareFoundation/openexr/commit/e79d2296496a50826a15c667bf92bdc5a05518b4#diff-43177fd19d088bdab917430799223092
Appears to be caused by an integer overflow due to use of an int type rather than ptrdiff_t type in CompositeDeepScanLine::Data::handleDeepFrameBuffer.
Statement: The versions of OpenEXR which are vulnerable to this flaw are not shipped in Red Hat Enterprise Linux 7 or prior.
After speaking with upstream, the patch for this was actually: https://github.com/AcademySoftwareFoundation/openexr/pull/643/commits/41a99da450e749800182674012c8df002919e15a .