# CVE-2017-7859: Memory corruption in n/a

> A heap-based buffer overflow in FFmpeg allows attackers to execute arbitrary code or cause denial of service via crafted media files.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jj73-fmvh-f947

## What is CVE-2017-7859?

CVE-2017-7859 is a critical memory corruption vulnerability in Ffmpeg Ffmpeg, published on 14 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FFmpeg before 2017-03-05 has an out-of-bounds write caused by a heap-based buffer overflow related to the ff_h264_slice_context_init function in libavcodec/h264dec.c.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Upgrade to a fixed version.

## Is CVE-2017-7859 being exploited?

There is no known exploitation of CVE-2017-7859 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-2017-7859 and fix it if it is affected.

What it is: CVE-2017-7859 is a critical memory corruption vulnerability in Ffmpeg Ffmpeg, published on 14 Apr 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-7859 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-2017-7859/ (Markdown: https://insights.sbomify.com/CVE-2017-7859/index.md)
```

## Sources

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

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