Microsoft Windows up to XP SP1 UPnP GetDeviceList resource management

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.7$0-$5k0.00

Summaryinfo

A vulnerability was found in Microsoft Windows up to XP SP1. It has been classified as critical. The affected element is the function GetDeviceList of the component UPnP. This manipulation causes resource management. The identification of this vulnerability is CVE-2005-3644. Furthermore, there is an exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability classified as critical was found in Microsoft Windows up to XP SP1 (Operating System). Affected by this vulnerability is the function GetDeviceList of the component UPnP. The manipulation with an unknown input leads to a resource management vulnerability. The CWE definition for the vulnerability is CWE-399. As an impact it is known to affect availability. The summary by CVE is:

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.

The bug was discovered 11/14/2005. The weakness was shared 11/16/2005 by Winny Thomas as confirmed bulletin (Technet). The advisory is shared at microsoft.com. This vulnerability is known as CVE-2005-3644 since 11/17/2005. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $5k-$25k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 90285 (Microsoft Windows Memory Allocation Denial of Service via RPC (KB911052) - Zero Day).

Applying a patch is able to eliminate this problem. The bugfix is ready for download at windowsupdate.microsoft.com. Attack attempts may be identified with Snort ID 4826. In this case the pattern |05 00 00| is used for detection. Furthermore it is possible to detect and prevent this kind of attack with TippingPoint and the filter 3966.

The vulnerability is also documented in the databases at X-Force (23066), Exploit-DB (1328), SecurityFocus (BID 15460†), OSVDB (20916†) and Secunia (SA17595†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Support

  • end of life (old version)

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 6.7

VulDB Base Score: 7.5
VulDB Temp Score: 6.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Resource management
CWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: windowsupdate.microsoft.com

Snort ID: 4826
Snort Message: NETBIOS DCERPC NCACN-IP-TCP umpnpmgr PNP_GetRootDeviceInstance attempt
Snort Pattern: 🔍
TippingPoint: 🔍

McAfee IPS: 🔍
McAfee IPS Version: 🔍

SourceFire IPS: 🔍
ISS Proventia IPS: 🔍
PaloAlto IPS: 🔍
Fortigate IPS: 🔍

Timelineinfo

11/14/2005 🔍
11/16/2005 +2 days 🔍
11/16/2005 +0 days 🔍
11/16/2005 +0 days 🔍
11/17/2005 +1 days 🔍
11/17/2005 +0 days 🔍
11/17/2005 +0 days 🔍
11/17/2005 +0 days 🔍
11/17/2005 +0 days 🔍
11/18/2005 +0 days 🔍
11/20/2005 +2 days 🔍
06/29/2025 +7160 days 🔍

Sourcesinfo

Vendor: microsoft.com
Product: microsoft.com

Advisory: microsoft.com
Researcher: Winny Thomas
Status: Confirmed

CVE: CVE-2005-3644 (🔍)
GCVE (CVE): GCVE-0-2005-3644
GCVE (VulDB): GCVE-100-1909
X-Force: 23066
SecurityFocus: 15460 - Microsoft Windows Plug and Play Denial of Service Vulnerability
Secunia: 17595 - Microsoft Windows UPnP GetDeviceList Denial of Service, Less Critical
OSVDB: 20916 - Microsoft Windows UPnP GetDeviceList Remote DoS
SecurityTracker: 1015233
Vulnerability Center: 9645 - Windows Plug and Play Anonymous DoS via Malformed Request, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 11/18/2005 12:25
Updated: 06/29/2025 00:44
Changes: 11/18/2005 12:25 (95), 06/11/2019 13:05 (2), 06/16/2024 15:09 (17), 06/29/2025 00:44 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!