# CVE-2023-51793: Memory corruption in n/a

> A local attacker can execute arbitrary code via a buffer overflow in FFmpeg's image processing utilities.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 19 Apr 2024
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-51793, GHSA-hwp9-p6mr-p438, JLSEC-2026-635, UBUNTU-CVE-2023-51793

## What is CVE-2023-51793?

CVE-2023-51793 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 19 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer Overflow vulnerability in Ffmpeg v.N113007-g8d24a28d06 allows a local attacker to execute arbitrary code via the libavutil/imgutils.c:353:9 in image_copy_plane.

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

## Which versions are affected by CVE-2023-51793?

It affects 1 product.


Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2023-51793?

Upgrade to a fixed version.

## Is CVE-2023-51793 being exploited?

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

What it is: CVE-2023-51793 is a high-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 19 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51793 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-2023-51793/ (Markdown: https://insights.sbomify.com/CVE-2023-51793/index.md)
```

## Sources

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

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