Bug 1624981 (CVE-2018-16335) - CVE-2018-16335 libtiff: Heap-based buffer overflow in ChopUpSingleUncompressedStrip in tif_dirread.c
Summary: CVE-2018-16335 libtiff: Heap-based buffer overflow in ChopUpSingleUncompresse...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2018-16335
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1624982 1624984 1624985 1624986
Blocks: 1624983
TreeView+ depends on / blocked
 
Reported: 2018-09-03 19:27 UTC by Laura Pardo
Modified: 2023-09-20 14:19 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:37:14 UTC
Embargoed:

Attachments (Terms of Use)

Description Laura Pardo 2018-09-03 19:27:44 UTC 
A flaw was found in LibTIFF 4.0.9. The newoffsets handling in ChopUpSingleUncompressedStrip in tif_dirread.c allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) via a crafted TIFF file, as demonstrated by tiff2pdf. This is a different vulnerability than CVE-2018-15209.


References:
http://bugzilla.maptools.org/show_bug.cgi?id=2809
Comment 1 Laura Pardo 2018-09-03 19:28:34 UTC 
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1624982]


Created mingw-libtiff tracking bugs for this issue:

Affects: epel-7 [bug 1624985]
Affects: fedora-all [bug 1624984]
Comment 4 Paul Harvey 2018-10-02 09:28:58 UTC 
openshift-enterprise-3: the following container images include versions of libtiff ranging from 4.0.3-14.el7 to libtiff-4.0.3-27.el7_3 which will not be fixed; the underlying rhel-7 package is marked wontfix due to its low/moderate impact -
- openshift3/mediawiki-123 including v3.6.173.0.130-1, v3.7.64-2, v3.9.43-2
- openshift3/mediawiki including v3.10.45-2
- openshift3/metrics-hawkular-metrics including 3.1.1-7, 3.2.1-16, 3.3.1-24, v3.7.64-5, v3.10.45-3
Note You need to log in before you can comment on or make changes to this bug.