# CVE-2017-9953: Use after free in n/a

> A use-after-free vulnerability in Exiv2 allows remote attackers to cause a denial of service via crafted image files.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8399-fj6c-9hf7

## What is CVE-2017-9953?

CVE-2017-9953 is a high-severity use after free vulnerability in Exiv2 Exiv2, published on 26 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is an invalid free in Image::printIFDStructure that leads to a Segmentation fault in Exiv2 0.26. A crafted input will lead to a remote denial of service attack.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2017-9953?

It affects 2 products.


Products: Exiv2 Exiv2, Redhat Enterprise Linux.

## How do I fix CVE-2017-9953?

No fix has been published for CVE-2017-9953 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-9953 being exploited?

There is no known exploitation of CVE-2017-9953 in the wild and no public exploit code.

## Other vulnerabilities in Exiv2 Exiv2

- [CVE-2023-44398](https://insights.sbomify.com/CVE-2023-44398/): Out-of-bounds write in exiv2 (high 8.8)
- [CVE-2019-9143](https://insights.sbomify.com/CVE-2019-9143/): Denial of service in n/a (high 8.8)
- [CVE-2019-9144](https://insights.sbomify.com/CVE-2019-9144/): Denial of service in n/a (high 8.8)
- [CVE-2018-14046](https://insights.sbomify.com/CVE-2018-14046/): Memory corruption in n/a (high 8.8)
- [CVE-2017-12955](https://insights.sbomify.com/CVE-2017-12955/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9953 and fix it if it is affected.

What it is: CVE-2017-9953 is a high-severity use after free vulnerability in Exiv2 Exiv2, published on 26 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9953 in the wild and no public exploit code.

Affected product: Exiv2 Exiv2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9953/ (Markdown: https://insights.sbomify.com/CVE-2017-9953/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9953
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9953
- OSV: https://osv.dev/vulnerability/CVE-2017-9953

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9953/
Summaries are generated and may contain mistakes; the official description above is the record.