# CVE-2004-2527: Denial of service in n/a

> Remote attackers can cause denial of service in Windows XP and 2003 by repeatedly triggering the Utility Manager via keyboard shortcuts.

- **Severity:** Medium 5.4 (`AV:N/AC:H/Au:N/C:N/I:N/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:** 25 Oct 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-86w6-qr9g-m66p

## What is CVE-2004-2527?

CVE-2004-2527 is a medium-severity denial of service vulnerability in n/a, published on 25 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The local and remote desktop login screens in Microsoft Windows XP before SP2 and 2003 allow remote attackers to cause a denial of service (CPU and memory consumption) by repeatedly using the WinKey+"U" key combination, which causes multiple copies of Windows Utility Manager to be loaded more quickly than they can be closed when the copies detect that another instance is running.

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


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

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

## Is CVE-2004-2527 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2527 and fix it if it is affected.

What it is: CVE-2004-2527 is a medium-severity denial of service vulnerability in n/a, published on 25 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2527 in the wild and no public exploit code.

Affected product: n/a. 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-2527/ (Markdown: https://insights.sbomify.com/CVE-2004-2527/index.md)
```

## Sources

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

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