CVE-2016-9453: LibTIFF out-of-bounds write in tiff2pdf

CVE-2016-9453 · Severity: high · CVSS 7.8 · Published 2017-01-27

LibTIFF is a widely used software library for handling TIFF image files. A vulnerability in its tiff2pdf tool could allow an attacker to crash applications or potentially execute unauthorized code if a user is tricked into opening a specially crafted, malicious image file. This could lead to a loss of system availability or a compromise of the user's workstation.

Technologies: Libtiff. Vendors: Libtiff.

Quick answers

Is CVE-2016-9453 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-9453 being exploited in the wild.
How severe is CVE-2016-9453?
High severity, with a CVSS score of 7.8, published 27 January 2017.
Which products and versions are affected?
Libtiff up to (excluding) 4.0.7.
Is there a fix for CVE-2016-9453?
A patch was published on 2016-10-08: Fix committed to LibTIFF source code Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2016-9453 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2016-9453?
Check whether you run Libtiff at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An out-of-bounds write vulnerability exists in the t2p_readwrite_pdf_image_tile function within LibTIFF's tiff2pdf tool. The flaw is triggered when processing a JPEG-compressed TIFF image where the TIFFTAG_JPEGTABLES tag has a length of one. This causes an incorrect buffer offset calculation during a memcpy operation, leading to a heap-based out-of-bounds write. An attacker can exploit this by providing a malicious file to a user, potentially achieving arbitrary code execution or causing a denial of service (crash). The issue was addressed in LibTIFF version 4.0.7.

Affected products

  • LibTIFF LibTIFF up to (excluding) 4.0.7

Timeline

  • 2016-09-28: disclosed: Initial report to LibTIFF bugzilla
  • 2016-10-08: patched: Fix committed to LibTIFF source code
  • 2017-01-27: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.