Microsoft Windows XML Core Services XSLT Buffer Overrun Vulnerability



Date Discovered

October 10, 2006


Microsoft Windows is prone to a remotely exploitable buffer-overrun condition in the XSLT implementation of XML core services. An attacker can exploit this issue to execute arbitrary code on an unsuspecting victim's computer. This may facilitate a remote compromise.

Technologies Affected

  • Avaya Modular Messaging (MAS) 3.0.0
  • HP Storage Management Appliance 2.1
  • Microsoft Office 2003
  • Microsoft Office 2003 SP1
  • Microsoft Office 2003 SP2
  • Microsoft Office 2003 SP3
  • Microsoft SQL Server 2000
  • Microsoft SQL Server 2000 Client 8.0 SP3
  • Microsoft SQL Server 2000 SP1
  • Microsoft SQL Server 2000 SP2
  • Microsoft SQL Server 2000 SP3
  • Microsoft SQL Server 2000 SP3a
  • Microsoft SQL Server 2005 SP1
  • Microsoft XML Core Services 3.0
  • Microsoft XML Core Services 3.0 SP3
  • 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
  • Microsoft XML Core Services 5.0 SP1
  • Microsoft XML Core Services 6.0
  • Microsoft XML Parser 2.6


Run all software as a nonprivileged user with minimal access rights.
Run all software with the least privileges required while still maintaining functionality. This may limit the consequences of a successful exploit.

Do not follow links provided by unknown or untrusted sources.
Do not follow links or visit pages of unknown or questionable integrity. This may limit exposure to this and other latent vulnerabilities.

Implement multiple redundant layers of security.
Various memory-protection schemes (such as non-executable and randomly mapped memory segments) may hinder an attacker's ability to exploit this vulnerability to execute arbitrary code.

Microsoft has released security bulletin MS06-061 to address this issue. Please see the attached security bulletin for information on how to obtain fixes.



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