Microsoft Windows 2000 USBH_IoctlGetNodeConnectionDriverKeyName information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Microsoft Windows 2000. Impacted is the function USBH_IoctlGetNodeConnectionDriverKeyName. Executing a manipulation can lead to information disclosure.
The attack requires local access. There is no available exploit.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability has been found in Microsoft Windows 2000 (Operating System) and classified as problematic. This vulnerability affects the function USBH_IoctlGetNodeConnectionDriverKeyName. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The issue has been introduced in 02/17/2000. The weakness was presented 07/04/2003 by window with Microsoft (Website). The advisory is shared for download at microsoft.com. The attack needs to be approached locally. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
The vulnerability was handled as a non-public zero-day exploit for at least 1233 days. During that time the estimated underground price was around $0-$5k.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at microsoft.com.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 8081†). See VDB-153, VDB-146, VDB-154 and VDB-150 for similar entries. Once again VulDB remains the best source for vulnerability data.
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: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
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: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: microsoft.com
Timeline
02/17/2000 🔍06/26/2003 🔍
07/04/2003 🔍
07/04/2003 🔍
03/08/2021 🔍
Sources
Vendor: microsoft.comProduct: microsoft.com
Advisory: microsoft.com
Researcher: This issue was reported by Microsoft with the release (window)
Organization: Microsoft
Status: Not defined
GCVE (VulDB): GCVE-100-148
SecurityFocus: 8081 - Microsoft Windows 2000 USBH_IoctlGetNodeConnectionDriverKeyName Information Disclosure Vulnerability
See also: 🔍
Entry
Created: 07/04/2003 02:00Updated: 03/08/2021 13:15
Changes: 07/04/2003 02:00 (54), 06/26/2019 07:34 (3), 03/08/2021 13:15 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.