CVE-2017-17723 json
In Exiv2 0.26, there is a heap-based buffer over-read in the Exiv2::Image::byteSwap4 function in image.cpp.
published 2018-02-12 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-0047
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
In Exiv2 0.26, there is a heap-based buffer over-read in the Exiv2::Image::byteSwap4 function in image.cpp. Remote attackers can exploit this vulnerability to disclose memory data or cause a denial of service via a crafted TIFF file.
Patch / fix
- exiv2 Arch Linux 0.27.1-1
arch linux advisories AVG-614
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-17723 updated cvss 4.4
exiv2: heap-based buffer over-read in Exiv2::Image::byteSwap4 in image.cpp
-
Red Hat Enterprise Linux 6 exiv2, exiv2-libs Red Hat Enterprise Linux 7 exiv2, exiv2-libs Red Hat Enterprise Linux 8 exiv2, exiv2-libsnot 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
Exploit prediction
1.80% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1524104 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:N/A:P |
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
bugzilla.redhat.com
/show_bug.cgi?id=1524104
exploit, issue-tracking, third-party-advisory
-
security.gentoo.org
/glsa/201811-14
vendor-advisory
Sources
- CVE List CVE-2017-17723
- NVD CVE-2017-17723
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.