# CVE-2022-3964: ffmpeg QuickTime RPZA Video Encoder rpzaenc.c out-of-bounds

> A remote attacker can trigger an out-of-bounds read in the QuickTime RPZA Video Encoder, potentially causing a crash or leaking memory.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Nov 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-3964, GHSA-5fpv-gjqp-q83p, JLSEC-2025-120, SUSE-SU-2022:4194-1, UBUNTU-CVE-2022-3964, openSUSE-SU-2024:12514-1, openSUSE-SU-2024:12520-1

## What is CVE-2022-3964?

CVE-2022-3964 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 13 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability classified as problematic has been found in ffmpeg. This affects an unknown part of the file libavcodec/rpzaenc.c of the component QuickTime RPZA Video Encoder. The manipulation of the argument y_size leads to out-of-bounds read. It is possible to initiate the attack remotely. The name of the patch is 92f9b28ed84a77138105475beba16c146bdaf984. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-213543.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ffmpeg-4` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP4 | All versions | 4.4-150400.3.5.1 |
| `ffmpeg-4` | SUSE:Linux Enterprise Module for Package Hub 15 SP4 | All versions | 4.4-150400.3.5.1 |
| `ffmpeg-4` | SUSE:Linux Enterprise Workstation Extension 15 SP4 | All versions | 4.4-150400.3.5.1 |
| `ffmpeg-4` | openSUSE:Leap 15.4 | All versions | 4.4-150400.3.5.1 |
| `ffmpeg-4` | openSUSE:Tumbleweed | All versions | 4.4.3-2.1 |
| `ffmpeg-5` | openSUSE:Tumbleweed | All versions | 5.1.2-4.1 |

Products: Ffmpeg Ffmpeg.

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

Apply the vendor's patch.

## Is CVE-2022-3964 being exploited?

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

What it is: CVE-2022-3964 is a medium-severity memory corruption vulnerability in Ffmpeg Ffmpeg, published on 13 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-3964 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-3964/ (Markdown: https://insights.sbomify.com/CVE-2022-3964/index.md)
```

## Sources

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

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