Microsoft XML Core Services Information Disclosure Vulnerability



Date Discovered

October 10, 2006


Microsoft XML Core Services is prone to an information-disclosure vulnerability. This vulnerability is caused by an error in how the affected component handles server redirects. An attacker can exploit this vulnerability by enticing a victim user into visiting a malicious web page.

Technologies Affected

  • Avaya Modular Messaging (MAS) 3.0.0
  • HP Storage Management Appliance 2.1
  • Microsoft Office 2003
  • Microsoft SQL Server 2000 Client 8.0 SP3
  • Microsoft SQL Server 2005 SP1
  • Microsoft Windows 2000 Advanced Server SP4
  • Microsoft Windows 2000 Datacenter Server SP4
  • Microsoft Windows 2000 Professional SP4
  • Microsoft Windows 2000 Server SP4
  • Microsoft XML Core Services 3.0
  • Microsoft XML Core Services 3.0 SP4
  • Microsoft XML Core Services 3.0 SP5
  • Microsoft XML Core Services 3.0 SP7
  • Microsoft XML Core Services 4.0
  • Microsoft XML Core Services 5.0 SP1


Run all software as a nonprivileged user with minimal access rights.
Attackers may successfully exploit client flaws in the browser through latent vulnerabilities. When possible, run client software 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.
Web users should be cautious about following links to websites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.

Set web browser security to disable the execution of script code or active content.
Disabling support for Active Scripting while visiting untrusted sites may mitigate this issue.

Microsoft has released a security bulletin with fixes to address this issue on supported platforms.



The vendor 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


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 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.