Bug 1474356 (CVE-2017-11335) - CVE-2017-11335 libtiff: Heap-based buffer overflow in tiff2pdf
Summary: CVE-2017-11335 libtiff: Heap-based buffer overflow in tiff2pdf
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2017-11335
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: 1474372 1474373 1474374 1910612
Blocks: 1474358
TreeView+ depends on / blocked
 
Reported: 2017-07-24 12:50 UTC by Adam Mariš
Modified: 2022-04-17 20:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A heap-based buffer overflow flaw was found within libtiff's tiff2pdf tool. A remote attacker could potentially exploit this flaw to execute arbitrary code by tricking a user into converting a specially crafted file using the tiff2pdf tool.
Clone Of:
Environment:
Last Closed: 2017-07-28 10:52:52 UTC
Embargoed:

Attachments (Terms of Use)

Description Adam Mariš 2017-07-24 12:50:05 UTC 
There is a heap based buffer overflow in tools/tiff2pdf.c of LibTIFF
4.0.8 via a PlanarConfig=Contig image, which causes a more than one
hundred bytes out-of-bounds write (related to the ZIPDecode function in
tif_zip.c). A crafted input may lead to a remote denial of service
attack or an arbitrary code execution attack.

Upstream bug:

http://bugzilla.maptools.org/show_bug.cgi?id=2715


Upstream patch:
https://github.com/vadz/libtiff/commit/69bfeec247899776b1b396651adb47436e5f1556
Comment 1 Adam Mariš 2017-07-24 13:25:38 UTC 
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1474373]


Created mingw-libtiff tracking bugs for this issue:

Affects: epel-7 [bug 1474372]
Affects: fedora-all [bug 1474374]
Comment 3 Raphael Sanchez Prudencio 2017-07-28 10:53:01 UTC 
Statement:

Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
Note You need to log in before you can comment on or make changes to this bug.