Integer overflow in Exiv2
CVE-2017-17725
In Exiv2 0.26, there is an integer overflow leading to a heap-based buffer over-read in the Exiv2::getULong function in types.cpp. Remote attackers can exploit the vulnerability to cause a denial of service via a crafted image file. Note that this vulnerability is different from CVE-2017-14864, which is an invalid memory address dereference.
Vulnerability class: Integer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS: 0.018 (77.6th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 78th percentile — 77.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.018 · newest: 0.018 · change: 0.000
Affected products
- Exiv2 — versions 0.26
Weakness classification (CWE)
Public proof-of-concept exploits
References
- github.com/Exiv2/exiv2/issues/188 (Exploit, Issue Tracking)
- bugzilla.redhat.com/show_bug.cgi (Exploit, Third Party Advisory, Issue Tracking)
Frequently asked questions
- What is CVE-2017-17725?
- CVE-2017-17725 is a medium-severity vulnerability in Exiv2, classified under Integer Overflow or Wraparound. CVSS score: 6.5/10. Published 2018-02-12.
- How severe is CVE-2017-17725?
- Medium severity. CVSS v3 base score is 6.5 out of 10.
- Is CVE-2017-17725 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.