CVE-2018-10801 json
TIFFClientOpen in tif_unix.c in LibTIFF 3.8.2 has memory leaks, as demonstrated by bmp2tiff.
published 8y ago modified 4mo ago also EUVD-2018-2870
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
TIFFClientOpen in tif_unix.c in LibTIFF 3.8.2 has memory leaks, as demonstrated by bmp2tiff.
Patch / fix
- tiff Debian 14, Debian 13, Debian 12 4.0.6-3
debian advisories DEBIAN-CVE-2018-10801
Is CVE-2018-10801 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-10801 updated cvss 5.5
libtiff: memory leak in bmp2tiff tool
-
Red Hat Enterprise Linux 5 libtiff Red Hat Enterprise Linux 6 libtiff Red Hat Enterprise Linux 7 libtiff, libtiff-tools Red Hat Enterprise Linux 8 libtiff, libtiff-toolsaffected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.09% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.maptools.org http://bugzilla.maptools.org/show_bug.cgi?id=2790 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-772 Missing Release of Resource after Effective Lifetime
References
-
bugzilla.maptools.org
/show_bug.cgi?id=2790
exploit, issue-tracking, third-party-advisory
Sources
- CVE List CVE-2018-10801
- NVD CVE-2018-10801
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.