Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1630004 - (CVE-2018-17000) CVE-2018-17000 libtiff: NULL pointer dereference in function _TIFFmemcmp at tif_unix.c
CVE-2018-17000 libtiff: NULL pointer dereference in function _TIFFmemcmp at t...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20180913,reported=2...
: Security
Depends On: 1630006 1630007 1630009 1630010 1630011
Blocks: 1630008
  Show dependency treegraph
 
Reported: 2018-09-17 14:23 EDT by Pedro Sampaio
Modified: 2018-09-24 02:15 EDT (History)
18 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-09-24 02:15:08 EDT
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 Pedro Sampaio 2018-09-17 14:23:43 EDT
A NULL pointer dereference in the function _TIFFmemcmp at tif_unix.c (called from TIFFWriteDirectoryTagTransferfunction) in LibTIFF 4.0.9 allows an attacker to cause a denial-of-service through a crafted tiff file. This vulnerability can be triggered by the executable tiffcp.

Upstream bug:

http://bugzilla.maptools.org/show_bug.cgi?id=2811
Comment 1 Pedro Sampaio 2018-09-17 14:24:40 EDT
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1630006]


Created mingw-libtiff tracking bugs for this issue:

Affects: epel-7 [bug 1630009]
Affects: fedora-all [bug 1630007]
Comment 3 Huzaifa S. Sidhpurwala 2018-09-24 02:11:51 EDT
Analysis:

It seems like the flaw was introduced after libtiff-4.0.9 was released. So this is likely a regression in the unreleased version of libtiff (current git master). Which means that any released versions of the pkg will not be affected.

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