Security Bulletin
Vulnerabilities in Microsoft XML Core Services Could Allow Remote Code Execution (2756145)
Published: January 08, 2013 | Updated: December 16, 2013
Microsoft XML Core Services is an application for processing Extensible Stylesheet Language Transformation (XSLT) in an XML file and these services are included in various Windows operating system installations, by default. Successful exploitation of this vulnerability could result in an attacker gaining the same privileges as the logged on user.
Email extractor free software download. Incoming Fax Routing: E-mail, Store in Folder, Print. You can also use 400+ popular search engines (AltaVista, Excite, Yahoo, InfoSeek and others from 30+ countries) for search by keywords. You can not only limit the scanning depth and width, you also can cut off unnecessary paths using patterns or just delete them entirely.AEE is very flexible and may be used to extract e-mail addresses with owners real names from “simple sites” as well as from web-forums built on scripts and from servers like ZDNet. Advanced Email Extractor is built on Microsoft Internet Explorer kernel and therefore features unmatched compatibility with all web-servers and has knowledge of all subtleties of HTTP and HTPS protocols. AEE has various criteria for scanning ranges; you can extract only the addresses you actually need from web-pages, instead of extracting all the addresses present.
Version: 1.2
General InformationExecutive Summary
This security update resolves two privately reported vulnerabilities in Microsoft XML Core Services. The vulnerabilities could allow remote code execution if a user views a specially crafted webpage using Internet Explorer. An attacker would have no way to force users to visit such a website. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes the user to the attacker's website.
This security update is rated Critical for Microsoft XML Core Services 3.0, Microsoft XML Core Services 4.0, and Microsoft XML Core Services 6.0 on all affected editions of Windows XP, Windows Vista, Windows 7, Windows 8, and Windows RT; Critical for Microsoft XML Core Services 5.0 when installed with all supported editions of Microsoft Office 2003, Microsoft Office 2007, Microsoft Word Viewer, Microsoft Office Compatibility Pack, Microsoft Expression Web, Microsoft SharePoint Server 2007, and Microsoft Groove Server 2007; Moderate for Microsoft XML Core Services 3.0, 4.0, and 6.0 on all affected editions of Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by modifying the way that Microsoft XML Core Services parses XML content. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Most customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Known Issues.Microsoft Knowledge Base Article 2756145 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.
Affected Software
Microsoft Office Suites and Software
MicrosoftDeveloper Tools andSoftware
Microsoft Server Software
Non-Affected Software
Frequently Asked Questions (FAQ) Related to This Security Update
Is security update KB2687497 for Microsoft SharePoint Server 2007 and Microsoft Groove Server 2007 being rereleased as part of MS13-002?
No. The security update for Microsoft SharePoint Server 2007 and Microsoft Groove Server 2007 that was offered in MS12-043 is a new update package. If you have already installed KB2687497, you need to install the security update again.
How is the original KB2687497 update in MS12-043 related to the KB2687497 update in this bulletin, MS13-002?
The original KB2687497 update in MS12-043 addresses the vulnerabilities described in MS12-043. The KB2687497 update in MS13-002 replaces the original update and also addresses the vulnerabilities described in this bulletin, MS13-002.
I have the KB2687497 update already installed, but Microsoft Update is offering the update to me again. Do I need to install it?
Most likely you have the original KB2687497 update installed, in which case you need to install the new KB2687497 update. Customers should apply all updates offered for the version of Microsoft Office Server software running on their systems.
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
Whereare the hashes of the securityupdates?
The SHA1 and SHA2 hashes of the security updates can be used to verify the authenticity of downloaded security update packages. For the hash information pertaining to this update, see Microsoft Knowledge Base Article 2756145.
What version of Microsoft XML Core Services is installed on my system?
Some versions of Microsoft XML Core Services are included with Microsoft Windows; others are installed with non-operating system software from Microsoft or third-party providers. Some are also available as separate downloads. The following table shows which versions of Microsoft XML Core Services are included with Microsoft Windows and which are installed with the installation of additional Microsoft or third-party software.
Note Depending on which versions of Microsoft XML Core Services are installed on your system, you may be offered more than one security update with this security bulletin. Also note that only supported versions of Microsoft XML Core Services are offered an update. For more information on which versions are supported by Microsoft, see Microsoft Knowledge Base Article 269238.
What is Microsoft XML Core Services (MSXML)?
Microsoft XML Core Services (MSXML) allows customers who use JScript, Visual Basic Scripting Edition (VBScript), and Microsoft Visual Studio 6.0 to develop XML-based applications that provide interoperability with other applications that adhere to the XML 1.0 standard. For more information, see the MSDN article, MSXML.
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, see the Microsoft Support Lifecycle website.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Service Pack Lifecycle Support Policy.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, see the Microsoft Worldwide Information website, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.
Vulnerability InformationSeverity Ratings and Vulnerability Identifiers
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the January bulletin summary. For more information, see Microsoft Exploitability Index.
MSXML Integer Truncation Vulnerability - CVE-2013-0006
A remote code execution vulnerability exists in the way that Microsoft Windows parses XML content. The vulnerability may corrupt memory in such a way that an attacker could execute arbitrary code in the context of the logged-on user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2013-0006.
Mitigating Factors for MSXML Integer Truncation Vulnerability - CVE-2013-0006
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation
Workarounds for MSXML Integer Truncation Vulnerability - CVE-2013-0006
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
FAQ for MSXML Integer Truncation Vulnerability - CVE-2013-0006
What is the scope of the vulnerability?
This is a remote code execution vulnerability.
What causes the vulnerability?
The vulnerability is caused when Microsoft XML Core Services (MSXML) parses XML content, which can corrupt the system state in such a way as to allow an attacker to run arbitrary code.
What isthe component affected by the vulnerability?
The vulnerability affects Microsoft XML Core Services (MSXML), which allows customers who use JScript, Visual Basic Scripting Edition (VBScript), and Microsoft Visual Studio 6.0 to develop XML-based applications that provide interoperability with other applications that adhere to the XML 1.0 standard. For more information, see the MSDN site, MSXML.
What is Microsoft XML Core Services (MSXML)?
Microsoft XML Core Services (MSXML) allows customers who use JScript, Visual Basic Scripting Edition (VBScript), and Microsoft Visual Studio 6.0 to develop XML-based applications that provide interoperability with other applications that adhere to the XML 1.0 standard. For more information, see the MSDN site, MSXML.
What version of Microsoft XML Core Services is installed on my system?
Microsoft XML Core Services is included in additional non-operating system software from Microsoft and is also available as separate downloads. For information about the different Microsoft XML Core Services versions that are available and the products that install them, see Microsoft Knowledge Base Article 269238.
Note Depending on which version of Microsoft XML Core Services you have installed on your system, you may be offered more than one security update from this security bulletin.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
How could an attacker exploit thevulnerability?
An attacker could exploit the vulnerability by hosting a specially crafted website that is designed to invoke MSXML through Internet Explorer. This can also include compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or in an Instant Messenger request that takes users to the attacker's website. It could also be possible to display specially crafted web content by using banner advertisements or by using other methods to deliver web content to affected systems.
Non-Microsoft web applications and services that utilize the MSXML library for parsing XML could also be vulnerable to this attack.
What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and visits a website for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
What does the update do?
The update addresses the vulnerability by modifying the way that Microsoft XML Core Services parses XML content.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued. MSXML XSLT Vulnerability - CVE-2013-0007
A remote code execution vulnerability exists in the way that Microsoft Windows parses XML content. The vulnerability may corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2013-0007.
Mitigating Factors for MSXML XSLT Vulnerability - CVE-2013-0007
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation
Workarounds for MSXML XSLT Vulnerability - CVE-2013-0007
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
FAQ for MSXML XSLT Vulnerability - CVE-2013-0007
What is the scope of the vulnerability?
This is a remote code execution vulnerability.
What causes the vulnerability?
The vulnerability is caused when Microsoft XML Core Services (MSXML) parses XML content, which can corrupt the system state in such a way as to allow an attacker to run arbitrary code.
What is the component affected by the vulnerability?
The vulnerability affects Microsoft XML Core Services (MSXML) which allows customers who use JScript, Visual Basic Scripting Edition (VBScript), and Microsoft Visual Studio 6.0 to develop XML-based applications that provide interoperability with other applications that adhere to the XML 1.0 standard. For more information, see the MSDN site, MSXML.
What is Microsoft XML Core Services (MSXML)?
Microsoft XML Core Services (MSXML) allows customers who use JScript, Visual Basic Scripting Edition (VBScript), and Microsoft Visual Studio 6.0 to develop XML-based applications that provide interoperability with other applications that adhere to the XML 1.0 standard. For more information, see the MSDN site, MSXML.
What version of Microsoft XML Core Services is installed on my system?
Microsoft XML Core Services is included in additional non-operating system software from Microsoft and is also available as separate downloads. For information about the different Microsoft XML Core Services versions that are available and the products that install them, see Microsoft Knowledge Base Article 269238.
Note Depending on which version of Microsoft XML Core Services you have installed on your system, you may be offered more than one security update from this security bulletin.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code as the current user. If the current user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
How could an attacker exploit the vulnerability?
An attacker could exploit the vulnerability by hosting a specially crafted website that is designed to invoke MSXML through Internet Explorer. This can also include compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or in an Instant Messenger request that takes users to the attacker's website. It could also be possible to display specially crafted web content by using banner advertisements or by using other methods to deliver web content to affected systems.
Non-Microsoft web applications and services that utilize the MSXML library for parsing XML could also be vulnerable to this attack.
What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user is logged on and visits a website for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
What does the update do?
The update addresses the vulnerability by modifying the way that Microsoft XML Core Services parses XML content.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued. Update InformationDetection and Deployment Tools and Guidance
Security Central
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security website provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for 'security update.'
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, 'MS12-001'), you can add all the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates as well as common security misconfigurations. For more information, see Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please see Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
![]()
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
Note Microsoft discontinued support for SMS 2.0 on April 12, 2011. For SMS 2003, Microsoft also discontinued support for the Security Update Inventory Tool (SUIT) on April 12, 2011. Customers are encouraged to upgrade to System Center Configuration Manager. For customers remaining on SMS 2003 Service Pack 3, the Inventory Tool for Microsoft Updates (ITMU) is also an option.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager uses WSUS 3.0 for detection of updates. For more information, see System Center.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows XP (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Note The update for supported versions of Windows XP Professional x64 Edition also applies to supported versions of Windows Server 2003 x64 Edition.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, see Microsoft Knowledge Base Article 832475.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
The security updates for MSXML 3.0 and MSXML 6.0 on Windows XP Service Pack 3 support the following setup switches::
The security updates for MSXML 4.0 and MSXML 6.0 on Windows XP Professional x64 Edition Service Pack 2 support the following setup switches:
Removing the Update
This security update supports the following setup switches.
Windows Server 2003 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
If you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.
For more information about the installer, see Microsoft Knowledge Base Article 832475.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
The security updates for MSXML 3.0 support the following setup switches:
The security updates for MSXML 4.0 and MSXML 6.0 support the following setup switches:
Microsoft Xml Parser Unsupported
Removing the Update
This security update supports the following setup switches.
Windows Vista (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Microsoft Xml Parser And Xml Core Services Unsupported FixDeployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
The security updates for MSXML 3.0 and MSXML 6.0 support the following setup switches:
Supported Security Update Installation Switches
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
The security update for MSXML 4.0 supports the following setup switches:
Verifying That the Update Has Been Applied
Windows Server 2008 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
The security updates for MSXML 3.0 and MSXML 6.0 support the following setup switches:
Supported Security Update Installation Switches
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
The security update for MSXML 4.0 supports the following setup switches:
Verifying That the Update Has Been Applied
Windows 7 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
The security updates for MSXML 3.0 and MSXML 6.0 support the following setup switches:
Supported Security Update Installation Switches
Note For more information about the wusa.exe installer, see 'Windows Update Stand-alone Installer' in the TechNet article, Miscellaneous Changes in Windows 7.
The security update for MSXML 4.0 supports the following setup switches:
Verifying Thatthe Update Has Been Applied
Windows Server 2008 R2 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
The security updates for MSXML 3.0 and MSXML 6.0 support the following setup switches:
Supported Security Update Installation Switches
Note For more information about the wusa.exe installer, see 'Windows Update Stand-alone Installer' in the TechNet article, Miscellaneous Changes in Windows 7.
The security update for MSXML 4.0 supports the following setup switches:
Verifying That the Update Has Been Applied
Windows 8 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
The security updates for MSXML 3.0 and MSXML 6.0 support the following setup switches:
Supported Security Update Installation Switches
Note For more information about the wusa.exe installer, see 'Windows Update Stand-alone Installer' in the TechNet article, Miscellaneous Changes in Windows 7.
The security update for MSXML 4.0 supports the following setup switches:
Verifying Thatthe Update Has Been Applied
Windows Server 2012 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
The security updates for MSXML 3.0 and MSXML 6.0 support the following setup switches:
Supported Security Update Installation Switches
![]()
Note For more information about the wusa.exe installer, see 'Windows Update Stand-alone Installer' in the TechNet article, Miscellaneous Changes in Windows 7.
The security update for MSXML 4.0 supports the following setup switches:
Verifying That the Update Has Been Applied
Windows RT (all editions)
The following table contains the security update information for this software.
Office 2003 (all editions)Download Microsoft Xml Parser
Reference Table
The following table contains the security update information for this software. You can find additional information in the Deployment Information subsection below.
Supported Security Update Installation Switches
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
To remove this security update, use the Add or Remove Programs item in Control Panel.
Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Verifying that the Update Has Been Applied
Office 2007, Office Compatibility Pack, Word Viewer, Expression Web, and Expression Web 2 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Supported Security Update Installation Switches
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
To remove this security update, use the Add or Remove Programs item in Control Panel.
Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Verifying that the Update Has Been Applied
Microsoft Xml Parser Unsupported Windows 10Microsoft SharePoint Server 2007 and Microsoft Groove Server 2007
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Supported Security Update Installation Switches
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
To remove this security update, use the Add or Remove Programs item in Control Panel.
Note When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Verifying that the Update Has Been Applied
Other InformationAcknowledgments
Microsoft thanks the following for working with us to help protect customers:
Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please go to the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
How to obtain help and support for this security update
Disclaimer
The information provided in the Microsoft Knowledge Base is provided 'as is' without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
Built at 2014-04-18T13:49:36Z-07:00
-->
Vulnerability in XML Core Services Could Allow Remote Code Execution (2993958)
Published: November 11, 2014
Microsoft Xml Parser And Sdk
Version: 1.0
Executive Summary
This security update resolves a privately reported vulnerability in Microsoft Windows. The vulnerability could allow remote code execution if a logged-on user visits a specially crafted website that is designed to invoke Microsoft XML Core Services (MSXML) through Internet Explorer. In all cases, however, an attacker would have no way to force users to visit such websites. Instead, an attacker would have to convince users to visit a website, typically by getting them to click a link in an email message or in an Instant Messenger request that takes users to the attacker's website.
This security update for Microsoft XML Core Services 3.0 is rated Critical for affected releases of Microsoft Windows clients and Important for affected releases of Microsoft Windows servers. For more information, see the Affected Software section.
The security update addresses the vulnerability by modifying the way that Microsoft XML Core Services parses XML content. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability.
For more information about this document, see Knowledge Base Article 2993958.
Affected Software
The following software versions or editions are affected. Versions or editions that are not listed are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.
Note Windows Technical Preview and Windows Server Technical Preview are affected. Customers running these operating systems are encouraged to apply the update, which is available via Windows Update.
Update FAQ
What version of Microsoft XML Core Services is installed on my system?
Some versions of Microsoft XML Core Services are included with Microsoft Windows; others are installed with non-operating system software from Microsoft or third-party providers. Some are also available as separate downloads. The following table shows the supported releases of Microsoft Windows and indicates which versions of Microsoft XML Core Services are included with the operating system, and which versions are installed when you install additional Microsoft or third-party software.
MSXML Remote Code Execution Vulnerability - CVE-2014-4118
A remote code execution vulnerability exists when Microsoft XML Core Services (MSXML) improperly parses XML content, which can corrupt the system state in such a way as to allow an attacker to run arbitrary code. The vulnerability could allow remote code execution if a user opens a specially crafted file or webpage. Microsoft received information about this vulnerability through coordinated vulnerability disclosure. When this security bulletin was issued, Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers. The update addresses the vulnerability by modifying the way that Microsoft XML Core Services parses XML content.
Mitigating Factors
The following mitigating factors may be helpful in your situation:
Workarounds
Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
You can apply this .reg file to individual systems by double-clicking it. You can also apply it across domains by using Group Policy. For more information about Group Policy, see the TechNet article, Group Policy Collection.
Impact of workaround. Websites that use the XMLHTTP 3.0 ActiveX controls may no longer display or function correctly in Internet Explorer.
How to undo the workaround. Delete the registry keys previously added in implementing this workaround.
FAQ
What is the component affected by the vulnerability?
The vulnerability affects Microsoft XML Core Services (MSXML), which allows customers who use JScript, Visual Basic Scripting Edition (VBScript), and Microsoft Visual Studio 6.0 to develop XML-based applications that provide interoperability with other applications that adhere to the XML 1.0 standard. For more information, see the Microsoft Developer Network article, MSXML.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. If a user is logged on with administrative user rights, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
How could an attacker exploit the vulnerability?
An attacker could exploit the vulnerability by hosting a specially crafted website that is designed to invoke MSXML through Internet Explorer. This can also include compromised websites and websites that accept or host user-provided content or advertisements. These websites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or in an Instant Messenger request that takes users to the attacker's website. It could also be possible to display specially crafted web content by using banner advertisements or by using other methods to deliver web content to affected systems.
Non-Microsoft web applications and services that utilize the MSXML library for parsing XML could also be vulnerable to this attack.
What systems are primarily at risk from the vulnerability?
This vulnerability requires that a user be logged on and visiting a website for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
I am running Internet Explorer on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted web content on a server. This is a mitigating factor for websites that you have not added to the Internet Explorer Trusted sites zone. Security Update Deployment
For Security Update Deployment information, see the Microsoft Knowledge Base article referenced here in the Executive Summary.
Acknowledgments
Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgments for more information.
Disclaimer
The information provided in the Microsoft Knowledge Base is provided 'as is' without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
Page generated 2015-01-14 11:39Z-08:00.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |