CVE-2016-5652: An exploitable heap-based buffer overflow exists in the handling of TIFF images in LibTIFF's TIFF2PDF tool.
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.1% (FIRST EPSS); higher than 91% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: tiff (Alpine:v3.2) 4.0.7-r0; tiff (Debian:12) 4.0.6-3; tiff (Debian:7) 4.0.2-6+deb7u7.
Low priority for now. Upgrade to tiff (Alpine:v3.2) 4.0.7-r0; tiff (Debian:12) 4.0.6-3; tiff (Debian:7) 4.0.2-6+deb7u7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An exploitable heap-based buffer overflow exists in the handling of TIFF images in LibTIFF's TIFF2PDF tool. A crafted TIFF document can lead to a heap-based buffer overflow resulting in remote code execution. Vulnerability can be triggered via a saved TIFF file delivered by other means.
- Published
- Jan 6, 2017
- Updated
- Jun 16, 2026
- EPSS
- 4.1% · 91th percentile
- CWE
- CWE-119
Report tools
Action score
29
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libtiff | libtiff | cpe:2.3:a:libtiff:libtiff |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (certcc). Independent of NVD's CPE analysis and usually ahead of it.
LibTiff LibTiff
- 4.0.6affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libtiff libtiff4.0.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.2 | tiff | before 4.0.7-r0 | 4.0.7-r0 |
| Debian:12 | tiff | before 4.0.6-3 | 4.0.6-3 |
| Debian:7 | tiff | before 4.0.2-6+deb7u7 | 4.0.2-6+deb7u7 |
| Debian:8 | tiff | before 4.0.3-12.3+deb8u2 | 4.0.3-12.3+deb8u2 |
| Red Hat:enterprise_linux:6::client | libtiff | before 0:3.9.4-21.el6_8 | 0:3.9.4-21.el6_8 |
| Red Hat:enterprise_linux:6::client | libtiff-debuginfo | before 0:3.9.4-21.el6_8 | 0:3.9.4-21.el6_8 |
| Red Hat:enterprise_linux:6::client | libtiff-devel | before 0:3.9.4-21.el6_8 | 0:3.9.4-21.el6_8 |
| Red Hat:enterprise_linux:6::client | libtiff-static | before 0:3.9.4-21.el6_8 | 0:3.9.4-21.el6_8 |
| Red Hat:enterprise_linux:7::client | libtiff | before 0:4.0.3-27.el7_3 | 0:4.0.3-27.el7_3 |
| Red Hat:enterprise_linux:7::client | libtiff-debuginfo | before 0:4.0.3-27.el7_3 | 0:4.0.3-27.el7_3 |
| Red Hat:enterprise_linux:7::client | libtiff-devel | before 0:4.0.3-27.el7_3 | 0:4.0.3-27.el7_3 |
| Red Hat:enterprise_linux:7::client | libtiff-static | before 0:4.0.3-27.el7_3 | 0:4.0.3-27.el7_3 |
| Red Hat:enterprise_linux:7::client | libtiff-tools | before 0:4.0.3-27.el7_3 | 0:4.0.3-27.el7_3 |
| SUSE:Linux Enterprise Desktop 12 SP1 | tiff | before 4.0.7-35.1 | 4.0.7-35.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | tiff | before 3.8.2-141.169.3.1 | 3.8.2-141.169.3.1 |
Same product
libtiff: all recordsOther highest-scoring records for the same primary product.
- CVE-2006-3459Multiple stack-based buffer overflows in the TIFF library (libtiff) before 3.8.2, as used in Adobe Reader 9.3.0 and other products, allow…47Plan
- CVE-2004-1308Integer overflow in (1) tif_dirread.c and (2) tif_fax3.c for libtiff 3.5.7 and 3.7.0 allows remote attackers to execute arbitrary code via…44Plan
- CVE-2015-8668Heap-based buffer overflow in the PackBitsPreEncode function in tif_packbits.c in bmp2tiff in libtiff 4.0.6 and earlier allows remote…43Plan
Published before and after this one in the same product
- ← EarlierCVE-2016-9540Nov 22, 2016 · tools/tiffcp.c in libtiff 4.0.6 has an out-of-bounds write on tiled images with odd tile width versus image width.40Plan
- ← EarlierCVE-2015-8870Dec 6, 2016 · Integer overflow in tools/bmp2tiff.c in LibTIFF before 4.0.4 allows remote attackers to cause a denial of service (heap-based buffer…30Monitor
- Later →CVE-2017-5225Jan 12, 2017 · LibTIFF version 4.0.7 is vulnerable to a heap buffer overflow in the tools/tiffcp resulting in DoS or code execution via a crafted…36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:tiff | 4.0.7-r0 · Alpine:v3.2 | Package registry (OSV) |
| debian:tiff | 4.0.6-3 · Debian:12 | Package registry (OSV) |
| red hat:libtiff | 0:3.9.4-21.el6_8 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libtiff-debuginfo | 0:3.9.4-21.el6_8 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libtiff-devel | 0:3.9.4-21.el6_8 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libtiff-static | 0:3.9.4-21.el6_8 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libtiff-tools | 0:4.0.3-27.el7_3 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:tiff | 4.0.7-35.1 · SUSE:Linux Enterprise Desktop 12 SP1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.