# CVE-2024-25385: Use after free in n/a

> A local attacker can cause a denial of service in flvmeta via a use-after-free vulnerability in the flv_close function.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2024
- **Updated:** 16 Aug 2024
- **Also known as:** GHSA-67vv-989w-hhr5, UBUNTU-CVE-2024-25385

## What is CVE-2024-25385?

CVE-2024-25385 is a medium-severity use after free vulnerability in n/a, published on 22 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in flvmeta v.1.2.2 allows a local attacker to cause a denial of service via the flvmeta/src/flv.c:375:21 function in flv_close.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-25385?

It affects 1 product.


Products: Flvmeta Flvmeta.

## How do I fix CVE-2024-25385?

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

## Is CVE-2024-25385 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-36243](https://insights.sbomify.com/CVE-2023-36243/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25385 and fix it if it is affected.

What it is: CVE-2024-25385 is a medium-severity use after free vulnerability in n/a, published on 22 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25385 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-2024-25385/ (Markdown: https://insights.sbomify.com/CVE-2024-25385/index.md)
```

## Sources

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

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