# CVE-2025-57613: Null dereference in n/a

> A null pointer dereference in the rust-ffmpeg library allows attackers to cause a denial of service when context allocation fails.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2025
- **Updated:** 3 Sep 2025
- **Also known as:** GHSA-r9rp-xj5x-xhgh

## What is CVE-2025-57613?

CVE-2025-57613 is a high-severity vulnerability in n/a, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in rust-ffmpeg 0.3.0 (after comit 5ac0527) A null pointer dereference vulnerability in the input() constructor function allows an attacker to cause a denial of service. The vulnerability is triggered when the avio_alloc_context() call fails and returns NULL, which is then stored and later dereferenced by the Io struct's Drop implementation.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Meh.schizofreni Rust-Ffmpeg.

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

No fix has been published for CVE-2025-57613 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-57613 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-57612](https://insights.sbomify.com/CVE-2025-57612/): Null dereference in n/a (high 7.5)
- [CVE-2025-57614](https://insights.sbomify.com/CVE-2025-57614/): Integer overflow in n/a (high 7.5)
- [CVE-2025-57615](https://insights.sbomify.com/CVE-2025-57615/): Integer overflow in n/a (high 7.5)
- [CVE-2025-57616](https://insights.sbomify.com/CVE-2025-57616/): Use after free in n/a (high 7.5)
- [CVE-2025-57611](https://insights.sbomify.com/CVE-2025-57611/): Null dereference in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57613 and fix it if it is affected.

What it is: CVE-2025-57613 is a high-severity vulnerability in n/a, published on 2 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57613 exists.

Affected product: n/a. 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-57613/ (Markdown: https://insights.sbomify.com/CVE-2025-57613/index.md)
```

## Sources

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

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