CVE-2016-9532: Integer Overflow

Published Nov 23, 2016
·
Updated

Integer overflow in the writeBufferToSeparateStrips function in tiffcrop.c in LibTIFF before 4.0.7 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted tif file.

Other sources

Multiple integer overflows were found in writeBufferToSeparateStrips(), writeBufferToContigTiles() and writeBufferToSeparateTiles() that could lead to out-of-bounds heap read.

Upstream bug:

http://bugzilla.maptools.org/showbug.cgi?id=2592

CVE assignment:

http://seclists.org/oss-sec/2016/q4/487

Red Hat

Affected Software

3 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.6
Debian Debian Linux=8.0

Event History

Nov 23, 2016
Data Sourced
via Red Hat·09:30 AM
DescriptionSeverityAffected Software
Feb 6, 2017
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Data Sourced
via NVD·05:59 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2016-9532?

CVE-2016-9532 is classified as a denial of service vulnerability due to integer overflow leading to out-of-bounds reads.

2

How do I fix CVE-2016-9532?

To fix CVE-2016-9532, you should upgrade to LibTIFF version 4.0.7 or later.

3

What software is affected by CVE-2016-9532?

CVE-2016-9532 affects versions of LibTIFF prior to 4.0.7, including the tiff package on Debian systems.

4

Can CVE-2016-9532 be exploited remotely?

Yes, CVE-2016-9532 can be exploited remotely by attackers using crafted tif files.

5

What functions are involved in CVE-2016-9532?

The vulnerability lies in the writeBufferToSeparateStrips and writeBufferToContigTiles functions in tiffcrop.c.

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