Microsoft XML Core Service XMLHTTP ActiveX Control Remote Code Execution Vulnerability



Date Discovered

November 3, 2006


Microsoft XML Core Service is prone to a remote code-execution vulnerability. An attacker can exploit this issue to execute arbitrary code within the affected application, facilitating the remote compromise of affected computers. Failed exploit attempts will result in a denial-of-service condition.

Technologies Affected

  • Avaya Messaging Application Server
  • Avaya S8100 Media Servers
  • Avaya S8100 Media Servers R10
  • Avaya S8100 Media Servers R11
  • Avaya S8100 Media Servers R12
  • Avaya S8100 Media Servers R6
  • Avaya S8100 Media Servers R7
  • Avaya S8100 Media Servers R8
  • Avaya S8100 Media Servers R9
  • HP Storage Management Appliance 2.1
  • Microsoft XML Core Services 4.0
  • Microsoft XML Core Services 6.0


Run all software as a nonprivileged user with minimal access rights.
Run the web client as an unprivileged user with minimal access rights. This will limit the impact of latent vulnerabilities.

Do not follow links provided by unknown or untrusted sources.
Users should refrain from visiting sites of questionable integrity.

Set web browser security to disable the execution of script code or active content.
Disabling scripting and active content in the Internet Zone may limit exposure to this and other 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 advisory MS06-071 addressing this issue in supported versions of affected applications. Please see the references for more information.



The vendor credits Robert Freeman of ISS, and Dror Shalev and Moti Jospeh of Checkpoint with the discovery of this vulnerability.

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