CVE-2016-9534: tif_write.c in libtiff 4.0.6 has an issue in the error code path of TIFFFlushData1() that didn't reset the tif_rawcc and tif_rawcp members.
Noroxi assessment
Priority: Plan (action score 40/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: 3.5% (FIRST EPSS); higher than 89.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: tiff (Debian:12) 4.0.7-1; tiff (Debian:7) 4.0.2-6+deb7u9; tiff3 (Debian:7) 3.9.6-11+deb7u4.
Add it to your regular patch cycle. Upgrade to tiff (Debian:12) 4.0.7-1; tiff (Debian:7) 4.0.2-6+deb7u9; tiff3 (Debian:7) 3.9.6-11+deb7u4 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
tif_write.c in libtiff 4.0.6 has an issue in the error code path of TIFFFlushData1() that didn't reset the tif_rawcc and tif_rawcp members. Reported as MSVR 35095, aka "TIFFFlushData1 heap-buffer-overflow."
- Published
- Nov 22, 2016
- Updated
- Jun 16, 2026
- EPSS
- 3.5% · 89th percentile
- CWE
- CWE-119
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.5%
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 |
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 |
|---|---|---|---|
| Debian:12 | tiff | before 4.0.7-1 | 4.0.7-1 |
| Debian:7 | tiff | before 4.0.2-6+deb7u9 | 4.0.2-6+deb7u9 |
| Debian:7 | tiff3 | before 3.9.6-11+deb7u4 | 3.9.6-11+deb7u4 |
| 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 |
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-8331Oct 28, 2016 · An exploitable remote code execution vulnerability exists in the handling of TIFF images in LibTIFF version 4.0.6.34Monitor
- ← EarlierCVE-2016-9533Nov 22, 2016 · tif_pixarlog.c in libtiff 4.0.6 has out-of-bounds write vulnerabilities in heap allocated buffers.40Plan
- Later →CVE-2016-9535Nov 22, 2016 · tif_predict.h and tif_predict.c in libtiff 4.0.6 have assertions that can lead to assertion failures in debug mode, or buffer overflows in…40Plan
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 |
|---|---|---|
| debian:tiff | 4.0.7-1 · Debian:12 | Package registry (OSV) |
| debian:tiff3 | 3.9.6-11+deb7u4 · Debian:7 | 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) |
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- 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:N/AC:L/PR:N/UI:N/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.