VDB

CVE-2017-9239

CVE-2017-9239 PUBLISHED

Reported by mitre · Published May 26, 2017

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
exiv2Ubuntu:14.04:LTS0.23-1ubuntu2.2
exiv2Ubuntu:16.04:LTS0.25-2.1ubuntu16.04.3

Affected products

VendorProductVersions
n/an/an/a
n/an/a*

Timeline

  • May 26, 2017 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Sep 8, 2025 CVE Updated
  • Mar 6, 2026 Distribution Patch
  • Mar 6, 2026 Security Advisory (4 in total, the first dated here)
  • Sep 27, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-9239
vulnetix vdb fixes CVE-2017-9239

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-9239/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›