Bug 1630004 (CVE-2018-17000)

Summary: CVE-2018-17000 libtiff: NULL pointer dereference in function _TIFFmemcmp at tif_unix.c
Product: [Other] Security Response Reporter: Pedro Sampaio <psampaio>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: abhgupta, ahardin, bleanhar, ccoleman, darunesh, dbaker, dedgar, erik-fedora, jgoulding, mchappel, mike, nforro, phracek, rh-spice-bugs, sthangav, tgl, trankin
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-24 06:15:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1630006, 1630007, 1630009, 1630010, 1630011    
Bug Blocks: 1630008, 1679012    

Description Pedro Sampaio 2018-09-17 18:23:43 UTC 
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 18:24:40 UTC 
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 06:11:51 UTC 
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.
Comment 4 Stefan Cornelius 2020-03-06 13:21:14 UTC 
*** Bug 1677528 has been marked as a duplicate of this bug. ***