CVE-2017-14860 json
There is a heap-based buffer over-read in the Exiv2::Jp2Image::readMetadata function of jp2image.cpp in Exiv2 0.26.
published 2017-09-28 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-0047
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
There is a heap-based buffer over-read in the Exiv2::Jp2Image::readMetadata function of jp2image.cpp in Exiv2 0.26. A Crafted input will lead to a denial of service attack.
Patch / fix
- exiv2 SLE Module for Desktop Applications 15 0.26-6.3.1
suse advisories SUSE-SU-2018:1882-1
- exiv2 openSUSE Tumbleweed 0.27.4-1.2
opensuse advisories openSUSE-SU-2024:10747-1
Vendor 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-14860 updated cvss 3.3
exiv2: Heap-based buffer over-read in the Exiv2::Jp2Image::readMetadata function
-
Red Hat Enterprise Linux 6 exiv2, exiv2-libs Red Hat Enterprise Linux 7 exiv2, exiv2-libsaffected: 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
0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1494776 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/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-125 Out-of-bounds Read
References
-
bugzilla.redhat.com
/show_bug.cgi?id=1494776
exploit, issue-tracking, third-party-advisory
Sources
- CVE List CVE-2017-14860
- NVD CVE-2017-14860
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.