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 1530440 - (CVE-2017-18013) CVE-2017-18013 libtiff: NULL pointer dereference in tif_print.c:TIFFPrintDirectory() causes crash
CVE-2017-18013 libtiff: NULL pointer dereference in tif_print.c:TIFFPrintDire...
Status: CLOSED NOTABUG
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=20171229,repor...
: Security
Depends On: 1530441
Blocks: 1530443
  Show dependency treegraph
 
Reported: 2018-01-02 23:01 EST by Sam Fowler
Modified: 2018-01-08 00:42 EST (History)
3 users (show)

See Also:
Fixed In Version: libtiff 4.0.9-3
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-01-08 00:42:09 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 2018-01-02 23:01:56 EST
LibTIFF 4.0.9 is vulnerable to a crash caused by a NULL pointer dereference in the TIFFPrintDirectory function in tif_print.c. An attacker could exploit this by supplying a specially crafted TIFF image, leading to a denial of service.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-18013
http://www.cvedetails.com/cve/CVE-2017-18013/
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-18013
https://gitlab.com/libtiff/libtiff/commit/c6f41df7b581402dfba3c19a1e3df4454c551a01
http://bugzilla.maptools.org/show_bug.cgi?id=2770
Comment 1 Sam Fowler 2018-01-02 23:03:12 EST
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1530441]
Comment 2 Huzaifa S. Sidhpurwala 2018-01-08 00:41:27 EST
It seems this flaw is triggered by the following changeset:
https://gitlab.com/libtiff/libtiff/commit/7057734d986001b7fd6d2afde9667da7754ff2cc

This was introduced in tiff-4.0.9, therefore older versions are not affected.

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