Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1389229 - (CVE-2016-8331) CVE-2016-8331 libtiff: FAX IFD Entry Parsing Type Confusion
CVE-2016-8331 libtiff: FAX IFD Entry Parsing Type Confusion
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=20161025,repor...
: Security
Depends On: 1389233 1389231 1389232
Blocks: 1389235
  Show dependency treegraph
 
Reported: 2016-10-27 04:44 EDT by Andrej Nemec
Modified: 2017-01-20 00:25 EST (History)
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-01-17 03:46:20 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 Andrej Nemec 2016-10-27 04:44:58 EDT
An exploitable remote code execution vulnerability exists in the handling of TIFF images in LibTIFF. A crafted TIFF document can lead to a type confusion vulnerability resulting in remote code execution. This vulnerability can be triggered via a TIFF file delivered to the application using LibTIFF’s tag extension functionality.

External References:

http://www.talosintelligence.com/reports/TALOS-2016-0190
Comment 1 Andrej Nemec 2016-10-27 04:47:33 EDT
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1389231]
Comment 2 Andrej Nemec 2016-10-27 04:47:39 EDT
Created mingw-libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1389232]
Affects: epel-7 [bug 1389233]
Comment 3 Huzaifa S. Sidhpurwala 2016-11-07 01:06:52 EST
Analysis:

The flaw is possibly caused by expecting a double value on the argument list, va_arg and there is none. This results in a possible sizeof(double) OOB read/write. This may result in a crash, or a difficult to pull off code exec.
Comment 8 Nikola Forró 2017-01-17 03:34:30 EST
Analysis:

The reproducer reads BadFaxLines tag like this:

uint32 *a;
TiffGetField(tiff, TIFFTAG_BADFAXLINES, &a);

Despite the documentation, which says:

Tag Name            Count   Types
TIFFTAG_BADFAXLINES 1       uint32*

the correct way how to read the tag is this:

uint32 count;
uint16 *values;
TIFFGetField(tiff, TIFFTAG_BADFAXLINES, &count, &values);

That is because TIFFTAG_BADFAXLINES is considered an anonymous custom tag, and as such is has to be read as count and array of values.

The reproducer does exactly what thumbnail utility is doing when it is processing BadFaxLines tag. However, processing this tag has been disabled in RHEL with patch for CVE-2016-3632. That means RHEL packages are not affected.

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