January 8, 2013
Microsoft XML Core Services is prone to a remote code-execution vulnerability. Attackers can exploit this issue to execute arbitrary code in the context of the currently logged-in user. Failed attacks will cause denial-of-service conditions.
- Microsoft Expression Web 2
- Microsoft Expression Web
- Microsoft Groove Server 2007 Service Pack 2
- Microsoft Groove Server 2007 Service Pack 3
- Microsoft Office 2003 SP3
- Microsoft Office 2007 SP2
- Microsoft Office 2007 SP3
- Microsoft Office Compatibility Pack SP2
- Microsoft Office Compatibility Pack SP3
- Microsoft Office SharePoint Server 2007 SP2 (32-bit)
- Microsoft Office SharePoint Server 2007 SP2 (64-bit)
- Microsoft Office SharePoint Server 2007 SP3 (32-bit)
- Microsoft Office SharePoint Server 2007 SP3 (64-bit)
- Microsoft Windows 7 for x64-based Systems
- Microsoft Windows 7 for x64-based Systems SP1
- Microsoft Windows 8 for 64-bit Systems
- Microsoft Windows Server 2003 Itanium
- Microsoft Windows Server 2003 Itanium SP1
- Microsoft Windows Server 2003 Itanium SP2
- Microsoft Windows Server 2003 x64 SP1
- Microsoft Windows Server 2003 x64 SP2
- Microsoft Windows Server 2008 R2 Itanium
- Microsoft Windows Server 2008 R2 Itanium SP1
- Microsoft Windows Server 2008 R2 for x64-based Systems SP1
- Microsoft Windows Server 2008 for Itanium-based Systems
- Microsoft Windows Server 2008 for Itanium-based Systems SP2
- Microsoft Windows Server 2008 for x64-based Systems
- Microsoft Windows Server 2008 for x64-based Systems R2
- Microsoft Windows Server 2008 for x64-based Systems SP2
- Microsoft Windows Server 2012
- Microsoft Windows Vista x64 Edition Service Pack 2
- Microsoft Windows XP 64-bit Edition
- Microsoft Windows XP 64-bit Edition SP1
- Microsoft Word Viewer
- Microsoft XML Core Services 3.0
- Microsoft XML Core Services 5.0
- Microsoft XML Core Services 6.0
Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.
Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to sites 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.
Since a successful exploit of this issue requires malicious code to execute in web clients, consider disabling support for script code and active content within the client browser. Note that this mitigation tactic might adversely affect legitimate websites that rely on the execution of browser-based script code.
Implement multiple redundant layers of security.
Memory-protection schemes (such as nonexecutable stack and heap configurations and randomly mapped memory segments) will complicate exploits of memory-corruption vulnerabilities.
Updates are available. Please see the references for more information.
© 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.