Bug 1464449 – CVE-2017-9815 libtiff: Memory leak in the TIFFReadDirEntryLong8Array function

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1464449 - (CVE-2017-9815) CVE-2017-9815 libtiff: Memory leak in the TIFFReadDirEntryLong8Array function

Summary:	CVE-2017-9815 libtiff: Memory leak in the TIFFReadDirEntryLong8Array function

Status:	CLOSED WONTFIX

Aliases:	CVE-2017-9815

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=low,public=20170622,reported=2...
Keywords:	Security

Depends On:	1464450
Blocks:
	Show dependency tree / graph

Reported:	2017-06-23 08:46 EDT by Pedro Sampaio
Modified:	2017-06-23 09:13 EDT (History)
CC List:	2 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-06-23 08:49:13 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)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Pedro Sampaio 2017-06-23 08:46:24 EDT

In LibTIFF 4.0.7, the TIFFReadDirEntryLong8Array function in
libtiff/tif_dirread.c mishandles a malloc operation, which allows
attackers to cause a denial of service (memory leak within the function
_TIFFmalloc in tif_unix.c) via a crafted file.

Upstream bug:
http://bugzilla.maptools.org/show_bug.cgi?id=2682

Comment 1 Pedro Sampaio 2017-06-23 08:46:32 EDT

External References:

http://somevulnsofadlab.blogspot.com.br/2017/06/libtiffmemory-leak-in-tiffmalloc.html

Comment 2 Pedro Sampaio 2017-06-23 08:46:56 EDT

Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1464450]

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