# CVE-2006-0010: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted EOT fonts in emails or web pages, affecting multiple Windows versions.

- **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:** 10 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4373-qwqg-vgwm

## What is CVE-2006-0010?

CVE-2006-0010 is a critical memory corruption vulnerability in Microsoft Windows 2000, published on 10 Jan 2006. 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

Heap-based buffer overflow in T2EMBED.DLL in Microsoft Windows 2000 SP4, XP SP1 and SP2, and Server 2003 up to SP1, Windows 98, and Windows ME allows remote attackers to execute arbitrary code via an e-mail message or web page with a crafted Embedded Open Type (EOT) web font that triggers the overflow during decompression.

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

## Which versions are affected by CVE-2006-0010?

It affects 7 products.


Products: Microsoft Windows 2000, Microsoft Windows 2003 Server, Microsoft Windows 98, Microsoft Windows 98se, Microsoft Windows Me, Microsoft Windows Nt, Microsoft Windows Xp.

## How do I fix CVE-2006-0010?

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

## Is CVE-2006-0010 being exploited?

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

## Other vulnerabilities in Microsoft Windows 2000

- [CVE-2008-4250](https://insights.sbomify.com/CVE-2008-4250/): Microsoft Windows Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2010-0232](https://insights.sbomify.com/CVE-2010-0232/): Microsoft Windows Kernel Exception Handler (high 7.8, exploited in the wild)
- [CVE-2009-1123](https://insights.sbomify.com/CVE-2009-1123/): Microsoft Windows Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2002-0367](https://insights.sbomify.com/CVE-2002-0367/): Microsoft Windows Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2010-0269](https://insights.sbomify.com/CVE-2010-0269/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0010 and fix it if it is affected.

What it is: CVE-2006-0010 is a critical memory corruption vulnerability in Microsoft Windows 2000, published on 10 Jan 2006. 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-2006-0010 in the wild and no public exploit code.

Affected product: Microsoft Windows 2000. 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-2006-0010/ (Markdown: https://insights.sbomify.com/CVE-2006-0010/index.md)
```

## Sources

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

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