July 8, 2003
It has been reported that Microsoft Windows does not properly handle named pipes through the CreateFile API. Because of this, an attacker may be able to gain access to the SYSTEM account.
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Advanced Server SP3
- Microsoft Windows 2000 Datacenter Server
- Microsoft Windows 2000 Datacenter Server SP1
- Microsoft Windows 2000 Datacenter Server SP2
- Microsoft Windows 2000 Datacenter Server SP3
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
- Microsoft Windows 2000 Professional SP3
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Server SP3
- Microsoft Windows 2000 Terminal Services
- Microsoft Windows 2000 Terminal Services SP1
- Microsoft Windows 2000 Terminal Services SP2
- Microsoft Windows 2000 Terminal Services SP3
Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
Exploitation of this issue is possible if attackers have interactive access to vulnerable systems. Permit interactive access for trusted individuals only.
Block external access at the network boundary, unless external parties require service.
Filter network traffic of questionable integrity at border routers and network firewalls. Prohibit unauthorized network traffic through ingress and egress filtering.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Use intrusion detection systems to monitor networks and hosts. Audit intrusion detection systems regularly to identify anomalies and potential attempted attacks.
Use access control lists to enhance security.
To limit exposure to this vulnerability via SQL Server, the database should be locked down. This includes use of strong database credentials and auditing database driven applications for latent vulnerabilities that could expose the database to attacks.
This issue has been resolved in Windows 2000 Service Pack 4:
Discovery credited to Andreas Junestam.
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.