CVE-2018-10963: The TIFFWriteDirectorySec() function in tif_dirwrite.c in LibTIFF through 4.0.9 allows remote attackers to cause a denial of service…
Noroxi assessment
Priority: Monitor (action score 27/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.6% (FIRST EPSS); higher than 89.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: tiff (Alpine:v3.10) 4.0.9-r6; tiff (Alpine:v3.5) 4.0.9-r5; tiff (Debian:12) 4.0.9-6.
Low priority for now. Upgrade to tiff (Alpine:v3.10) 4.0.9-r6; tiff (Alpine:v3.5) 4.0.9-r5; tiff (Debian:12) 4.0.9-6 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
The TIFFWriteDirectorySec() function in tif_dirwrite.c in LibTIFF through 4.0.9 allows remote attackers to cause a denial of service (assertion failure and application crash) via a crafted file, a different vulnerability than CVE-2017-13726.
- Published
- May 9, 2018
- Updated
- Jun 16, 2026
- EPSS
- 3.6% · 89th percentile
- CWE
- CWE-617
Report tools
Action score
27
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.6%
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux14.04
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux18.10
- debian debian linux8.0
- debian debian linux9.0
- libtiff libtiffup to 4.0.9 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | tiff | before 4.0.9-r6 | 4.0.9-r6 |
| Alpine:v3.5 | tiff | before 4.0.9-r5 | 4.0.9-r5 |
| Debian:12 | tiff | before 4.0.9-6 | 4.0.9-6 |
| Debian:8 | tiff | before 4.0.3-12.3+deb8u6 | 4.0.3-12.3+deb8u6 |
| Debian:9 | tiff | before 4.0.8-2+deb9u4 | 4.0.8-2+deb9u4 |
| Red Hat:enterprise_linux:7::client | libtiff | before 0:4.0.3-32.el7 | 0:4.0.3-32.el7 |
| Red Hat:enterprise_linux:7::client | libtiff-debuginfo | before 0:4.0.3-32.el7 | 0:4.0.3-32.el7 |
| Red Hat:enterprise_linux:7::client | libtiff-devel | before 0:4.0.3-32.el7 | 0:4.0.3-32.el7 |
| Red Hat:enterprise_linux:7::client | libtiff-static | before 0:4.0.3-32.el7 | 0:4.0.3-32.el7 |
| Red Hat:enterprise_linux:7::client | libtiff-tools | before 0:4.0.3-32.el7 | 0:4.0.3-32.el7 |
| SUSE:Linux Enterprise Desktop 12 SP3 | tiff | before 4.0.9-44.15.2 | 4.0.9-44.15.2 |
| SUSE:Linux Enterprise Module for Basesystem 15 | tiff | before 4.0.9-5.9.1 | 4.0.9-5.9.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-2018-10779May 7, 2018 · TIFFWriteScanline in tif_write.c in LibTIFF 3.8.2 has a heap-based buffer over-read, as demonstrated by bmp2tiff.27Monitor
- ← EarlierCVE-2018-10801May 8, 2018 · TIFFClientOpen in tif_unix.c in LibTIFF 3.8.2 has memory leaks, as demonstrated by bmp2tiff.26Monitor
- Later →CVE-2018-12900Jun 26, 2018 · Heap-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
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.9-r6 · Alpine:v3.10 | Package registry (OSV) |
| debian:tiff | 4.0.9-6 · Debian:12 | Package registry (OSV) |
| red hat:libtiff | 0:4.0.3-32.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libtiff-debuginfo | 0:4.0.3-32.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libtiff-devel | 0:4.0.3-32.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libtiff-static | 0:4.0.3-32.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:libtiff-tools | 0:4.0.3-32.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:tiff | 4.0.9-44.15.2 · SUSE:Linux Enterprise Desktop 12 SP3 | 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.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-617 · Reachable AssertionCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.