# CVE-2022-2566: Heap-memory write in FFMPEG

> An integer overflow in FFmpeg's MP4 parsing allows remote code execution via a malicious file, requiring a patch to fix.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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:** 23 Sep 2022
- **Updated:** 21 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-2566, GHSA-m864-5788-g574, openSUSE-SU-2024:12332-1

## What is CVE-2022-2566?

CVE-2022-2566 is a critical vulnerability in Ffmpeg Ffmpeg, published on 23 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap out-of-bounds memory write exists in FFMPEG since version 5.1. The size calculation in `build_open_gop_key_points()` goes through all entries in the loop and adds `sc->ctts_data[i].count` to `sc->sample_offsets_count`. This can lead to an integer overflow resulting in a small allocation with `av_calloc()`. An attacker can cause remote code execution via a malicious mp4 file. We recommend upgrading past commit c953baa084607dd1d84c3bfcce3cf6a87c3e6e05

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2022-2566?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ffmpeg-5` | openSUSE:Tumbleweed | All versions | 5.1.1-1.1 |

Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2022-2566?

Apply the vendor's patch.

## Is CVE-2022-2566 being exploited?

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

What it is: CVE-2022-2566 is a critical vulnerability in Ffmpeg Ffmpeg, published on 23 Sep 2022. 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-2022-2566 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-2022-2566/ (Markdown: https://insights.sbomify.com/CVE-2022-2566/index.md)
```

## Sources

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

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