Bug 1397755 – CVE-2016-9535 libtiff: Predictor heap-buffer-overflow

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

Bug 1397755 - (CVE-2016-9535) CVE-2016-9535 libtiff: Predictor heap-buffer-overflow

Summary:	CVE-2016-9535 libtiff: Predictor heap-buffer-overflow

Status:	CLOSED ERRATA

Aliases:	CVE-2016-9535

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

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

URL:
Whiteboard:	impact=moderate,public=20161104,repor...
Keywords:	Security

Depends On:	1397783 1397781 1397782 1412078 1412079 1412080 1412081
Blocks:	1389235
	Show dependency tree / graph

Reported:	2016-11-23 05:14 EST by Adam Mariš
Modified:	2017-02-01 05:19 EST (History)
CC List:	6 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-02-01 05:19:23 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:0225	normal	SHIPPED_LIVE	Moderate: libtiff security update	2017-02-01 10:03:24 EST

Groups: None (edit)

Description Adam Mariš 2016-11-23 05:14:48 EST

It was found that tif_predict.h and tif_predict.c in libtiff 4.0.6 have assertions that can lead to assertion failures in debug mode, or buffer overflows in release mode, when dealing with unusual tile size like YCbCr with subsampling.

Upstream patch:

https://github.com/vadz/libtiff/commit/83a4b92815ea04969d494416eaae3d4c6b338e4a#diff-5be5ce02d0dea67050d5b2a10102d1ba

Comment 1 Adam Mariš 2016-11-23 05:56:15 EST

Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1397781]

Comment 2 Adam Mariš 2016-11-23 05:56:21 EST

Created mingw-libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1397782]
Affects: epel-7 [bug 1397783]

Comment 5 Miroslav Hradílek 2017-01-11 10:54:05 EST

Hi Adam,

is the link correct? https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9535 mentions the two commits:
https://github.com/vadz/libtiff/commit/3ca657a8793dd011bf869695d72ad31c779c3cc1
https://github.com/vadz/libtiff/commit/6a984bf7905c6621281588431f384e79d11a2e33

Comment 6 Huzaifa S. Sidhpurwala 2017-01-16 01:40:36 EST

(In reply to Miroslav Hradílek from comment #5)
> Hi Adam,
> 
> is the link correct?
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9535 mentions the
> two commits:
> https://github.com/vadz/libtiff/commit/
> 3ca657a8793dd011bf869695d72ad31c779c3cc1
> https://github.com/vadz/libtiff/commit/
> 6a984bf7905c6621281588431f384e79d11a2e33

The above links are correct, the ones mentioned in comment #0 seem to be wrong.

Comment 7 errata-xmlrpc 2017-02-01 05:04:11 EST

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7
  Red Hat Enterprise Linux 6

Via RHSA-2017:0225 https://rhn.redhat.com/errata/RHSA-2017-0225.html

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