# CVE-2012-0002: Memory corruption in n/a

> Remote attackers can execute arbitrary code on Windows systems by sending crafted RDP packets due to improper memory processing.

- **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:** Not needed
- **Fix available:** No
- **Published:** 13 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5rh5-ff3w-38rh

## What is CVE-2012-0002?

CVE-2012-0002 is a critical memory corruption vulnerability in Microsoft Windows 7, published on 13 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Remote Desktop Protocol (RDP) implementation 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 does not properly process packets in memory, which allows remote attackers to execute arbitrary code by sending crafted RDP packets triggering access to an object that (1) was not properly initialized or (2) is deleted, aka "Remote Desktop Protocol Vulnerability."

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2012-0002?

It affects 5 products.


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

## How do I fix CVE-2012-0002?

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

## Is CVE-2012-0002 being exploited?

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

Public exploit code:

- Microsoft Terminal Services - Use-After-Free (MS12-020) (exploitdb)
- MS12-020 Microsoft Remote Desktop Use-After-Free DoS (metasploit)
- https://github.com/zhangkaibin0921/MS12-020-CVE-2012-0002 (github_poc): https://github.com/zhangkaibin0921/MS12-020-CVE-2012-0002
- MS12-020 Microsoft Remote Desktop Checker (metasploit)

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0002 and fix it if it is affected.

What it is: CVE-2012-0002 is a critical memory corruption vulnerability in Microsoft Windows 7, published on 13 Mar 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-0002 exists.

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

## Sources

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

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