# CVE-2011-2003: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted font file, affecting Windows kernel drivers.

- **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 Oct 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rr89-f283-c7m9

## What is CVE-2011-2003?

CVE-2011-2003 is a critical memory corruption vulnerability in Microsoft Windows 2003 Server, published on 12 Oct 2011. 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

Buffer overflow in win32k.sys in the kernel-mode drivers in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 allows remote attackers to execute arbitrary code via a crafted .fon file, aka "Font Library File Buffer Overrun Vulnerability."

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

## Which versions are affected by CVE-2011-2003?

It affects 6 products.


Products: Microsoft Windows 2003 Server, Microsoft Windows 7, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2011-2003?

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

## Is CVE-2011-2003 being exploited?

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

Public exploit code:

- Microsoft Windows - '.fon' Kernel-Mode Buffer Overrun (PoC) (MS11-077) (exploitdb)

## Other vulnerabilities in Microsoft Windows 2003 Server

- [CVE-2008-0015](https://insights.sbomify.com/CVE-2008-0015/): Microsoft Windows Video ActiveX Control Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-1701](https://insights.sbomify.com/CVE-2015-1701/): Microsoft Win32k Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2013-5065](https://insights.sbomify.com/CVE-2013-5065/): Microsoft Windows Kernel Privilege Escalation (high 7.8, exploited in the wild)
- [CVE-2011-1268](https://insights.sbomify.com/CVE-2011-1268/): Code injection in n/a (critical 10.0)
- [CVE-2011-1868](https://insights.sbomify.com/CVE-2011-1868/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2003 and fix it if it is affected.

What it is: CVE-2011-2003 is a critical memory corruption vulnerability in Microsoft Windows 2003 Server, published on 12 Oct 2011. 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-2011-2003 exists.

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

## Sources

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

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