February 8, 2005
A cross-site scripting and spoofing vulnerability affects Microsoft Windows SharePoint Services and SharePoint Team Services. A remote attacker may carry out a cross-site scripting attack to execute arbitrary HTML and script code in a user's browser. It is also possible to poison Web browser and intermediate proxy server caches by placing spoofed content in the caches.
- Microsoft SharePoint Team Services from Microsoft
- Microsoft Windows SharePoint Services Windows Server 2003
- Microsoft Windows SharePoint Services Windows Server 2003 SP1
Block external access at the network boundary, unless external parties require service.
Access to the affected computer providing SharePoint Services may be blocked at the network perimeter. Only allow trusted computers and networks to have access to resources.
Run all software as a nonprivileged user with minimal access rights.
It may also be possible for attackers to more successfully exploit client flaws in the browser through cross-site scripting vulnerabilities. When possible, run client software (especially programs such as IM clients, Web browsers and MUAs) as regular user accounts with limited access to system resources. This may limit the immediate consequences of client-side vulnerabilities.
Do not follow links provided by unknown or untrusted sources.
Users should avoid Web sites of questionable integrity and not follow links supplied by unknown or untrusted sources.
Set web browser security to disable the execution of script code or active content.
As the exploitation of this issue allows the execution of malicious script code in Web clients, it may be possible to prevent successful exploitation by disabling script code and active content support within a client browser. It should be noted that this mitigation tactic might adversely affect Websites that rely on the execution of browser based script code.
Microsoft has released updates to address this vulnerability on supported platforms.
The discoverer of this vulnerability is currently unknown. Microsoft reported this issue.
© 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 email@example.com.
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 firstname.lastname@example.org 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.