# CVE-2015-4696: Use after free in n/a

> Remote attackers can cause a denial of service via crafted WMF files processed by libwmf utilities, requiring user interaction to open the file.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-4696, GHSA-4c7m-gh7v-c837, UBUNTU-CVE-2015-4696

## What is CVE-2015-4696?

CVE-2015-4696 is a medium-severity use after free vulnerability in n/a, published on 1 Jul 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Use-after-free vulnerability in libwmf 0.2.8.4 allows remote attackers to cause a denial of service (crash) via a crafted WMF file to the (1) wmf2gd or (2) wmf2eps command.

## Which versions are affected by CVE-2015-4696?

It affects 1 product.


Products: Wvware Libwmf.

## How do I fix CVE-2015-4696?

Upgrade to a fixed version.

## Is CVE-2015-4696 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3376](https://insights.sbomify.com/CVE-2006-3376/): Integer overflow in n/a (high 7.5)
- [CVE-2016-9011](https://insights.sbomify.com/CVE-2016-9011/): Denial of service in n/a (medium 5.5)
- [CVE-2015-4695](https://insights.sbomify.com/CVE-2015-4695/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4696 and fix it if it is affected.

What it is: CVE-2015-4696 is a medium-severity use after free vulnerability in n/a, published on 1 Jul 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-4696 in the wild and no public exploit code.

Affected product: n/a. 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-2015-4696/ (Markdown: https://insights.sbomify.com/CVE-2015-4696/index.md)
```

## Sources

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

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