Quick answers
- Is CVE-2016-6223 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2016-6223 being exploited in the wild.
- How severe is CVE-2016-6223?
- Critical severity, with a CVSS score of 9.1, published 23 January 2017.
- Which products and versions are affected?
- libtiff libtiff before 4.0.7.
- Is there a fix for CVE-2016-6223?
- A patch was published on 2016-07-10: Fixed in CVS HEAD revision 1.49 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2016-6223 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2016-6223?
- 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's tif_read.c within the TIFFReadRawStrip1() and TIFFReadRawTile1() functions. The flaw is triggered when a TIFF file contains a 'stripoffset' value that exceeds the maximum value of the tmsize_t type, leading to a negative index in a file-content buffer. A remote attacker can exploit this by providing a malicious TIFF image to an application using the library. Successful exploitation can result in a process crash (Denial of Service) due to accessing unmapped memory or the disclosure of sensitive information from the process heap. The issue was addressed in libtiff version 4.0.7.
Affected products
- libtiff libtiff before 4.0.7
Timeline
- 2016-07-10: patched: Fixed in CVS HEAD revision 1.49
- 2016-07-14: disclosed: CVE assigned via oss-security mailing list
- 2017-01-13: advisory: Debian Security Advisory DSA-3762-1 released
- 2017-01-23: advisory: NVD publication date