| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Microsoft Windows 2000 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Utility Manager. The manipulation leads to memory corruption. This vulnerability is referenced as CVE-2003-0908. The attack needs to be initiated within the local network. Furthermore, an exploit is available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, has been found in Microsoft Windows 2000 (Operating System). This issue affects an unknown part of the component Utility Manager. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The Utility Manager in Microsoft Windows 2000 executes winhlp32.exe with system privileges, which allows local users to execute arbitrary code via a "Shatter" style attack using a Windows message that accesses the context sensitive help button in the GUI, as demonstrated using the File Open dialog in the Help window, a different vulnerability than CVE-2004-0213.
The bug was discovered 04/13/2004. The weakness was published 04/13/2004 by Brett Moore, Cesar Cerrudo and Ben Pryor with Security-Assessment.com as MS04-011 as confirmed bulletin (Technet). The advisory is shared at microsoft.com. The identification of this vulnerability is CVE-2003-0908 since 11/04/2003. The attack needs to be done within the local network. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.
A public exploit has been developed in ANSI C. The exploit is available at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1517 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 12205 (MS04-011: Microsoft Hotfix (credentialed check) (835732)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Windows : Microsoft Bulletins and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 90108 (Multiple Microsoft Windows Vulnerabilities (MS04-011)).
Applying the patch MS04-011 is able to eliminate this problem. The bugfix is ready for download at windowsupdate.microsoft.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (15632), Exploit-DB (271), Tenable (12205), SecurityFocus (BID 10124†) and OSVDB (5254†). Similar entries are available at VDB-530, VDB-599, VDB-600 and VDB-603. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
- Product: https://www.microsoft.com/en-us/windows
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 7.9
VulDB Base Score: 8.8
VulDB Temp Score: 7.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 12205
Nessus Name: MS04-011: Microsoft Hotfix (credentialed check) (835732)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 101011
OpenVAS Name: MS04-011 security check
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: MS04-011
Timeline
02/17/2000 🔍11/04/2003 🔍
04/13/2004 🔍
04/13/2004 🔍
04/13/2004 🔍
04/13/2004 🔍
04/13/2004 🔍
04/13/2004 🔍
04/13/2004 🔍
04/14/2004 🔍
04/14/2004 🔍
04/14/2004 🔍
06/01/2004 🔍
01/02/2025 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: MS04-011
Researcher: Brett Moore, Cesar Cerrudo, Ben Pryor
Organization: Security-Assessment.com
Status: Confirmed
CVE: CVE-2003-0908 (🔍)
GCVE (CVE): GCVE-0-2003-0908
GCVE (VulDB): GCVE-100-605
OVAL: 🔍
CERT: 🔍
X-Force: 15632 - Microsoft Windows 2000 Utility Manger allows privilege escalation, High Risk
SecurityFocus: 10124 - Microsoft Windows Utility Manager Local Privilege Escalation Vulnerability
Secunia: 11064 - Microsoft Windows 14 Vulnerabilities, Highly Critical
OSVDB: 5254 - Microsoft Windows Utility Manager Privilege Escalation
SecurityTracker: 1009769
Vulnerability Center: 4122 - [MS04-011] Microsoft Windows 2000 Utility Manager Allows Privilege Elevation, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 04/14/2004 14:39Updated: 01/02/2025 11:24
Changes: 04/14/2004 14:39 (106), 06/28/2019 09:40 (5), 01/02/2025 11:24 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.