CVE-2016-10092: Buffer Overflow
First published: Wed Mar 01 2017(Updated: )
Heap-based buffer overflow in the readContigStripsIntoBuffer function in tif_unix.c in LibTIFF 4.0.7, 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6, 4.0.0beta7, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.4beta, 4.0.5 and 4.0.6 allows remote attackers to have unspecified impact via a crafted image.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/tiff | 4.1.0+git191117-2~deb10u4 4.1.0+git191117-2~deb10u8 4.2.0-1+deb11u4 4.5.0-6 4.5.1+git230720-1 | |
| TIFF | =4.0.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://bugzilla.maptools.org/show_bug.cgi?id=2620
- https://github.com/vadz/libtiff/commit/9657bbe3cdce4aaa90e07d50c1c70ae52da0ba6a
- https://security-tracker.debian.org/tracker/CVE-2016-10092
- http://bugzilla.maptools.org/show_bug.cgi?id=2622
- http://www.debian.org/security/2017/dsa-3762
- http://www.openwall.com/lists/oss-security/2017/01/01/10
- http://www.openwall.com/lists/oss-security/2017/01/01/12
- http://www.securityfocus.com/bid/95218
- https://blogs.gentoo.org/ago/2017/01/01/libtiff-multiple-heap-based-buffer-overflow/
- https://github.com/Hack-Me/Pocs_for_Multi_Versions/tree/main/CVE-2016-10092
Frequently Asked Questions
What is the severity of CVE-2016-10092?
CVE-2016-10092 is classified as a high severity vulnerability due to the potential for remote code execution.
How do I fix CVE-2016-10092?
To fix CVE-2016-10092, update to a patched version of LibTIFF, specifically version 4.1.0 or later.
What impact does CVE-2016-10092 have on my system?
CVE-2016-10092 can allow remote attackers to exploit a heap-based buffer overflow, leading to possible arbitrary code execution.
Which versions of LibTIFF are affected by CVE-2016-10092?
Versions of LibTIFF from 4.0.7 to 4.0.6, among others, are affected by CVE-2016-10092.
Is LibTIFF used in any common applications that may be vulnerable due to CVE-2016-10092?
Yes, LibTIFF is commonly used in image processing applications, making them potentially vulnerable if they use affected versions.
- collector/security-tracker-debian
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/references
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- package-manager/debian
- vendor/libtiff
- canonical/tiff
- version/tiff/4.0.7