Quick answers
- Is CVE-2016-9297 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2016-9297 being exploited in the wild.
- How severe is CVE-2016-9297?
- High severity, with a CVSS score of 7.5, published 18 January 2017.
- Which products and versions are affected?
- LibTiff LibTiff 4.0.6.
- Is there a fix for CVE-2016-9297?
- A patch was published on 2016-11-11: Fix committed to LibTiff source repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2016-9297 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2016-9297?
- Check whether you run Libtiff. 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 read vulnerability exists in LibTiff 4.0.6 within the TIFFFetchNormalTag function in tif_dirread.c. The issue stems from a failure to ensure that certain ASCII tags (specifically TIFF_SETGET_C16ASCII and TIFF_SETGET_C32_ASCII) are properly null-terminated. When these malformed tags are processed, subsequent calls to _TIFFPrintField() may read past the end of the allocated buffer. A remote attacker can exploit this by providing a specially crafted TIFF image, leading to an application crash (denial of service). The vulnerability was addressed in version 4.0.7 by ensuring proper null termination of these tag values.
Affected products
- LibTiff LibTiff 4.0.6
Timeline
- 2016-11-11: patched: Fix committed to LibTiff source repository
- 2017-01-13: advisory: Debian security advisory DSA-3762-1 released
- 2017-01-18: disclosed: NVD publication date