Microsoft Windows 2000 USBH_IoctlGetNodeConnectionDriverKeyName Information Disclosure Vulnerability

Bugtraq ID:	8081
Class:	Design Error
CVE:
Remote:	No
Local:	Yes
Published:	Jun 26 2003 12:00AM
Updated:	Jun 26 2003 12:00AM
Credit:	This issue was reported by Microsoft with the release of Windows 2000 Service Pack 4.
Vulnerable:	Microsoft Windows 2000 Server SP3 Microsoft Windows 2000 Server SP2 Microsoft Windows 2000 Server SP1 Microsoft Windows 2000 Server + Avaya DefinityOne Media Servers + Avaya IP600 Media Servers + Avaya S3400 Message Application Server 0 + Avaya S8100 Media Servers 0 Microsoft Windows 2000 Professional SP3 Microsoft Windows 2000 Professional SP2 Microsoft Windows 2000 Professional SP1 Microsoft Windows 2000 Professional Microsoft Windows 2000 Datacenter Server SP3 Microsoft Windows 2000 Datacenter Server SP2 Microsoft Windows 2000 Datacenter Server SP1 Microsoft Windows 2000 Datacenter Server Microsoft Windows 2000 Advanced Server SP3 Microsoft Windows 2000 Advanced Server SP2 Microsoft Windows 2000 Advanced Server SP1 Microsoft Windows 2000 Advanced Server
Not Vulnerable:	Microsoft Windows 2000 Server SP4 Microsoft Windows 2000 Professional SP4 Microsoft Windows 2000 Datacenter Server SP4 Microsoft Windows 2000 Advanced Server SP4

Microsoft Windows 2000 USBH_IoctlGetNodeConnectionDriverKeyName Information Disclosure Vulnerability

It has been reported that under some circumstances a call to USBH_IoctlGetNodeConnectionDriverKeyName() may return uninitialized data from kernel memory space. This may potentially provide a conduit for the disclosure of sensitive data.

Microsoft Windows 2000 USBH_IoctlGetNodeConnectionDriverKeyName Information Disclosure Vulnerability

Currently we are not aware of any exploits for this issue. If you feel we are in error or are aware of more recent information, please mail us at: [email protected] <mailto:[email protected]>.

Microsoft Windows 2000 USBH_IoctlGetNodeConnectionDriverKeyName Information Disclosure Vulnerability

Solution:
The vendor has released a service pack to address this and other issues:


Microsoft Windows 2000 Professional

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Server SP2

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Server SP3

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Advanced Server SP3

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Advanced Server SP1

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Server SP1

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Professional SP3

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Advanced Server SP2

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Professional SP2

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Advanced Server

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Professional SP1

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 Server

• Microsoft Windows 2000 SP4
  http://www.microsoft.com/windows2000/downloads/servicepacks/sp4/defaul t.asp

Microsoft Windows 2000 USBH_IoctlGetNodeConnectionDriverKeyName Information Disclosure Vulnerability

References:

• Windows 2000 Service Pack 4 (Microsoft)