# CVE-2005-2120: Memory corruption in n/a

> Remote authenticated attackers can execute arbitrary code via a stack-based buffer overflow in the Windows Plug and Play service.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c4pq-7f26-f57v

## What is CVE-2005-2120?

CVE-2005-2120 is a medium-severity memory corruption vulnerability in Microsoft Windows 2000, published on 13 Oct 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stack-based buffer overflow in the Plug and Play (PnP) service (UMPNPMGR.DLL) in Microsoft Windows 2000 SP4, and XP SP1 and SP2, allows remote or local authenticated attackers to execute arbitrary code via a large number of "\" (backslash) characters in a registry key name, which triggers the overflow in a wsprintfW function call.

## Which versions are affected by CVE-2005-2120?

It affects 2 products.


Products: Microsoft Windows 2000, Microsoft Windows Xp.

## How do I fix CVE-2005-2120?

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

## Is CVE-2005-2120 being exploited?

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

Public exploit code:

- Microsoft Windows Plug-and-Play - 'Umpnpmgr.dll' Denial of Service (MS05-047) (1) (exploitdb)
- Microsoft Windows Plug-and-Play - 'Umpnpmgr.dll' Denial of Service (MS05-047) (2) (exploitdb)
- Microsoft Plug and Play Service Registry Overflow (metasploit)

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

What it is: CVE-2005-2120 is a medium-severity memory corruption vulnerability in Microsoft Windows 2000, published on 13 Oct 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2120 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-2005-2120/ (Markdown: https://insights.sbomify.com/CVE-2005-2120/index.md)
```

## Sources

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

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