Bug 1828995 (CVE-2020-11763) - CVE-2020-11763 OpenEXR: std::vector out-of-bounds read and write in ImfTileOffsets.cpp
Summary: CVE-2020-11763 OpenEXR: std::vector out-of-bounds read and write in ImfTileOf...
Alias: CVE-2020-11763
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1828996 1828997 1833565 1833566 1833567
Blocks: 1829017
TreeView+ depends on / blocked
Reported: 2020-04-28 17:16 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-02-16 20:11 UTC (History)
5 users (show)

Fixed In Version: OpenEXR 2.4.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-09-29 22:00:37 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:4039 0 None None None 2020-09-29 20:50:32 UTC

Description Guilherme de Almeida Suckevicz 2020-04-28 17:16:30 UTC
An issue was discovered in OpenEXR before 2.4.1. There is an std::vector out-of-bounds read and write, as demonstrated by ImfTileOffsets.cpp.


Comment 1 Guilherme de Almeida Suckevicz 2020-04-28 17:16:49 UTC
Created OpenEXR tracking bugs for this issue:

Affects: fedora-all [bug 1828996]

Created mingw-OpenEXR tracking bugs for this issue:

Affects: fedora-all [bug 1828997]

Comment 3 Todd Cullum 2020-05-08 22:21:03 UTC

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Comment 4 Todd Cullum 2020-05-08 22:23:02 UTC
This flaw affects versions of OpenEXR shipped in Red Hat Enterprise Linux 7 and 8.

Comment 7 errata-xmlrpc 2020-09-29 20:50:30 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2020:4039 https://access.redhat.com/errata/RHSA-2020:4039

Comment 8 Product Security DevOps Team 2020-09-29 22:00:37 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.