# OSV-2025-617: UNKNOWN WRITE in MP4_BoxFree

> A memory corruption vulnerability in the MP4_BoxFree function allows attackers to cause a crash or potentially execute arbitrary code via crafted MP4 files.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2025

## What is OSV-2025-617?

OSV-2025-617 is a memory corruption vulnerability in vlc, published on 12 Aug 2025. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=437783630

```
Crash type: UNKNOWN WRITE
Crash state:
MP4_BoxFree
MP4_ReadBoxContainerChildrenIndexed
MP4_ReadBoxContainer
```

## Which versions are affected by OSV-2025-617?

1 open source package ship an affected version, including vlc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vlc` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2025-617?

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

## Is OSV-2025-617 being exploited?

There is no known exploitation of OSV-2025-617 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2025-617 and fix it if it is affected.

What it is: OSV-2025-617 is a memory corruption vulnerability in vlc, published on 12 Aug 2025. 
Exploitation: There is no known exploitation of OSV-2025-617 in the wild and no public exploit code.

Affected packages and fixed versions:
- vlc (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2025-617/ (Markdown: https://insights.sbomify.com/OSV-2025-617/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2025-617

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