# CVE-2005-3644: Denial of service in n/a

> Remote attackers can cause denial of service via memory consumption in the Windows UPnP service by sending a crafted DCE RPC request.

- **Severity:** High 7.8 (`AV:N/AC:L/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:** 17 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h3rx-xhvf-jfqc

## What is CVE-2005-3644?

CVE-2005-3644 is a high-severity denial of service vulnerability in Microsoft Windows 2000, published on 17 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PNP_GetDeviceList (upnp_getdevicelist) in UPnP for Microsoft Windows 2000 SP4 and earlier, and possibly Windows XP SP1 and earlier, allows remote attackers to cause a denial of service (memory consumption) via a DCE RPC request that specifies a large output buffer size, a variant of CVE-2006-6296, and a different vulnerability than CVE-2005-2120.

Weakness: CWE-399

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

It affects 2 products.


Products: Microsoft Windows 2000, Microsoft Windows Xp.

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

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

## Is CVE-2005-3644 being exploited?

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

Public exploit code:

- Microsoft Windows Server 2000 - UPNP 'getdevicelist' Memory Leak Denial of Service (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-2005-3644 and fix it if it is affected.

What it is: CVE-2005-3644 is a high-severity denial of service vulnerability in Microsoft Windows 2000, published on 17 Nov 2005. 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-2005-3644 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-3644/ (Markdown: https://insights.sbomify.com/CVE-2005-3644/index.md)
```

## Sources

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

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