CVE-2014-8129: Integer Overflow

Published Jan 26, 2015
·
Updated

LibTIFF 4.0.3 allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via a crafted TIFF image, as demonstrated by failure of tifnext.c to verify that the BitsPerSample value is 2, and the t2psamplelabsignedtounsigned function in tiff2pdf.c.

Other sources

Out-of-bounds read/write was reported in tiff2pdf libtiff tool:

- CVE-2014-8129 libtiff: Out-of-bounds Read & Write in the tiff2pdf tool http://bugzilla.maptools.org/showbug.cgi?id=2487 - CVE-2014-8129 libtiff: Out-of-bounds Read & Write in the tiff2pdf tool http://bugzilla.maptools.org/showbug.cgi?id=2488

Above upstream bugs were fixed by the below commits:

2014-12-21 Even Rouault <even.rouault> libtiff/tifnext.c: check that BitsPerSample = 2. Fixes http://bugzilla.maptools.org/showbug.cgi?id=2487 (CVE-2014-8129)

2014-12-21 Even Rouault <even.rouault> Fix various crasher bugs on fuzzed images. libtiff/tifdir.c: TIFFSetField(): refuse to set negative values for TIFFTAGXRESOLUTION and TIFFTAGYRESOLUTION that cause asserts when writing the directory libtiff/tifdirread.c: TIFFReadDirectory(): refuse to read ColorMap or TransferFunction if BitsPerSample has not yet been read, otherwise reading it later will cause user code to crash if BitsPerSample > 1 libtiff/tifgetimage.c: TIFFRGBAImageOK(): return FALSE if LOGLUV with SamplesPerPixel != 3, or if CIELAB with SamplesPerPixel != 3 or BitsPerSample != 8 libtiff/tifnext.c: in the "run mode", use tilewidth for tiled images instead of imagewidth to avoid crash tools/bmp2tiff.c: fix crash due to int overflow related to input BMP dimensions tools/tiff2pdf.c: fix crash due to invalid tile count (should likely be checked by libtiff too). Detect invalid settings of BitsPerSample/SamplesPerPixel for CIELAB / ITULAB tools/tiffcrop.c: fix crash due to invalid TileWidth/TileHeight tools/tiffdump.c: fix crash due to overflow of entry count.

Red Hat

Affected Software

22 affected componentsFixes available
debian/tiff
4.1.0+git191117-2~deb10u44.1.0+git191117-2~deb10u84.2.0-1+deb11u44.5.0-64.5.1+git230720-1
LibTIFF libtiff=4.0.3
Debian Debian Linux=7.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.2
redhat Enterprise Linux Server Aus=7.3
redhat Enterprise Linux Server Aus=7.4
redhat Enterprise Linux Server Eus=7.2
redhat Enterprise Linux Server Eus=7.3
redhat Enterprise Linux Server Eus=7.4
redhat Enterprise Linux Server Tus=7.2
redhat Enterprise Linux Server Tus=7.3
Apple iOS and macOS=10.8.5
Apple iOS and macOS=10.9.5
Apple iOS and macOS=10.10.0
Apple iOS and macOS=10.10.1
Apple iOS and macOS=10.10.2
Apple iOS and macOS=10.10.3
Apple iPhone OS
Apple iPhone OS
Apple iPhone OS

Event History

Jan 26, 2015
Data Sourced
via Red Hat·11:10 AM
DescriptionSeverityAffected Software
Mar 12, 2018
CVE Published
via MITRE·02:00 AM
Data Sourced
via MITRE·02:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2014-8129?

CVE-2014-8129 has a severity rating of medium due to its potential for causing denial of service.

2

How do I fix CVE-2014-8129?

To fix CVE-2014-8129, upgrade to LibTIFF version 4.1.0 or later as specified in your package manager's updates.

3

What types of systems are affected by CVE-2014-8129?

CVE-2014-8129 affects systems that utilize LibTIFF version 4.0.3, including various Debian and Red Hat distributions.

4

What potential impacts are associated with CVE-2014-8129?

The impacts associated with CVE-2014-8129 include denial of service from an out-of-bounds write when processing crafted TIFF images.

5

Are there any exploits known for CVE-2014-8129?

There are no publicly known exploits specifically targeting CVE-2014-8129 reported at this time.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203