January 11, 2005
Microsoft Indexing Service is reported prone to a buffer overflow vulnerability. This issue results from insufficient boundary checks performed by the application when copying user-supplied data in to sensitive process buffers. A remote or local attacker may execute arbitrary code on a vulnerable computer, which could ultimately allow the attacker to gain unauthorized access to the computer or gain elevated privileges.
This issue can be exploited by sending a malformed query to the Indexing Service. It is reported that issue may be locally and remotely exploited, if Indexing Service is enabled on a vulnerable computer.
- Microsoft Windows 2000 Advanced Server SP3
- Microsoft Windows 2000 Advanced Server SP4
- Microsoft Windows 2000 Datacenter Server SP3
- Microsoft Windows 2000 Datacenter Server SP4
- Microsoft Windows 2000 Professional SP3
- Microsoft Windows 2000 Professional SP4
- Microsoft Windows 2000 Server SP3
- Microsoft Windows 2000 Server SP4
- Microsoft Windows 2000 Terminal Services SP3
- Microsoft Windows 2000 Terminal Services SP4
- Microsoft Windows Server 2003 Datacenter Edition
- Microsoft Windows Server 2003 Datacenter Edition Itanium
- Microsoft Windows Server 2003 Enterprise Edition
- Microsoft Windows Server 2003 Enterprise Edition Itanium
- Microsoft Windows Server 2003 Standard Edition
- Microsoft Windows Server 2003 Web Edition
- Microsoft Windows XP 64-bit Edition
- Microsoft Windows XP 64-bit Edition SP1
- Microsoft Windows XP 64-bit Edition Version 2003
- Microsoft Windows XP 64-bit Edition Version 2003 SP1
- Microsoft Windows XP Home
- Microsoft Windows XP Home SP1
- Microsoft Windows XP Professional
- Microsoft Windows XP Professional SP1
Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
To prevent against local attacks, it is recommended that local interactive access to a vulnerable computer should be provided to trusted individuals only.
Block external access at the network boundary, unless external parties require service.
If the Indexing service is enabled with Microsoft IIS to be accessible remotely, it is recommended that access should be limited to trusted computers and networks only. Block UDP ports 137 and 138 and TCP ports 139 and 445 to deny access to the resources.
Disallow anonymous access to services. Permit access for trusted individuals only.
Do not allow anonymous access to the resources. Ensure that a strong password policy is in place to protect against brute force type attacks.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy network intrusion detection systems to monitor network traffic for signs of suspicious or anomalous activity. This may aid in detecting attacks as well as help in detecting malicious activities that are performed as a result of exploitation.
Implement multiple redundant layers of security.
Deploy applicable memory protection schemes such as non-executable stack/heap configurations and randomly mapped memory segments. This may complicate exploitation of memory corruption vulnerabilities.
Microsoft has released updates to address this vulnerability in supported versions of the Windows operating system.
This issue was announced by Microsoft.
Copyright © 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.