CVE-2017-17973 json
In LibTIFF 4.0.8, there is a heap-based use-after-free in the t2p_writeproc function in tiff2pdf.c.
published 8y ago modified 4mo ago also EUVD-2017-9115
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
In LibTIFF 4.0.8, there is a heap-based use-after-free in the t2p_writeproc function in tiff2pdf.c. NOTE: there is a third-party report of inability to reproduce this issue
Patch / fix
- tiff SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 +1 more 4.0.9-44.10.1
- tiff SLES for SAP 11 SP4, SLES 11 SP4, SLE Software Development Kit 11 SP4 3.8.2-141.169.3.1
suse advisories SUSE-SU-2018:1180-1SUSE-SU-2018:1179-1
Is CVE-2017-17973 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-2017-17973 updated cvss 7.5
libtiff: heap-based use after free in tiff2pdf.c:t2p_writeproc
-
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-tools Red Hat Enterprise Linux 9 libtiff, libtiff-toolsnot affected: vulnerable code not present
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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
3.05% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.maptools.org http://bugzilla.maptools.org/show_bug.cgi?id=2769 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
bugzilla.maptools.org
/show_bug.cgi?id=2769
exploit, issue-tracking, third-party-advisory
- bugzilla.novell.com /show_bug.cgi?id=1074318
-
securityfocus.com
/bid/102331
vdb-entry, third-party-advisory
- bugzilla.redhat.com /show_bug.cgi?id=1530912
Sources
- CVE List CVE-2017-17973
- NVD CVE-2017-17973
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.