Stack-based buffer overflow in the tiffsplit command in libtiff 3.8.2 and earlier might might allow attackers to execute arbitrary code via
Stack-based buffer overflow in the tiffsplit command in libtiff 3.8.2 and earlier might might allow attackers to execute arbitrary code via a long filename. NOTE: tiffsplit is not setuid. If there is not a common scenario under which tiffsplit is called with attacker-controlled command line arguments, then perhaps this issue should not be included in CVE.
- Published
- May 30, 2006
- Updated
- Sep 23, 2026
- EPSS
- 14.4% · 97th percentile
- CWE
- CWE-119
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 14.4%
Affected systems
| 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 libtiffup to 3.8.2 inclusive
- libtiff libtiff3.4
- libtiff libtiff3.5.1
- libtiff libtiff3.5.2
- libtiff libtiff3.5.3
- libtiff libtiff3.5.4
- libtiff libtiff3.5.5
- libtiff libtiff3.5.6
- libtiff libtiff3.5.7
- libtiff libtiff3.6.0
- libtiff libtiff3.6.1
- libtiff libtiff3.7.0
- libtiff libtiff3.7.1
- libtiff libtiff3.8.0
- libtiff libtiff3.8.1
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 3.8.2-3 | 3.8.2-3 |
| Debian:3.0 | tiff | before 3.5.5-7woody2 | 3.5.5-7woody2 |
| Debian:3.1 | tiff | before 3.7.2-5 | 3.7.2-5 |
| openSUSE:Tumbleweed | tiff | before 4.3.0-1.3 | 4.3.0-1.3 |
| Red Hat:enterprise_linux:3::as | libtiff | before 0:3.5.7-25.el3.4 | 0:3.5.7-25.el3.4 |
| Red Hat:enterprise_linux:3::as | libtiff-debuginfo | before 0:3.5.7-25.el3.4 | 0:3.5.7-25.el3.4 |
| Red Hat:enterprise_linux:3::as | libtiff-devel | before 0:3.5.7-25.el3.4 | 0:3.5.7-25.el3.4 |
| Red Hat:enterprise_linux:4::as | libtiff | before 0:3.6.1-12 | 0:3.6.1-12 |
| Red Hat:enterprise_linux:4::as | libtiff-debuginfo | before 0:3.6.1-12 | 0:3.6.1-12 |
| Red Hat:enterprise_linux:4::as | libtiff-devel | before 0:3.6.1-12 | 0:3.6.1-12 |
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 co46Plan
- 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 a44Plan
- 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.43Plan
- 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 attack43Plan
- CVE-2004-0929Heap-based buffer overflow in the OJPEGVSetField function in tif_ojpeg.c for libtiff 3.6.1 and earlier, when compiled with the OJPEG_SUPPORT42Plan
- CVE-2016-9540tools/tiffcp.c in libtiff 4.0.6 has an out-of-bounds write on tiled images with odd tile width versus image width.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 | 3.8.2-3 · Debian:12 | Package registry (OSV) |
| opensuse:tiff | 4.3.0-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:libtiff | 0:3.5.7-25.el3.4 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libtiff-debuginfo | 0:3.5.7-25.el3.4 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:libtiff-devel | 0:3.5.7-25.el3.4 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | local | 2006-05-26 |
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.
- First PoC-5 d
- Published
- TodaySep 30, 2026+7428 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
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
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- lists.suse.com/archive/suse-security-announce/2006-Jun/0008.html
- marc.info/?l=vuln-dev&m=114857412916909&w=2
- secunia.com/advisories/20501
- secunia.com/advisories/20520
- secunia.com/advisories/20766
- secunia.com/advisories/21002
- security.gentoo.org/glsa/glsa-200607-03.xml
- www.debian.org/security/2006/dsa-1091
- www.mandriva.com/security/advisories?name=MDKSA-2006:095
- usn.ubuntu.com/289-1/
- www.redhat.com/archives/fedora-package-announce/2006-May/msg00127.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.