Bug 1932037 (CVE-2020-35522) - CVE-2020-35522 libtiff: Memory allocation failure in tiff2rgba
Summary: CVE-2020-35522 libtiff: Memory allocation failure in tiff2rgba
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2020-35522
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: 1932038 1932039 1934518 1934519 1945555 1945556
Blocks: 1932047 1932054
TreeView+ depends on / blocked
 
Reported: 2021-02-23 19:43 UTC by Pedro Sampaio
Modified: 2021-11-09 18:22 UTC (History)
7 users (show)

Fixed In Version: libtiff 4.2.0
Doc Type: If docs needed, set a value
Doc Text:
In LibTIFF, there is a memory malloc failure in tif_pixarlog.c. A crafted TIFF document can lead to an abort, resulting in a remote denial of service attack.
Clone Of:
Environment:
Last Closed: 2021-11-09 18:22:08 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4241 0 None None None 2021-11-09 17:53:29 UTC

Description Pedro Sampaio 2021-02-23 19:43:33 UTC 
A flaw was found in libtiff 4.1.0 and before. Due to a memory allocation failure in tif_read.c, a crafted TIFF file can lead to an abort, resulting in denial of service.

This is a different flaw from CVE-2020-35521

References:

https://gitlab.com/libtiff/libtiff/-/merge_requests/165
https://gitlab.com/libtiff/libtiff/-/commit/98a254f5b92cea22f5436555ff7fceb12afee84d
Comment 1 Pedro Sampaio 2021-02-23 19:44:07 UTC 
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1932038]


Created mingw-libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1932039]
Comment 4 errata-xmlrpc 2021-11-09 17:53:27 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2021:4241 https://access.redhat.com/errata/RHSA-2021:4241
Comment 5 Product Security DevOps Team 2021-11-09 18:22:06 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2020-35522
Note You need to log in before you can comment on or make changes to this bug.