Bug 1932040 (CVE-2020-35523) - CVE-2020-35523 libtiff: Integer overflow in tif_getimage.c
Summary: CVE-2020-35523 libtiff: Integer overflow in tif_getimage.c
Alias: CVE-2020-35523
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1932042 1932043 1934518 1934519 1945541 1945542
Blocks: 1932047 1932054
TreeView+ depends on / blocked
Reported: 2021-02-23 19:47 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:
An integer overflow flaw was found in libtiff that exists in the tif_getimage.c file. This flaw allows an attacker to inject and execute arbitrary code when a user opens a crafted TIFF file. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.
Clone Of:
Last Closed: 2021-11-09 18:22:39 UTC

Attachments (Terms of Use)

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

Description Pedro Sampaio 2021-02-23 19:47:12 UTC
In libtiff 4.1.0, an integer overflow vulnerability exists in tif_getimage.c file. By enticing a user to open a craft TIFF file, an attacker may leverage the vulnerability to inject and execute arbitrary code.



Comment 1 Pedro Sampaio 2021-02-23 19:48:05 UTC
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1932043]

Created mingw-libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1932042]

Comment 5 errata-xmlrpc 2021-11-09 17:53:32 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 6 Product Security DevOps Team 2021-11-09 18:22: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.