CVE-2017-9239 json
An issue was discovered in Exiv2 0.26.
published 2017-05-26 9 y ago modified 2026-06-17 4 mo ago also PYSEC-2017-112 , EUVD-2017-0028
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
An issue was discovered in Exiv2 0.26. When the data structure of the structure ifd is incorrect, the program assigns pValue_ to 0x0, and the value of pValue() is 0x0. TiffImageEntry::doWriteImage will use the value of pValue() to cause a segmentation fault. To exploit this vulnerability, someone must open a crafted tiff file.
Patch / fix
- exiv2 Debian 14, Debian 13, Debian 12 0.25-3.1
debian advisories DEBIAN-CVE-2017-9239
- exiv2 Ubuntu 14.04 LTS 0.23-1ubuntu2.2
- exiv2 Ubuntu 16.04 LTS 0.25-2.1ubuntu16.04.3
ubuntu advisories UBUNTU-CVE-2017-9239
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- exiv2 SLE Module for Desktop Applications 15 SP1 0.26-6.8.1
- exiv2 SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES 12 SP5 +3 more 0.23-12.8.1
suse advisories SUSE-SU-2020:0921-1SUSE-SU-2020:0860-1
- exiv2 openSUSE Tumbleweed 0.27.5-4.1
- exiv2 openSUSE Leap 15.1 0.26-lp151.7.3.1
opensuse advisories openSUSE-SU-2024:12399-1openSUSE-SU-2020:0482-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-9239 updated cvss 3.3
exiv2: Segmentation fault in TiffImageEntry::doWriteImage 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
2.63% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 |
| OSV | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | exiv2 | all versions |
no fix listed |
Classification
- Weakness
-
- CWE-369 Divide By Zero
References
-
usn.ubuntu.com
/3852-1/
vendor-advisory, third-party-advisory, web
-
lists.opensuse.org
/opensuse-security-announce/2020-04/msg00009.html
vendor-advisory, web
-
dev.exiv2.org
/issues/1295
issue-tracking, report
-
securityfocus.com
/bid/98720
vdb-entry, third-party-advisory, advisory
-
github.com
/lolo-pop/poc/tree/master/Segmentation%20fault%20in%20convert-test%28exiv2%29
web
Sources
- CVE List CVE-2017-9239
- NVD CVE-2017-9239
- OSV PYSEC-2017-112
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.