# CVE-2008-0011: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted MJPEG streams in AVI or ASF files due to improper error checking in Microsoft DirectX.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q2hg-79w4-xr3v

## What is CVE-2008-0011?

CVE-2008-0011 is a critical memory corruption vulnerability in n/a, published on 12 Jun 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Microsoft DirectX 8.1 through 9.0c, and DirectX on Microsoft XP SP2 and SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, and Server 2008, does not properly perform MJPEG error checking, which allows remote attackers to execute arbitrary code via a crafted MJPEG stream in a (1) AVI or (2) ASF file, aka the "MJPEG Decoder Vulnerability."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Microsoft Directx.

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

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

## Is CVE-2008-0011 being exploited?

There is no known exploitation of CVE-2008-0011 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2009-1537](https://insights.sbomify.com/CVE-2009-1537/): Microsoft DirectX NULL Byte Overwrite (high 8.8, exploited in the wild)
- [CVE-2012-1537](https://insights.sbomify.com/CVE-2012-1537/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-1879](https://insights.sbomify.com/CVE-2010-1879/): Code injection in n/a (critical 9.3)
- [CVE-2010-1880](https://insights.sbomify.com/CVE-2010-1880/): Code injection in n/a (critical 9.3)
- [CVE-2009-1538](https://insights.sbomify.com/CVE-2009-1538/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0011 and fix it if it is affected.

What it is: CVE-2008-0011 is a critical memory corruption vulnerability in n/a, published on 12 Jun 2008. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-0011 in the wild and no public exploit code.

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-2008-0011/ (Markdown: https://insights.sbomify.com/CVE-2008-0011/index.md)
```

## Sources

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

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