# CVE-2004-0209: Memory corruption in n/a

> Remote attackers can execute arbitrary code via malicious WMF or EMF images due to an unchecked buffer in the Windows Graphics Rendering Engine.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cxqv-7f9g-p3wr

## What is CVE-2004-0209?

CVE-2004-0209 is a critical memory corruption vulnerability in Microsoft Windows 2000, published on 16 Oct 2004. 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

Unknown vulnerability in the Graphics Rendering Engine processes of Microsoft Windows 2000, Windows XP, and Windows Server 2003 allows remote attackers to execute arbitrary code via (1) Windows Metafile (WMF) or (2) Enhanced Metafile (EMF) image formats that involve "an unchecked buffer."

## Which versions are affected by CVE-2004-0209?

It affects 3 products.


Products: Microsoft Windows 2000, Microsoft Windows 2003 Server, Microsoft Windows Xp.

## How do I fix CVE-2004-0209?

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

## Is CVE-2004-0209 being exploited?

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

Public exploit code:

- Microsoft Windows (x86) - Metafile '.emf' Heap Overflow (MS04-032) (exploitdb)

## 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-2004-0209 and fix it if it is affected.

What it is: CVE-2004-0209 is a critical memory corruption vulnerability in Microsoft Windows 2000, published on 16 Oct 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0209 exists.

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

## Sources

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

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