Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1524284 - (CVE-2017-17095) CVE-2017-17095 libtiff: Heap-based buffer overflow in tools/pal2rgb.c can lead to denial of service
CVE-2017-17095 libtiff: Heap-based buffer overflow in tools/pal2rgb.c can lea...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20171129,repor...
: Security
Depends On: 1524285 1526899
Blocks: 1524288
  Show dependency treegraph
 
Reported: 2017-12-11 02:13 EST by Sam Fowler
Modified: 2017-12-19 07:45 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-18 02:24:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2017-12-11 02:13:39 EST
The pal2rgb tool (tools/pal2rgb.c) in LibTIFF 4.0.9 is vulnerable to a heap-based bufferflow when parsing a specially crafted .tif file. A remote attacker could exploit this to cause an application crash (denial of service) or other possible unspecified impact.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-17095
http://www.openwall.com/lists/oss-security/2017/11/30/3
http://www.cvedetails.com/cve/CVE-2017-17095/
http://bugzilla.maptools.org/show_bug.cgi?id=2750
Comment 1 Sam Fowler 2017-12-11 02:14:03 EST
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1524285]
Comment 2 Huzaifa S. Sidhpurwala 2017-12-18 02:23:07 EST
Note: As per upstream bug, there is currently no patch yet. The proposed patch seems to be insufficient, since the issue still manifests after the patch is applied.

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