CVE-2015-8668: Heap-based buffer overflow in the PackBitsPreEncode function in tif_packbits.c in bmp2tiff in libtiff 4.0.6 and earlier allows remote…
Noroxi assessment
Priority: Plan (action score 43/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: 13.7% (FIRST EPSS); higher than 96.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.6-3; tiff (Debian:7) 4.0.2-6+deb7u7; libtiff (Red Hat:enterprise_linux:6::client) 0:3.9.4-18.el6_8.
Add it to your regular patch cycle. Upgrade to tiff (Debian:12) 4.0.6-3; tiff (Debian:7) 4.0.2-6+deb7u7; libtiff (Red Hat:enterprise_linux:6::client) 0:3.9.4-18.el6_8 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
Heap-based buffer overflow in the PackBitsPreEncode function in tif_packbits.c in bmp2tiff in libtiff 4.0.6 and earlier allows remote attackers to execute arbitrary code or cause a denial of service via a large width field in a BMP image.
- Published
- Jan 8, 2016
- Updated
- Jun 16, 2026
- EPSS
- 13.7% · 96th percentile
- CWE
- CWE-787
Report tools
Action score
43
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 13.7%
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 |
| oracle | vm server | cpe:2.3:a:oracle:vm_server |
| oracle | linux | cpe:2.3:o:oracle:linux |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libtiff libtiffup to 4.0.6 inclusive
- oracle linux6
- oracle linux7
- oracle vm server3.3
- oracle vm server3.4
- redhat enterprise linux6.0
- redhat enterprise linux7.0
- redhat enterprise linux desktop6.0
+3 more rows
- redhat enterprise linux desktop7.0
- redhat enterprise linux workstation6.0
- redhat enterprise linux workstation7.0
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.6-3 | 4.0.6-3 |
| Debian:7 | tiff | before 4.0.2-6+deb7u7 | 4.0.2-6+deb7u7 |
| Red Hat:enterprise_linux:6::client | libtiff | before 0:3.9.4-18.el6_8 | 0:3.9.4-18.el6_8 |
| Red Hat:enterprise_linux:6::client | libtiff-debuginfo | before 0:3.9.4-18.el6_8 | 0:3.9.4-18.el6_8 |
| Red Hat:enterprise_linux:6::client | libtiff-devel | before 0:3.9.4-18.el6_8 | 0:3.9.4-18.el6_8 |
| Red Hat:enterprise_linux:6::client | libtiff-static | before 0:3.9.4-18.el6_8 | 0:3.9.4-18.el6_8 |
| Red Hat:enterprise_linux:7::client | libtiff | before 0:4.0.3-25.el7_2 | 0:4.0.3-25.el7_2 |
| Red Hat:enterprise_linux:7::client | libtiff-debuginfo | before 0:4.0.3-25.el7_2 | 0:4.0.3-25.el7_2 |
| Red Hat:enterprise_linux:7::client | libtiff-devel | before 0:4.0.3-25.el7_2 | 0:4.0.3-25.el7_2 |
| Red Hat:enterprise_linux:7::client | libtiff-static | before 0:4.0.3-25.el7_2 | 0:4.0.3-25.el7_2 |
| Red Hat:enterprise_linux:7::client | libtiff-tools | before 0:4.0.3-25.el7_2 | 0:4.0.3-25.el7_2 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | tiff | before 3.8.2-141.169.16.1 | 3.8.2-141.169.16.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | tiff | before 4.0.9-44.80.1 | 4.0.9-44.80.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-2018-12900Heap-based buffer overflow in the cpSeparateBufToContigBuf function in tiffcp.c in LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0beta7, 4.42Plan
Published before and after this one in the same product
- ← EarlierCVE-2014-9330Jan 20, 2015 · Integer overflow in tif_packbits.c in bmp2tif in libtiff 4.0.3 allows remote attackers to cause a denial of service (crash) via crafted BMP…21Monitor
- ← EarlierCVE-2015-7554Jan 8, 2016 · The _TIFFVGetField function in tif_dir.c in libtiff 4.0.6 allows attackers to cause a denial of service (invalid memory write and crash) or…40Plan
- Later →CVE-2015-8781Feb 1, 2016 · tif_luv.c in libtiff allows attackers to cause a denial of service (out-of-bounds write) via an invalid number of samples per pixel in a…27Monitor
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.6-3 · Debian:12 | Package registry (OSV) |
| red hat:libtiff | 0:4.0.3-25.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libtiff-debuginfo | 0:4.0.3-25.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libtiff-devel | 0:4.0.3-25.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libtiff-static | 0:4.0.3-25.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libtiff-tools | 0:4.0.3-25.el7_2 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:tiff | 3.8.2-141.169.16.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4 | 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-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.