# CVE-2008-4869: Denial of service in n/a

> FFmpeg allows remote attackers to cause a denial of service via memory consumption, affecting applications using the library.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qjvh-9wvw-wjxm

## What is CVE-2008-4869?

CVE-2008-4869 is a critical denial of service vulnerability in Ffmpeg Ffmpeg, published on 31 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FFmpeg 0.4.9, as used by MPlayer, allows context-dependent attackers to cause a denial of service (memory consumption) via unknown vectors, aka a "Tcp/udp memory leak."

Weakness: CWE-399

## Which versions are affected by CVE-2008-4869?

It affects 1 product.


Products: Ffmpeg Ffmpeg.

## How do I fix CVE-2008-4869?

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

## Is CVE-2008-4869 being exploited?

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

What it is: CVE-2008-4869 is a critical denial of service vulnerability in Ffmpeg Ffmpeg, published on 31 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-4869 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-2008-4869/ (Markdown: https://insights.sbomify.com/CVE-2008-4869/index.md)
```

## Sources

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

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