Bug 1265998 (CVE-2015-7313) - CVE-2015-7313 libtiff: OOM when parsing crafted tiff files
Summary: CVE-2015-7313 libtiff: OOM when parsing crafted tiff files
Alias: CVE-2015-7313
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1265999 1266000
Blocks: 1266001
TreeView+ depends on / blocked
Reported: 2015-09-24 09:36 UTC by Martin Prpič
Modified: 2019-09-29 13:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-10-07 13:49:58 UTC

Attachments (Terms of Use)

Description Martin Prpič 2015-09-24 09:36:53 UTC
A denial of service flaw was found in the way libtiff parsed certain tiff files. An attacker could use this flaw to create a specially crafted TIFF file that would cause an application using libtiff to exhaust all available memory on the system.

Original report:


Comment 1 Martin Prpič 2015-09-24 09:37:49 UTC
Created libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1265999]

Comment 2 Martin Prpič 2015-09-24 09:37:54 UTC
Created mingw-libtiff tracking bugs for this issue:

Affects: fedora-all [bug 1266000]

Comment 3 Stefan Cornelius 2015-10-07 10:48:48 UTC
On Fedora and RHEL7, disabling memory overcommit (echo 2 > /proc/sys/vm/overcommit_memory) seems to "fix" this issue. Thus, there is nothing wrong with the libtiff code. Instead, the memory overcommit will prevent certain memory errors to be passed to the libtiff code, ultimately "bypassing" the libtiff error checks, leading to an OOM kill instead of a libtiff exit.

On RHEL6, it detects and integer overflow and exits:
TIFFReadDirectory: Warning, oom.tif: Bogus "StripByteCounts" field, ignoring and calculating from imagelength.
oom.tif: Integer overflow in TIFFVStripSize.
TIFFReadDirectory: oom.tif: cannot handle zero strip size.

Comment 4 Federico Leva 2015-10-26 14:45:28 UTC
A variant with "bus error" was seen libtiff 3.4 http://markmail.org/message/igqy46wj7kzhnkjv

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