Bug 1929320 (CVE-2020-16587) - CVE-2020-16587 OpenEXR: A heap-based buffer overflow in chunkOffsetReconstruction in ImfMultiPartInputFile.cpp could result in a DOS via a crafted EXR file
Summary: CVE-2020-16587 OpenEXR: A heap-based buffer overflow in chunkOffsetReconstruc...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2020-16587
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1929321 1929324 1930949 1930950 1930951
Blocks: 1929327
TreeView+ depends on / blocked
 
Reported: 2021-02-16 16:39 UTC by Michael Kaplan
Modified: 2021-11-02 23:07 UTC (History)
6 users (show)

Fixed In Version: openexr 2.4.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-02 23:07:11 UTC
Embargoed:


Attachments (Terms of Use)

Description Michael Kaplan 2021-02-16 16:39:09 UTC
A heap-based buffer overflow vulnerability exists in Academy Software Foundation OpenEXR 2.3.0 in chunkOffsetReconstruction in ImfMultiPartInputFile.cpp that can cause a denial of service via a crafted EXR file.

Comment 2 Michael Kaplan 2021-02-16 16:40:16 UTC
Created OpenEXR tracking bugs for this issue:

Affects: fedora-all [bug 1929321]

Comment 5 Todd Cullum 2021-02-19 21:05:05 UTC
Statement:

This flaw is out of support scope for OpenEXR as shipped with Red Hat Enterprise Linux 6 and 7. For more information on Red Hat Enterprise Linux support scope, please see https://access.redhat.com/support/policy/updates/errata/ .

Comment 6 Todd Cullum 2021-02-24 17:54:05 UTC
Flaw summary:

MultiPartInputFile::Data::chunkOffsetReconstruction() in OpenEXR/IlmImf/ImfMultiPartInputFile.cpp has an off-by-one error allowing an invalid index to be used when restructuring the chunk offset table. This could cause an out-of-bounds read.

Upstream patch: https://github.com/AcademySoftwareFoundation/openexr/commit/8b5370c688a7362673c3a5256d93695617a4cd9a


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