# CVE-2014-9676: Use after free in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a crafted video file due to a use-after-free error in FFmpeg.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 28 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DLA-464-1, GHSA-9fmj-mghc-6mmj, UBUNTU-CVE-2014-9676

## What is CVE-2014-9676?

CVE-2014-9676 is a medium-severity use after free vulnerability in Ffmpeg Ffmpeg, published on 28 Feb 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

The seg_write_packet function in libavformat/segment.c in ffmpeg 2.1.4 and earlier does not free the correct memory location, which allows remote attackers to cause a denial of service ("invalid memory handler") and possibly execute arbitrary code via a crafted video that triggers a use after free.

## Which versions are affected by CVE-2014-9676?

It affects 1 product.


Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2014-9676?

Upgrade to a fixed version.

## Is CVE-2014-9676 being exploited?

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

## Other vulnerabilities in Ffmpeg Ffmpeg

- [CVE-2013-0864](https://insights.sbomify.com/CVE-2013-0864/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0872](https://insights.sbomify.com/CVE-2013-0872/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-0873](https://insights.sbomify.com/CVE-2013-0873/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-4265](https://insights.sbomify.com/CVE-2013-4265/): Null dereference in n/a (critical 10.0)
- [CVE-2011-3937](https://insights.sbomify.com/CVE-2011-3937/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9676 and fix it if it is affected.

What it is: CVE-2014-9676 is a medium-severity use after free vulnerability in Ffmpeg Ffmpeg, published on 28 Feb 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-2014-9676 in the wild and no public exploit code.

Affected product: Ffmpeg Ffmpeg. 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-2014-9676/ (Markdown: https://insights.sbomify.com/CVE-2014-9676/index.md)
```

## Sources

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

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