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

> A buffer overflow in FFmpeg's HEVC decoder can cause a segmentation fault, potentially leading to denial of service or arbitrary code execution.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2024-32228, GHSA-4fr2-p4v7-6hwq, OESA-2024-1936, UBUNTU-CVE-2024-32228

## What is CVE-2024-32228?

CVE-2024-32228 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 1 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

FFmpeg 7.0 is vulnerable to Buffer Overflow. There is a SEGV at libavcodec/hevcdec.c:2947:22 in hevc_frame_end.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Ffmpeg Ffmpeg.

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

Upgrade to a fixed version.

## Is CVE-2024-32228 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32228 exists.

## 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-32228 and fix it if it is affected.

What it is: CVE-2024-32228 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 1 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32228 exists.

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-32228/ (Markdown: https://insights.sbomify.com/CVE-2024-32228/index.md)
```

## Sources

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

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