# CVE-2024-32230: Memory corruption in n/a

> A buffer overflow in FFmpeg's MPEG video encoder allows attackers to execute arbitrary code or cause denial of service via crafted media files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Jul 2024
- **Updated:** 14 Mar 2025
- **Also known as:** DEBIAN-CVE-2024-32230, GHSA-q935-8vhv-gg93, SUSE-SU-2024:2814-1, UBUNTU-CVE-2024-32230, USN-6983-1, openSUSE-SU-2024:14231-1

## What is CVE-2024-32230?

CVE-2024-32230 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 1 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

FFmpeg 7.0 is vulnerable to Buffer Overflow. There is a negative-size-param bug at libavcodec/mpegvideo_enc.c:1216:21 in load_input_picture in FFmpeg7.0

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-32230?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ffmpeg` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP5 | All versions | 3.4.2-150200.11.50.1 |
| `ffmpeg` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP6 | All versions | 3.4.2-150200.11.50.1 |
| `ffmpeg` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 3.4.2-150200.11.50.1 |
| `ffmpeg` | SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 3.4.2-150200.11.50.1 |
| `ffmpeg` | SUSE:Linux Enterprise Workstation Extension 15 SP5 | All versions | 3.4.2-150200.11.50.1 |
| `ffmpeg` | SUSE:Linux Enterprise Workstation Extension 15 SP6 | All versions | 3.4.2-150200.11.50.1 |
| `ffmpeg` | openSUSE:Leap 15.5 | All versions | 3.4.2-150200.11.50.1 |
| `ffmpeg` | openSUSE:Leap 15.6 | All versions | 3.4.2-150200.11.50.1 |
| `ffmpeg-4` | openSUSE:Tumbleweed | All versions | 4.4.4-12.1 |

Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2024-32230?

Apply the vendor's patch.

## Is CVE-2024-32230 being exploited?

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

What it is: CVE-2024-32230 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 1 Jul 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-32230 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-2024-32230/ (Markdown: https://insights.sbomify.com/CVE-2024-32230/index.md)
```

## Sources

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

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