# CVE-2025-1373: FFmpeg MOV Parser mov.c mov_read_trak null pointer dereference

> A local attacker can cause a denial of service in FFmpeg via a null pointer dereference in the MOV parser.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **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:** 17 Feb 2025
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-xgcj-hc3f-6mjc, JLSEC-2025-150, UBUNTU-CVE-2025-1373

## What is CVE-2025-1373?

CVE-2025-1373 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 17 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in FFmpeg up to 7.1. It has been rated as problematic. Affected by this issue is the function mov_read_trak of the file libavformat/mov.c of the component MOV Parser. The manipulation leads to null pointer dereference. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The patch is identified as 43be8d07281caca2e88bfd8ee2333633e1fb1a13. It is recommended to apply a patch to fix this issue.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2025-1373?

It affects 1 product.


Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2025-1373?

Apply the vendor's patch.

## Is CVE-2025-1373 being exploited?

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

What it is: CVE-2025-1373 is a medium-severity vulnerability in Ffmpeg Ffmpeg, published on 17 Feb 2025. 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-2025-1373 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-2025-1373/ (Markdown: https://insights.sbomify.com/CVE-2025-1373/index.md)
```

## Sources

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

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