Security Bulletin
Microsoft Security Bulletin MS12-043 - Critical
Vulnerability in Microsoft XML Core Services Could Allow Remote Code Execution (2722479)
Published: July 10, 2012 | Updated: April 26, 2013
Version: 4.2
General Information
Executive Summary
This security update resolves a publicly disclosed vulnerability in Microsoft XML Core Services. The vulnerability 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 supported editions of Windows XP, Windows Vista, and Windows 7; Critical for Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 8; Critical for Microsoft XML Core Services 5.0 when installed with all supported editions of Microsoft Office 2003, Microsoft Office 2007, Microsoft Office Word Viewer, Microsoft Office Compatibility Pack, Microsoft Expression Web, Microsoft Office SharePoint Server 2007, Microsoft Groove 2007, and Microsoft Groove Server 2007; Moderate for Microsoft XML Core Services 3.0, 4.0, and 6.0 on all supported editions of Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2; and Moderate for Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2012. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by modifying the way that MSXML initializes objects in memory before use. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
This security update also addresses the vulnerability first described in Microsoft Security Advisory 2719615.
Recommendation. The majority of 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 2722479 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, visit Microsoft Support Lifecycle.
Affected Software
Windows Operating Systems and Components
| Operating System | Component | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|---|
| Windows XP | ||||
| Windows XP Service Pack 3 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Critical | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 KB954459 in MS08-069 replaced by KB2719985 |
| Windows XP Professional x64 Edition Service Pack 2 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2721693) | Remote Code Execution | Critical | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 KB954459 in MS08-069 replaced by KB2721693 |
| Windows Server 2003 | ||||
| Windows Server 2003 Service Pack 2 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2721693) | Remote Code Execution | Moderate | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 KB954459 in MS08-069 replaced by KB2721693 |
| Windows Server 2003 x64 Edition Service Pack 2 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2721693) | Remote Code Execution | Moderate | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 KB954459 in MS08-069 replaced by KB2721693 |
| Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2721693) | Remote Code Execution | Moderate | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 KB954459 in MS08-069 replaced by KB2721693 |
| Windows Vista | ||||
| Windows Vista Service Pack 2 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Critical | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows Vista x64 Edition Service Pack 2 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Critical | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows Server 2008 | ||||
| Windows Server 2008 for 32-bit Systems Service Pack 2 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Moderate | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows Server 2008 for x64-based Systems Service Pack 2 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Moderate | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Moderate | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows 7 | ||||
| Windows 7 for 32-bit Systems | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Critical | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows 7 for 32-bit Systems Service Pack 1 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Critical | No updates replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows 7 for x64-based Systems | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Critical | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows 7 for x64-based Systems Service Pack 1 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Critical | No updates replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows Server 2008 R2 | ||||
| Windows Server 2008 R2 for x64-based Systems | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Moderate | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Moderate | No updates replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows Server 2008 R2 for Itanium-based Systems | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Moderate | KB2079403 in MS10-051 replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Microsoft XML Core Services 3.0 (KB2719985) Microsoft XML Core Services 4.0 (KB2721691) Microsoft XML Core Services 6.0 (KB2719985) | Remote Code Execution | Moderate | No updates replaced by KB2719985 No updates replaced by KB2721691 No updates replaced by KB2719985 |
| Windows 8 | ||||
| Windows 8 for 32-bit Systems | Microsoft XML Core Services 4.0 (KB2721691) | Remote Code Execution | Critical | None |
| Windows 8 for 64-bit Systems | Microsoft XML Core Services 4.0 (KB2721691) | Remote Code Execution | Critical | None |
| Windows Server 2012 | ||||
| Windows Server 2012 | Microsoft XML Core Services 4.0 (KB2721691) | Remote Code Execution | Moderate | None |
Microsoft Office Suites and Software
| Office Software | Component | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|---|
| Microsoft Office Suites and Components | ||||
| Microsoft Office 2003 Service Pack 3 | Microsoft XML Core Services 5.0 (KB2687627) | Remote Code Execution | Critical | KB951535 in MS08-069 replaced by KB2687324 or KB2687627 |
| Microsoft Office 2007 Service Pack 2 | Microsoft XML Core Services 5.0 (KB2596856) | Remote Code Execution | Critical | None |
| Microsoft Office 2007 Service Pack 3 | Microsoft XML Core Services 5.0 (KB2596856) | Remote Code Execution | Critical | None |
| Other Microsoft Office Software | ||||
| Microsoft Office Word Viewer | Microsoft XML Core Services 5.0 (KB2596856) | Remote Code Execution | Critical | None |
| Microsoft Office Compatibility Pack Service Pack 2 | Microsoft XML Core Services 5.0 (KB2596856) | Remote Code Execution | Critical | None |
| Microsoft Office Compatibility Pack Service Pack 3 | Microsoft XML Core Services 5.0 (KB2596856) | Remote Code Execution | Critical | None |
| Microsoft Groove 2007 Service Pack 2 | Microsoft XML Core Services 5.0 (KB2687497) | Remote Code Execution | Critical | None |
| Microsoft Groove 2007 Service Pack 3 | Microsoft XML Core Services 5.0 (KB2687497) | Remote Code Execution | Critical | None |
Microsoft Developer Tools and Software
| Software | Component | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|---|
| Microsoft Expression Web Service Pack 1 | Microsoft XML Core Services 5.0\ (KB2596856) | Remote Code Execution | Critical | None |
| Microsoft Expression Web 2 | Microsoft XML Core Services 5.0\ (KB2596856) | Remote Code Execution | Critical | KB951550 in MS08-069 replaced by KB2596856 |
Microsoft Server Software
| Software | Component | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced |
|---|---|---|---|---|
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Microsoft XML Core Services 5.0\ (KB2687497) | Remote Code Execution | Critical | None |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Microsoft XML Core Services 5.0\ (KB2687497) | Remote Code Execution | Critical | None |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions) | Microsoft XML Core Services 5.0\ (KB2687497) | Remote Code Execution | Critical | None |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions) | Microsoft XML Core Services 5.0\ (KB2687497) | Remote Code Execution | Critical | None |
| Microsoft Groove Server 2007 Service Pack 2 | Microsoft XML Core Services 5.0\ (KB2687497) | Remote Code Execution | Critical | None |
| Microsoft Groove Server 2007 Service Pack 3 | Microsoft XML Core Services 5.0\ (KB2687497) | Remote Code Execution | Critical | None |
Non-Affected Software
| Operating System |
|---|
| Microsoft MSXML Core Services 3.0 and Microsoft MSXML Core Services 6.0 on Windows 8 for 32-bit Systems |
| Microsoft MSXML Core Services 3.0 and Microsoft MSXML Core Services 6.0 on Windows 8 for 64-bit Systems |
| Microsoft MSXML Core Services 3.0 and Microsoft MSXML Core Services 6.0 on Windows Server 2012 |
| Operating System (Server Core installation) |
| Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) |
| Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) |
| Windows Server 2008 R2 for x64-based Systems (Server Core installation) |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) |
| Windows Server 2012 (Server Core installation) |
| Software |
| Microsoft Office 2010 (32-bit editions) |
| Microsoft Office 2010 Service Pack 1 (32-bit editions) |
| Microsoft Office 2010 (64-bit editions) |
| Microsoft Office 2010 Service Pack 1 (64-bit editions) |
| Microsoft SharePoint Server 2010 |
| Microsoft SharePoint Server 2010 Service Pack 1 |
| Microsoft Groove Server 2010 |
| Microsoft Visio 2010 (32-bit editions) |
| Microsoft Visio 2010 Service Pack 1 (32-bit editions) |
| Microsoft Visio 2010 (64-bit editions) |
| Microsoft Visio 2010 Service Pack 1 (64-bit editions) |
| Microsoft Visio Viewer 2010 and Microsoft Visio Viewer 2010 Service Pack 1 |
| Microsoft Office Web Apps 2010 |
| Microsoft Expression Web 3 |
| Microsoft Expression Web 4 |
| Microsoft Excel Viewer |
| Microsoft Visio Viewer 2010 |
| Microsoft Visio Viewer 2010 Service Pack 1 |
| Microsoft Works 9 |
| Microsoft Office 2008 for Mac |
| Microsoft Office for Mac 2011 |
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin rereleased on December 11, 2012?
In order to address an issue involving specific digital certificates that were generated by Microsoft without proper timestamp attributes, Microsoft rereleased this bulletin to replace the KB2687324 update with the KB2687627 update for Microsoft Office 2003 Service Pack 3 and to replace the KB2596679 update with the KB2687497 update for Microsoft XML Core Services 5.0 when installed with all affected editions of Microsoft Groove 2007, Microsoft Groove Server 2007, and Microsoft Office SharePoint Server 2007. For more information, see Microsoft Security Advisory 2749655.
I already successfully installed the original KB2687324or KB2596679 update. Should I apply the rereleased update packages (KB2687627and KB2687497 respectively) released on December 11, 2012?
Yes. Although customers who already successfully installed the original updates do not need to install the rereleased updates to be protected from the vulnerability described in this bulletin, the rereleased updates (KB2687627 and KB2687497) replace the original updates (KB2687324 and KB2596679 respectively) with a higher product version for the applicable software.
Customers with the original updates applied will be offered the rereleased updates. Customers should apply all updates offered for the version of software running on their systems.
Does the offer to update a non-vulnerable version of software constitute an issue in the Microsoft update mechanism?
No. The update mechanism is functioning correctly in that it detects a product version for the applicable software on the system that is within the range of product versions that the update applies to and thus, offers the update.
Why was this bulletin rereleased on October9, 2012?
Microsoft rereleased this bulletin to add Microsoft XML Core Services 4.0 when installed on supported editions of Windows 8 and Windows Server 2012 to affected software. Accordingly, customers should be aware of the following:
- A detection change for the KB2721691 update package; the update will be offered to systems running Microsoft XML Core Services 4.0 when installed on Windows 8 or Windows Server 2012.
- Customers who have installed Microsoft XML Core Services 4.0 on systems running Windows 8 or Windows Server 2012 need to install the KB2721691 update to be protected from the vulnerability described in this bulletin.
- There were no changes to the KB2721691 update files, only the detection logic was changed to offer the update to the newly affected configurations. Customers who have already successfully updated their systems do not need to take any action.
Note While Microsoft Update and enterprise detection and deployment tools, such as System Center Configuration Manager, support systems running Windows 8 and Windows Server 2012, the Microsoft Baseline Security Analyzer tool does not support detection on systems running Windows 8 or Windows Server 2012.
Why was this bulletin rereleased on August 14, 2012?
Microsoft rereleased this bulletin to offer the security updates for Microsoft XML Core Services 5.0 that were unavailable at the time of initial release. Customers who have already successfully installed the updates originally offered on July 10, 2012 for Microsoft XML Core Services 3.0, Microsoft XML Core Services 4.0, and Microsoft XML Core Services 6.0 do not need to take any action. However, customers running Microsoft XML Core Services 5.0 should apply the following updates according to the affected software installed on their systems:
- KB2687324 (for Microsoft XML Core Services 5.0 when installed with Microsoft Office 2003 Service Pack 3)
- KB2596856 (for Microsoft XML Core Services 5.0 when installed with all affected editions of Office 2007, Office Compatibility Pack, Office Word Viewer, Expression Web, and Expression Web 2)
- KB2596679 (for Microsoft XML Core Services 5.0 when installed with all affected editions of Microsoft Office SharePoint Server 2007, Microsoft Groove 2007, and Microsoft Groove Server 2007)
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.
| Operating System | MSXML 3.0 and MSXML 6.0 | MSXML 4.0 and MSXML 5.0 |
|---|---|---|
| Windows XP | Shipped with operating system | Installed with additional software |
| Windows Server 2003 | Shipped with operating system | Installed with additional software |
| Windows Vista | Shipped with operating system | Installed with additional software |
| Windows Server 2008 | Shipped with operating system | Installed with additional software |
| Windows 7 | Shipped with operating system | Installed with additional software |
| Windows Server 2008 R2 | Shipped with operating system | Installed with additional software |
| Windows 8 | Shipped with operating system | Installed with additional software |
| Windows Server 2012 | Shipped with operating system | Installed with additional 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.
Are Windows 8 Consumer Preview and Windows Server 2012 Consumer Preview affected by the vulnerability addressed in this bulletin?
Yes. The KB2719985 update is available for Windows 8 Consumer Preview and Windows Server 2012 Consumer Preview. Customers with Windows 8 Consumer Preview or Windows Server 2012 Consumer Preview are encouraged to apply the updates to their systems. The updates are only available on Windows Update.
Note At the time of the October 9, 2012 detection change to the KB2721691 update, Windows 8 Consumer Preview and Windows Server 2012 Consumer Preview were out of support.
Are Windows 8 Release Preview and Windows Server 2012 Release Candidateaffected by the vulnerability addressed in this bulletin?
Yes. The KB2719985 and KB2721691 updates are available for Windows 8 Release Preview and Windows Server 2012 Release Candidate. Customers with Windows 8 Release Preview and Windows Server 2012 Release Candidate are encouraged to apply the updates to their systems. The updates are only available on Windows Update.
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.
Where are the hashes of the security updates?
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 2722479.
How are Server Core installations affected by the vulnerability addressed in this bulletin?
The vulnerability addressed by this update does not affect supported editions of Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 as indicated in the Non-Affected Software table, when installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation: Overview, Servicing a Server Core Installation, and Server Core and Full Server Integration Overview.
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, visit 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, visit 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 Information
Severity 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 July bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | MSXML Uninitialized Memory Corruption Vulnerability - CVE-2012-1889 | Aggregate Severity Rating |
|---|---|---|
| Windows XP Service Pack 3 | ||
| Microsoft XML Core Services 3.0 on Windows XP Service Pack 3 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows XP Service Pack 3 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 6.0 on Windows XP Service Pack 3 | Critical Remote Code Execution | Critical |
| Windows XP Professional x64 Edition Service Pack 2 | ||
| Microsoft XML Core Services 3.0 on Windows XP Professional x64 Edition Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows XP Professional x64 Edition Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 6.0 on Windows XP Professional x64 Edition Service Pack 2 | Critical Remote Code Execution | Critical |
| Windows Server 2003 Service Pack 2 | ||
| Microsoft XML Core Services 3.0 on Windows Server 2003 Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2003 Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2003 Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Windows Server 2003 x64 Edition Service Pack 2 | ||
| Microsoft XML Core Services 3.0 on Windows Server 2003 x64 Edition Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2003 x64 Edition Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2003 x64 Edition Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Windows Server 2003 with SP2 for Itanium-based Systems | ||
| Microsoft XML Core Services 3.0 on Windows Server 2003 with SP2 for Itanium-based Systems | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2003 with SP2 for Itanium-based Systems | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2003 with SP2 for Itanium-based Systems | Moderate Remote Code Execution | Moderate |
| Windows Vista Service Pack 2 | ||
| Microsoft XML Core Services 3.0 on Windows Vista Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Vista Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 6.0 on Windows Vista Service Pack 2 | Critical Remote Code Execution | Critical |
| Windows Vista x64 Edition Service Pack 2 | ||
| Microsoft XML Core Services 3.0 on Windows Vista x64 Edition Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Vista x64 Edition Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 6.0 on Windows Vista x64 Edition Service Pack 2 | Critical Remote Code Execution | Critical |
| Windows Server 2008 for 32-bit Systems Service Pack 2 | ||
| Microsoft XML Core Services 3.0 on Windows Server 2008 for 32-bit Systems Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for 32-bit Systems Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2008 for 32-bit Systems Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Windows Server 2008 for x64-based Systems Service Pack 2 | ||
| Microsoft XML Core Services 3.0 on Windows Server 2008 for x64-based Systems Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for x64-based Systems Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2008 for x64-based Systems Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 | ||
| Microsoft XML Core Services 3.0 on Windows Server 2008 for Itanium-based Systems Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for Itanium-based Systems Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2008 for Itanium-based Systems Service Pack 2 | Moderate Remote Code Execution | Moderate |
| Windows 7 for 32-bit Systems | ||
| Microsoft XML Core Services 3.0 on Windows 7 for 32-bit Systems | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows 7 for 32-bit Systems | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 6.0 on Windows 7 for 32-bit Systems | Critical Remote Code Execution | Critical |
| Windows 7 for 32-bit Systems Service Pack 1 | ||
| Microsoft XML Core Services 3.0 on Windows 7 for 32-bit Systems Service Pack 1 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows 7 for 32-bit Systems Service Pack 1 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 6.0 on Windows 7 for 32-bit Systems Service Pack 1 | Critical Remote Code Execution | Critical |
| Windows 7 for x64-based Systems | ||
| Microsoft XML Core Services 3.0 on Windows 7 for x64-based Systems | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows 7 for x64-based Systems | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 6.0 on Windows 7 for x64-based Systems | Critical Remote Code Execution | Critical |
| Windows 7 for x64-based Systems Service Pack 1 | ||
| Microsoft XML Core Services 3.0 on Windows 7 for x64-based Systems Service Pack 1 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows 7 for x64-based Systems Service Pack 1 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 6.0 on Windows 7 for x64-based Systems Service Pack 1 | Critical Remote Code Execution | Critical |
| Windows Server 2008 R2 for x64-based Systems | ||
| Microsoft XML Core Services 3.0 on Windows Server 2008 R2 for x64-based Systems | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 R2 for x64-based Systems | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2008 R2 for x64-based Systems | Moderate Remote Code Execution | Moderate |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 | ||
| Microsoft XML Core Services 3.0 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Moderate Remote Code Execution | Moderate |
| Windows Server 2008 R2 for Itanium-based Systems | ||
| Microsoft XML Core Services 3.0 on Windows Server 2008 R2 for Itanium-based Systems | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 R2 for Itanium-based Systems | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2008 R2 for Itanium-based Systems | Moderate Remote Code Execution | Moderate |
| Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | ||
| Microsoft XML Core Services 3.0 on Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Moderate Remote Code Execution | Moderate |
| Microsoft XML Core Services 6.0 on Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Moderate Remote Code Execution | Moderate |
| Windows 8 for 32-bit Systems | ||
| Microsoft XML Core Services 4.0 when installed on Windows 8 for 32-bit Systems | Critical Remote Code Execution | Critical |
| Windows 8 for 64-bit Systems | ||
| Microsoft XML Core Services 4.0 when installed on Windows 8 for 64-bit Systems | Critical Remote Code Execution | Critical |
| Windows Server 2012 | ||
| Microsoft XML Core Services 4.0 when installed on Windows Server 2012 for 64-bit Systems | Moderate Remote Code Execution | Moderate |
| Microsoft Office | ||
| Microsoft XML Core Services 5.0 when installed with Microsoft Office 2003 Service Pack 3 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Office 2007 Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Office 2007 Service Pack 3 | Critical Remote Code Execution | Critical |
| Other Microsoft Office Software | ||
| Microsoft XML Core Services 5.0 when installed with Microsoft Office Word Viewer | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Office Compatibility Pack Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Office Compatibility Pack Service Pack 3 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Groove 2007 Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Groove 2007 Service Pack 3 | Critical Remote Code Execution | Critical |
| Microsoft Developer Tools and Software | ||
| Microsoft XML Core Services 5.0 when installed with Microsoft Expression Web Service Pack 1 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Expression Web 2 | Critical Remote Code Execution | Critical |
| Microsoft Server Software | ||
| Microsoft XML Core Services 5.0 when installed with Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions) | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions) | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Groove Server 2007 Service Pack 2 | Critical Remote Code Execution | Critical |
| Microsoft XML Core Services 5.0 when installed with Microsoft Groove Server 2007 Service Pack 3 | Critical Remote Code Execution | Critical |
MSXML Uninitialized Memory Corruption Vulnerability - CVE-2012-1889
A remote code execution vulnerability exists in the way that Microsoft XML Core Services handles objects in memory. The vulnerability could allow remote code execution if a user views a website that contains specially crafted content. An attacker who successfully exploited this vulnerability could take complete control of an 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.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2012-1889.
Mitigating Factors for MSXML Uninitialized Memory Corruption Vulnerability - CVE-2012-1889
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:
- In a web-based attack scenario, an attacker would have to host a website that contains a specially crafted webpage that is used to exploit this vulnerability. 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.
- An attacker who successfully exploited this vulnerability could gain the same user rights as the logged on user. 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.
- By default, all supported versions of Microsoft Outlook, Microsoft Outlook Express, and Windows Mail open HTML email messages in the Restricted sites zone. The Restricted sites zone, which disables script and ActiveX controls, helps reduce the risk of an attacker being able to use this vulnerability to execute malicious code. If a user clicks a link in an email message, the user could still be vulnerable to exploitation of this vulnerability through the web-based attack scenario.
- By default, Internet Explorer on Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates this vulnerability.
Workarounds for MSXML Uninitialized Memory Corruption Vulnerability - CVE-2012-1889
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:
Apply the Microsoft Fix it solution that blocks the attack vector for XML Core Services 5.0
See Microsoft Knowledge Base Article 2722479 for instructions on applying an automated Microsoft Fix it solution that blocks the attack vector for XML Core Services 5.0. We recommend that administrators review the KB article closely prior to deploying this Fix it solution.
Configure Internet Explorer to prompt before running Active Scripting or disable Active Scripting in the Internet and Local intranet security zone
You can help protect against this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps:
- In Internet Explorer, click Internet Options on the Tools menu.
- Click the Security tab.
- Click Internet, and then click Custom Level.
- Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
- Click Local intranet, and then click Custom Level.
- Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
- Click OK two times to return to Internet Explorer.
Note Disabling Active Scripting in the Internet and Local intranet security zones may cause some websites to work incorrectly. If you have difficulty using a website after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly.
Impact of workaround. There are side effects to prompting before running Active Scripting. Many websites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".
Add sites that you trust to the Internet Explorer Trusted sites zone
After you set Internet Explorer to require a prompt before it runs ActiveX controls and/or Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted websites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.
To do this, follow these steps:
- In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
- In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
- If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
- In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
- Repeat these steps for each site that you want to add to the zone.
- Click OK two times to accept the changes and return to Internet Explorer.
Note Add any sites that you trust not to take malicious action on your computer. Two in particular that you may want to add are "*.windowsupdate.microsoft.com" and "*.update.microsoft.com" (without the quotation marks). These are the sites that will host the update, and it requires an ActiveX Control to install the update.
Prevent an ActiveX control from being run in Internet Explorer
You can disable attempts to instantiate the MSXML 5.0 for Microsoft Office ActiveX control in Internet Explorer by setting the kill bit for the controls in the registry.Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
For detailed steps that you can use to prevent a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797. Follow the steps in the article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer.
To set the kill bit for the MSXML 5.0 for Microsoft Office ActiveX control, follow these steps:
Create a text file named Disable_MSXML5.reg with the following contents:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{88d969e5-f192-11d4-a65f-0040963251e5}]"Compatibility Flags"=dword:00000400[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{88d969e5-f192-11d4-a65f-0040963251e5}]"Compatibility Flags"=dword:00000400[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{88d969e6-f192-11d4-a65f-0040963251e5}]"Compatibility Flags"=dword:00000400[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{88d969e6-f192-11d4-a65f-0040963251e5}]"Compatibility Flags"=dword:00000400Double-click the .reg file to apply it to an individual system.
Restart Internet Explorer for your changes to take effect.
Note You can also apply the registry change across domains by using Group Policy. For more information about Group Policy, see Group Policy collection.
FAQ for MSXML Uninitialized Memory Corruption Vulnerability - CVE-2012-1889
What is the scope of the vulnerability?
This is a remote code execution vulnerability.
What causes the vulnerability?
The vulnerability is caused when MSXML attempts to access an object in memory that has not been initialized.
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 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 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. 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.
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 MSXML initializes objects in memory before use.
Does EMET help mitigate attacks that try to exploit this vulnerability?
Yes. The Enhanced Mitigation Experience Toolkit (EMET) helps mitigate the exploitation of this vulnerability by adding additional protection layers that make the vulnerability harder to exploit. EMET is a utility that helps prevent vulnerabilities in software from being successfully exploited for code execution, by applying the latest security mitigation technologies. At this time, EMET is provided with limited support and is only available in the English language. For more information, see Microsoft Knowledge Base Article 2458544.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CVE-2012-1889.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. Microsoft is aware of limited, targeted attacks attempting to exploit the vulnerability.
Update Information
Detection 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, "MS07-036"), you can add all of 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) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
| Software | MBSA |
|---|---|
| Windows XP Service Pack 3 | Yes |
| Windows XP Professional x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 Service Pack 2 | Yes |
| Windows Server 2003 x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 with SP2 for Itanium-based Systems | Yes |
| Windows Vista Service Pack 2 | Yes |
| Windows Vista x64 Edition Service Pack 2 | Yes |
| Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes |
| Windows Server 2008 for x64-based Systems Service Pack 2 | Yes |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes |
| Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Yes |
| Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Yes |
| Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Yes |
| Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Yes |
| Windows 8 for 32-bit Systems | No |
| Windows 8 for 64-bit Systems | No |
| Windows Server 2012 | No |
| Microsoft Office 2003 Service Pack 3 | Yes |
| Microsoft Office 2007 Service Pack 2 | Yes |
| Microsoft Office 2007 Service Pack 3 | Yes |
| Microsoft Office Word Viewer | Yes |
| Microsoft Office Compatibility Pack Service Pack 2 | Yes |
| Microsoft Office Compatibility Pack Service Pack 3 | Yes |
| Microsoft Groove 2007 Service Pack 2 | Yes |
| Microsoft Groove 2007 Service Pack 3 | Yes |
| Microsoft Expression Web Service Pack 1 | Yes |
| Microsoft Expression Web 2 | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions) | Yes |
| Microsoft Groove Server 2007 Service Pack 2 | Yes |
| Microsoft Groove Server 2007 Service Pack 3 | Yes |
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit 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.
| Software | SMS 2003 with ITMU | System Center Configuration Manager |
|---|---|---|
| Windows XP Service Pack 3 | Yes | Yes |
| Windows XP Professional x64 Edition Service Pack 2 | Yes | Yes |
| Windows Server 2003 Service Pack 2 | Yes | Yes |
| Windows Server 2003 x64 Edition Service Pack 2 | Yes | Yes |
| Windows Server 2003 with SP2 for Itanium-based Systems | Yes | Yes |
| Windows Vista Service Pack 2 | Yes | Yes |
| Windows Vista x64 Edition Service Pack 2 | Yes | Yes |
| Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes | Yes |
| Windows Server 2008 for x64-based Systems Service Pack 2 | Yes | Yes |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes | Yes |
| Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Yes | Yes |
| Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Yes | Yes |
| Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Yes | Yes |
| Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Yes | Yes |
| Windows 8 for 32-bit Systems | Yes | Yes |
| Windows 8 for 64-bit Systems | Yes | Yes |
| Windows Server 2012 | Yes | Yes |
| Microsoft Office 2003 Service Pack 3 | Yes | Yes |
| Microsoft Office 2007 Service Pack 2 | Yes | Yes |
| Microsoft Office 2007 Service Pack 3 | Yes | Yes |
| Microsoft Office Word Viewer | Yes | Yes |
| Microsoft Office Compatibility Pack Service Pack 2 | Yes | Yes |
| Microsoft Office Compatibility Pack Service Pack 3 | Yes | Yes |
| Microsoft Groove 2007 Service Pack 2 | Yes | Yes |
| Microsoft Groove 2007 Service Pack 3 | Yes | Yes |
| Microsoft Expression Web Service Pack 1 | Yes | Yes |
| Microsoft Expression Web 2 | Yes | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions) | Yes | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions) | Yes | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (32-bit editions) | Yes | Yes |
| Microsoft Office SharePoint Server 2007 Service Pack 3 (64-bit editions) | Yes | Yes |
| Microsoft Groove Server 2007 Service Pack 2 | Yes | Yes |
| Microsoft Groove Server 2007 Service Pack 3 | Yes | Yes |
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 about System Center Configuration Manager Software Update Management, visit System Center.
For more information about SMS, visit the SMS website.
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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 3.0 on Windows XP Service Pack 3:\ WindowsXP-KB2719985-x86-ENU.exe /quiet |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Service Pack 3:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on Windows XP Service Pack 3:\ WindowsXP-KB2719985-x86-ENU.exe /quiet | |
| For Microsoft XML Core Services 3.0 on Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB2719985-x64-ENU.exe /quiet | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Professional x64 Edition Service Pack 2:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on Windows XP Professional x64 Edition Service Pack 2:\ msxml6-KB2721693-enu-amd64.exe /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on Windows XP Service Pack 3:\ WindowsXP-KB2719985-x86-ENU.exe /norestart |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Service Pack 3:\ msxml4-KB2721691-enu.exe /norestart | |
| For Microsoft XML Core Services 6.0 on Windows XP Service Pack 3:\ WindowsXP-KB2719985-x86-ENU.exe /norestart | |
| For Microsoft XML Core Services 3.0 on Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB2719985-x64-ENU.exe /norestart | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Professional x64 Edition Service Pack 2:\ msxml4-KB2721691-enu.exe /norestart | |
| For Microsoft XML Core Services 6.0 on Windows XP Professional x64 Edition Service Pack 2:\ msxml6-KB2721693-enu-amd64.exe /norestart | |
| Update log file | For Microsoft XML Core Services 3.0 on all supported editions of Windows XP:\ KB2719985.log |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows XP:\ msxml4-KB2721691-enu.log | |
| For Microsoft XML Core Services 6.0 on Windows XP Service Pack 3:\ KB2719985.log | |
| For Microsoft XML Core Services 6.0 on Windows XP Professional x64 Edition Service Pack 2:\ KB2721693.log | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | For Microsoft XML Core Services 3.0 on all supported editions of Windows XP:\ Yes, you must restart your system after you apply this security update. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows XP:\ This update does not require a restart. | |
| For Microsoft XML Core Services 6.0 on Windows XP Service Pack 3:\ Yes, you must restart your system after you apply this security update. | |
| For Microsoft XML Core Services 6.0 on all Windows XP Professional Service Pack 2:\ This update does not require a restart. | |
| HotPatching | Not applicable |
| Removal Information | For Microsoft XML Core Services 3.0 on all supported editions of Windows XP:\ Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB2719985$\Spuninst folder |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows XP:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in Microsoft Knowledge Base Article 2721691 to remove the security update. | |
| For Microsoft XML Core Services 6.0 on Windows XP Service Pack 3:\ Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB2719985$\Spuninst folder | |
| For Microsoft XML Core Services 6.0 on Windows XP Professional Service Pack 2:\ Use Add or Remove Programs tool in Control Panel.\ Note Removing this security update for Microsoft XML Core Services 6 will completely remove MSXML6 from the system. | |
| File Information | For Microsoft XML Core Services 3.0 on all supported editions of Windows XP:\ See Microsoft Knowledge Base Article 2719985 |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows XP:\ See Microsoft Knowledge Base Article 2721691 | |
| For Microsoft XML Core Services 6.0 on all Windows XP Service Pack 3:\ See Microsoft Knowledge Base Article 2719985 | |
| For Microsoft XML Core Services 6.0 on all Windows XP Professional Service Pack 2:\ See Microsoft Knowledge Base Article 2721693 | |
| Registry Key Verification | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2719985\Filelist |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP3\Q2721691 | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB2719985\Filelist | |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB2719985\Filelist | |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows XP:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP3\Q2721691 | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows XP:\ Note A registry key does not exist to validate the presence of this update |
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.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting. |
| /nobackup | Does not back up files needed for uninstall. |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program. |
| /ER | Enables extended error reporting. |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports 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
The security updates for MSXML 3.0 and MSXML 6.0 support the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows Server 2003:\ WindowsServer2003-KB2719985-x86-ENU.exe /quiet |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows Server 2003:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit editions of Windows Server 2003:\ msxml6-KB2721693-enu-x86.exe /quiet | |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Server 2003:\ WindowsServer2003.WindowsXP-KB2719985-x64-ENU.exe /quiet | |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Server 2003:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows Server 2003:\ msxml6-KB2721693-enu-amd64.exe /quiet | |
| For Microsoft XML Core Services 3.0 on all supported Itanium-based editions of Windows Server 2003:\ WindowsServer2003-KB2719985-ia64-ENU.exe /quiet | |
| For Microsoft XML Core Services 4.0 when installed on all supported Itanium-based editions of Windows Server 2003:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported Itanium-based editions of Windows Server 2003:\ msxml6-KB2721693-enu-ia64.exe /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows Server 2003:\ WindowsServer2003-KB2719985-x86-ENU.exe /norestart |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows Server 2003:\ msxml4-KB2721691-enu.exe /norestart | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit editions of Windows Server 2003:\ msxml6-KB2721693-enu-x86.exe /norestart | |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Server 2003:\ WindowsServer2003.WindowsXP-KB2719985-x64-ENU.exe /norestart | |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Server 2003:\ msxml4-KB2721691-enu.exe /norestart | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows Server 2003:\ msxml6-KB2721693-enu-amd64.exe /norestart | |
| For Microsoft XML Core Services 3.0 on all supported Itanium-based editions of Windows Server 2003:\ WindowsServer2003-KB2719985-ia64-ENU.exe /norestart | |
| For Microsoft XML Core Services 4.0 when installed on all supported Itanium-based editions of Windows Server 2003:\ msxml4-KB2721691-enu.exe /norestart | |
| For Microsoft XML Core Services 6.0 on all supported Itanium-based editions of Windows Server 2003:\ msxml6-KB2721693-enu-ia64.exe /norestart | |
| Update log file | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2003:\ KB2719985.log |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 Service Pack 2:\ msxml4-KB2721691-enu.log | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 x64 Edition Service Pack 2:\ msxml4-KB2721691-enu.log | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 with SP2 for Itanium-based Systems:\ Not applicable | |
| For Microsoft XML Core Services 6.0 on Windows Server 2003 Service Pack 2:\ msxml6-KB2721693-enu-x86.log | |
| For Microsoft XML Core Services 6.0 on Windows Server 2003 x64 Edition Service Pack 2:\ msxml6-KB2721693-enu-x64.log | |
| For Microsoft XML Core Services 6.0 on Windows Server 2003 with SP2 for Itanium-based Systems:\ msxml6-KB2721693-enu-ia64.log | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2003:\ Yes, you must restart your system after you apply this security update. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2003:\ This update does not require a restart. | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2003:\ This update does not require a restart. | |
| HotPatching | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. |
| Removal Information | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2003:\ Use Add or Remove Programs item in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB2719985$\Spuninst folder |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2003:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in Microsoft Knowledge Base Article 2721691 to remove the security update. | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2003:\ Use Add or Remove Programs tool in Control Panel.\ Note Removing this security update for Microsoft XML Core Services 6 will completely remove MSXML6 from the system. | |
| File Information | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2003:\ See Microsoft Knowledge Base Article 2719985 |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2003:\ See Microsoft Knowledge Base Article 2721691 | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2003:\ See Microsoft Knowledge Base Article 2721693 | |
| Registry Key Verification | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2003:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2719985\Filelist |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2003:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP3\Q2721691 | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2003:\ Note A registry key does not exist to validate the presence of this update |
Note The update for supported versions of Windows Server 2003 x64 Edition also applies to supported versions of Windows XP Professional 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.
This security update supports the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /overwriteoem | Overwrites OEM files without prompting. |
| /nobackup | Does not back up files needed for uninstall. |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
| /integrate:path | Integrates the update into the Windows source files. These files are located at the path that is specified in the switch. |
| /extract[:path] | Extracts files without starting the Setup program. |
| /ER | Enables extended error reporting. |
| /verbose | Enables verbose logging. During installation, creates %Windir%\CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly. |
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
The security updates for MSXML 3.0 and MSXML 6.0 support the following setup switches.
| Switch | Description |
|---|---|
| /help | Displays the command-line options. |
| Setup Modes | |
| /passive | Unattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds. |
| /quiet | Quiet mode. This is the same as unattended mode, but no status or error messages are displayed. |
| Restart Options | |
| /norestart | Does not restart when installation has completed. |
| /forcerestart | Restarts the computer after installation and force other applications to close at shutdown without saving open files first. |
| /warnrestart[:x] | Presents a dialog box with a timer warning the user that the computer will restart in x seconds. (The default setting is 30 seconds.) Intended for use with the /quiet switch or the /passive switch. |
| /promptrestart | Displays a dialog box prompting the local user to allow a restart. |
| Special Options | |
| /forceappsclose | Forces other programs to close when the computer shuts down. |
| /log:path | Allows the redirection of installation log files. |
Verifying that the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start, and then click Search.
- In the Search Results pane, click All files and folders under Search Companion.
- In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
- In the list of files, right-click a file name from the appropriate file information table, and then click Properties.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - On the Version tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Registry Key Verification
You may also be able to verify the files that this security update has installed by reviewing the registry keys listed in the Reference Table in this section.These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly when an administrator or an OEM integrates or slipstreams this security update into the Windows installation source files.
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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2719985-x86.msu /quiet |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows Vista:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2719985-x86.msu /quiet | |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Vista:\ Windows6.0-KB2719985-x64.msu /quiet | |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Vista:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows Vista:\ Windows6.0-KB2719985-x64.msu /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2719985-x86.msu /quiet /norestart |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows Vista:\ msxml4-KB2721691-enu.exe /quiet /norestart | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit editions of Windows Vista:\ Windows6.0-KB2719985-x86.msu /quiet /norestart | |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Vista:\ Windows6.0-KB2719985-x64.msu /quiet /norestart | |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Vista:\ msxml4-KB2721691-enu.exe /quiet /norestart | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows Vista:\ Windows6.0-KB2719985-x64.msu /quiet /norestart | |
| Update log file | For Microsoft XML Core Services 3.0 on all supported editions of Windows Vista:\ Not applicable |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Vista:\ msxml4-KB2721691-enu.log | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Vista:\ Not applicable | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | For Microsoft XML Core Services 3.0 on all supported editions of Windows Vista:\ Yes, you must restart your system after you apply this security update. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Vista:\ This update does not require a restart. | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Vista:\ Yes, you must restart your system after you apply this security update. | |
| HotPatching | Not applicable. |
| Removal Information | For Microsoft XML Core Services 3.0 and Microsoft XML Core Services 6.0 on all supported editions of Windows Vista:\ WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.\ \ For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Vista:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in Microsoft Knowledge Base Article 2721691 to remove the security update. |
| File Information | For Microsoft XML Core Services 3.0 on all supported editions of Windows Vista:\ See Microsoft Knowledge Base Article 2719985 |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Vista:\ See Microsoft Knowledge Base Article 2721691 | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Vista:\ See Microsoft Knowledge Base Article 2719985 | |
| Registry Key Verification | For Microsoft XML Core Services 3.0 on all supported editions of Windows Vista:\ Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Vista:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP3\Q2721691 | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Vista:\ Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. |
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.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB2719985-x86.msu /quiet |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows Server 2008:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB2719985-x86.msu /quiet | |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2719985-x64.msu /quiet | |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Server 2008:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2719985-x64.msu /quiet | |
| For Microsoft XML Core Services 3.0 on all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2719985-ia64.msu /quiet | |
| For Microsoft XML Core Services 4.0 when installed on all supported Itanium-based editions of Windows Server 2008:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2719985-ia64.msu /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB2719985-x86.msu /quiet /norestart |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows Server 2008:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit editions of Windows Server 2008:\ Windows6.0-KB2719985-x86.msu /quiet /norestart | |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2719985-x64.msu /quiet /norestart | |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Server 2008:\ msxml4-KB2721691-enu.exe /quiet /norestart | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows Server 2008:\ Windows6.0-KB2719985-x64.msu /quiet /norestart | |
| For Microsoft XML Core Services 3.0 on all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2719985-ia64.msu /quiet /norestart | |
| For Microsoft XML Core Services 4.0 when installed on all supported Itanium-based editions of Windows Server 2008:\ msxml4-KB2721691-enu.exe /quiet /norestart | |
| For Microsoft XML Core Services 6.0 on all supported Itanium-based editions of Windows Server 2008:\ Windows6.0-KB2719985-ia64.msu /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2008:\ Yes, you must restart your system after you apply this security update. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008:\ This update does not require a restart. | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008:\ Yes, you must restart your system after you apply this security update. | |
| Update log file | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2008:\ Not applicable |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008:\ msxml4-KB2721691-enu.log | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008:\ Not applicable | |
| HotPatching | Not applicable. |
| Removal Information | For Microsoft XML Core Services 3.0 and Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008:\ WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.\ \ For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in Microsoft Knowledge Base Article 2721691 to remove the security update. |
| File Information | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2008:\ See Microsoft Knowledge Base Article 2719985 |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008:\ See Microsoft Knowledge Base Article 2721691 | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008:\ See Microsoft Knowledge Base Article 2719985 | |
| Registry Key Verification | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2008:\ Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP3\Q2721691 | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008:\ Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. |
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.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
Note For more information about the wusa.exe installer, see Microsoft Knowledge Base Article 934307.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows 7:\ Windows6.1-KB2719985-x86.msu /quiet |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows 7:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit editions of Windows 7:\ Windows6.1-KB2719985-x86.msu /quiet | |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows 7:\ Windows6.1-KB2719985-x64.msu /quiet | |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows 7:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows 7:\ Windows6.1-KB2719985-x64.msu /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows 7:\ Windows6.1-KB2719985-x86.msu /quiet /norestart |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows 7:\ msxml4-KB2721691-enu.exe /quiet /norestart | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit editions of Windows 7:\ Windows6.1-KB2719985-x86.msu /quiet /norestart | |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows 7:\ Windows6.1-KB2719985-x64.msu /quiet /norestart | |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows 7:\ msxml4-KB2721691-enu.exe /quiet /norestart | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows 7:\ Windows6.1-KB2719985-x64.msu /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | For Microsoft XML Core Services 3.0 on all supported editions of Windows 7:\ Yes, you must restart your system after you apply this security update. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 7:\ This update does not require a restart. | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows 7:\ Yes, you must restart your system after you apply this security update. | |
| HotPatching | Not applicable. |
| Removal Information | For Microsoft XML Core Services 3.0 and Microsoft XML Core Services 6.0 on all supported editions of Windows 7:\ WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.\ \ For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 7:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in Microsoft Knowledge Base Article 2721691 to remove the security update. |
| File Information | For Microsoft XML Core Services 3.0 on all supported editions of Windows 7:\ See Microsoft Knowledge Base Article 2719985 |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 7:\ See Microsoft Knowledge Base Article 2721691 | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows 7:\ See Microsoft Knowledge Base Article 2719985 | |
| Registry Key Verification | For Microsoft XML Core Services 3.0 on all supported editions of Windows 7:\ Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 7:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP3\Q2721691 | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows 7:\ Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. |
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.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
| /warnrestart:<seconds> | When combined with /quiet, the installer will warn the user before initiating restart. |
| /promptrestart | When combined with /quiet, the installer will prompt before initiating restart. |
| /forcerestart | When combined with /quiet, the installer will forcefully close applications and initiate restart. |
| /log:<file name> | Enables logging to specified file. |
| /extract:<destination> | Extracts the package contents to the destination folder. |
| /uninstall /kb:<KB Number> | Uninstalls the security update. |
Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2719985-x64.msu /quiet |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Server 2008 R2:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2719985-x64.msu /quiet | |
| For Microsoft XML Core Services 3.0 on all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2719985-ia64.msu /quiet | |
| For Microsoft XML Core Services 4.0 when installed on all supported Itanium-based editions of Windows Server 2008 R2:\ msxml4-KB2721691-enu.exe /quiet | |
| For Microsoft XML Core Services 6.0 on all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2719985-ia64.msu /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2719985-x64.msu /quiet /norestart |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Server 2008 R2:\ msxml4-KB2721691-enu.exe /quiet /norestart | |
| For Microsoft XML Core Services 6.0 on all supported x64-based editions of Windows Server 2008 R2:\ Windows6.1-KB2719985-x64.msu /quiet /norestart | |
| For Microsoft XML Core Services 3.0 on all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2719985-ia64.msu /quiet /norestart | |
| For Microsoft XML Core Services 4.0 when installed on all supported Itanium-based editions of Windows Server 2008 R2:\ msxml4-KB2721691-enu.exe /quiet /norestart | |
| For Microsoft XML Core Services 6.0 on all supported Itanium-based editions of Windows Server 2008 R2:\ Windows6.1-KB2719985-ia64.msu /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2008 R2:\ Yes, you must restart your system after you apply this security update. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008 R2:\ This update does not require a restart. | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008 R2:\ Yes, you must restart your system after you apply this security update. | |
| HotPatching | Not applicable. |
| Removal Information | For Microsoft XML Core Services 3.0 and Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008 R2:\ WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.\ \ For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008 R2:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in Microsoft Knowledge Base Article 2721691 to remove the security update. |
| File Information | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2008 R2:\ See Microsoft Knowledge Base Article 2719985 |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008 R2:\ See Microsoft Knowledge Base Article 2721691 | |
| For Microsoft XML Core Services 6.0 when installed on all supported editions of Windows Server 2008 R2:\ See Microsoft Knowledge Base Article 2719985 | |
| Registry Key Verification | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2008 R2:\ Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. |
| For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2008 R2:\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\MSXML4SP3\Q2721691 | |
| For Microsoft XML Core Services 6.0 on all supported editions of Windows Server 2008 R2:\ Note A registry key does not exist to validate the presence of this update. Use WMI to detect for the presence of this patch. |
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.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
| /warnrestart:<seconds> | When combined with /quiet, the installer will warn the user before initiating restart. |
| /promptrestart | When combined with /quiet, the installer will prompt before initiating restart. |
| /forcerestart | When combined with /quiet, the installer will forcefully close applications and initiate restart. |
| /log:<file name> | Enables logging to specified file. |
| /extract:<destination> | Extracts the package contents to the destination folder. |
| /uninstall /kb:<KB Number> | Uninstalls the security update. |
Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows 8:\ msxml4-KB2721691-enu.exe /quiet |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows 8:\ msxml4-KB2721691-enu.exe /quiet | |
| Installing without restarting | For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows 8:\ msxml4-KB2721691-enu.exe /quiet /norestart |
| For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows 8:\ msxml4-KB2721691-enu.exe /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 8:\ This update does not require a restart. |
| HotPatching | Not applicable. |
| Removal Information | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 8:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in Microsoft Knowledge Base Article 2721691 to remove the security update. |
| File Information | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 8:\ See Microsoft Knowledge Base Article 2721691 |
| Registry Key Verification | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows 8:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP3\Q2721691 |
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.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
| /warnrestart:<seconds> | When combined with /quiet, the installer will warn the user before initiating restart. |
| /promptrestart | When combined with /quiet, the installer will prompt before initiating restart. |
| /forcerestart | When combined with /quiet, the installer will forcefully close applications and initiate restart. |
| /log:<file name> | Enables logging to specified file. |
| /extract:<destination> | Extracts the package contents to the destination folder. |
| /uninstall /kb:<KB Number> | Uninstalls the security update. |
Verifying That the Update Has Been Applied
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2012:\ msxml4-KB2721691-enu.exe /quiet |
| Installing without restarting | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2012:\ msxml4-KB2721691-enu.exe /quiet /norestart |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2012:\ This update does not require a restart. |
| HotPatching | Not applicable. |
| Removal Information | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2012:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in Microsoft Knowledge Base Article 2721691 to remove the security update. |
| File Information | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2012:\ See Microsoft Knowledge Base Article 2721691 |
| Registry Key Verification | For Microsoft XML Core Services 4.0 when installed on all supported editions of Windows Server 2012:\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\MSXML4SP3\Q2721691 |
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.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /?, /h, /help | Displays help on supported switches. |
| /quiet | Suppresses the display of status or error messages. |
| /norestart | When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation. |
| /warnrestart:<seconds> | When combined with /quiet, the installer will warn the user before initiating restart. |
| /promptrestart | When combined with /quiet, the installer will prompt before initiating restart. |
| /forcerestart | When combined with /quiet, the installer will forcefully close applications and initiate restart. |
| /log:<file name> | Enables logging to specified file. |
| /extract:<destination> | Extracts the package contents to the destination folder. |
| /uninstall /kb:<KB Number> | Uninstalls the security update. |
Verifying That the Update Has Been Applied
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Office 2003 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the Deployment Information subsection below.
| Inclusion in Future Service Packs | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 5.0 when installed with Microsoft Office 2003 Service Pack 3:\ office2003-kb2687627-fullfile-enu.exe /q:a |
| Installing without restarting | For Microsoft XML Core Services 5.0 when installed with Microsoft Office 2003 Service Pack 3:\ office2003-kb2687627-fullfile-enu.exe /r:n |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. \ \ For features you can selectively install, see the Office Features for Administrative Installations subsection in this section. |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| Removal Information | Use 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. |
| File Information | See Microsoft Knowledge Base Article 2687627 |
| Registry Key Verification | Not applicable |
Office Features
The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features:
| Product | Feature |
|---|---|
| ACCESSRT, OUTLS11, VISVEA, RMS, BASIC11, FP11, ONOTE11, OUTLSM11, PERS11, PUB11, STDP11, STD11, INF11, PRJPROE, PRJPRO, PRJSTDE, PRJSTD, VISPRO, VISPROR, VISSTD, VISSTDR | ProductNonBootFiles |
| PPT11, ACC11, OUTL11, PRO11SB, PROI11, PRO11, WORD11, EXCEL11 | ProductNonBootFiles,LISTFiles |
Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer.
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 2.0 or later version be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.
To install the 2.0 or later version of Windows Installer, visit one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000
- Windows Installer 2.0 Redistributable for Microsoft Windows 2000 and Windows NT 4.0
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /q:u | Specifies user-quiet mode, which presents some dialog boxes to the user. |
| /q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. |
| /t:path | Specifies the target folder for extracting files. |
| /c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
| /c:path | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /r:n | Never restarts the system after installation. |
| /r:I | Prompts the user to restart the system if a restart is required, except when used with /q:a. |
| /r:a | Always restarts the system after installation. |
| /r:s | Restarts the system after installation without prompting the user. |
| /n:v | No version checking - Install the program over any earlier version. |
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
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
- Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Office 2007, Office Compatibility Pack, Office 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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 5.0 when installed with all affected editions of Office 2007, Office Compatibility Pack, Office Word Viewer, Expression Web, and Expression Web 2:\ msxml52007-kb2596856-fullfile-x86-glb.exe /passive |
| Installing without restarting | For Microsoft XML Core Services 5.0 when installed with all affected editions of Office 2007, Office Compatibility Pack, Office Word Viewer, Expression Web, and Expression Web 2:\ msxml52007-kb2596856-fullfile-x86-glb.exe /norestart |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| Removal Information | Use Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2596856 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
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 Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Microsoft Office SharePoint Server 2007, Microsoft Groove Server 2007, Microsoft Groove 2007 (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.
| Inclusion in Future Service Packs | The update for this issue will be included in a future service pack or update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 5.0 when installed with all affected 32-bit editions of Microsoft Office SharePoint Server 2007 and Microsoft Groove 2007:\ msxml52007-kb2687497-fullfile-x86-glb.exe /passive |
| For Microsoft XML Core Services 5.0 when installed with all affected 64-bit editions of Microsoft Office SharePoint Server 2007 and Microsoft Groove Server 2007:\ msxml52007-kb2687497-fullfile-x64-glb.exe /passive | |
| Installing without restarting | For Microsoft XML Core Services 5.0 when installed with all affected 32-bit editions of Microsoft Office SharePoint Server 2007 and Microsoft Groove 2007:\ msxml52007-kb2687497-fullfile-x86-glb.exe /norestart |
| For Microsoft XML Core Services 5.0 when installed with all affected 64-bit editions of Microsoft Office SharePoint Server 2007 and Microsoft Groove Server 2007:\ msxml52007-kb2687497-fullfile-x64-glb.exe /norestart | |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| HotPatching | Not applicable |
| Removal Information | Use Add or Remove Programs item in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 2687497 |
| Registry Key Verification | Not applicable |
Deployment Information
Installing the Update
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later version be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft websites:
- Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP
- Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Microsoft Windows 2000
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
| Switch | Description |
|---|---|
| /? or /help | Displays usage dialog. |
| /passive | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. |
| /quiet | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /norestart | Suppresses restarting the system if the update requires a restart. |
| /forcerestart | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. |
| /extract | Extracts the files without installing them. You are prompted for a target folder. |
| /extract:<path> | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /lang:<LCID> | Forces the use of a specific language, when the update package supports that language. |
| /log:<log file> | Enables logging, by both Vnox and Installer, during the update installation. |
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 Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.- Click Start and then enter an update file name in the Start Search box.
- When the file appears under Programs, right-click the file name and click Properties.
- On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some files that are listed in the file information table may not be installed. - You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. - Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Google Security Team for working with us on the MSXML Uninitialized Memory Corruption Vulnerability (CVE-2012-1889)
- Qihoo 360 Security Center for reporting the MSXML Uninitialized Memory Corruption Vulnerability (CVE-2012-1889)
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 visit 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
- Help installing updates: Support for Microsoft Update
- Security solutions for IT professionals: TechNet Security Troubleshooting and Support
- Help protect your computer that is running Windows from viruses and malware: Virus Solution and Security Center
- Local support according to your country: International Support
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
- V1.0 (July 10, 2012): Bulletin published.
- V1.1 (July 31, 2012): Bulletin revised to announce a detection change in the Windows Vista packages for KB2719985 to correct a Windows Update reoffering issue. This is a detection change only. Customers who have already successfully updated their systems do not need to take any action.
- V2.0 (August 14, 2012): Bulletin rereleased to offer the security updates for Microsoft XML Core Services 5.0 that were unavailable at the time of initial release. Customers running Microsoft XML Core Services 5.0 should apply the KB2687324, KB2596856, or KB2596679 update to be protected from the vulnerability described in this bulletin. Customers who have already successfully installed the updates originally offered on July 10, 2012 for Microsoft XML Core Services 3.0, Microsoft XML Core Services 4.0, and Microsoft XML Core Services 6.0 do not need to take any action. See the Update FAQ for details.
- V2.1 (August 15, 2012): Corrected download links for Microsoft Groove Server 2007 and other Microsoft Office software. Added download links and update information for Microsoft Groove 2007. These are informational changes only. Customers who have already successfully updated their systems do not need to take any action.
- V3.0 (October 9, 2012): Added Microsoft XML Core Services 4.0 when installed on supported editions of Windows 8 and Windows Server 2012 to affected software and announced a corresponding detection change for the KB2721691 update package. Customers who have installed Microsoft XML Core Services 4.0 on systems running Windows 8 or Windows Server 2012 need to install the KB2721691 update to be protected from the vulnerability described in this bulletin. See the update FAQ for details.
- V3.1 (October 23, 2012): Added the KB2721691 update to the Bulletin FAQ that explains which updates are available for Windows 8 Release Preview and Windows Server 2012 Release Candidate.
- V4.0 (December 11, 2012): Rereleased bulletin to replace the KB2687324 update with the KB2687627 update for Microsoft XML Core Services 5.0 when installed on Microsoft Office 2003 Service Pack 3, and to replace the KB2596679 update with the KB2687497 update for Microsoft XML Core Services 5.0 when installed with all affected editions of Microsoft Groove 2007, Microsoft Groove Server 2007, and Microsoft Office SharePoint Server 2007. See the update FAQ for details.
- V4.1 (January 30, 2013): Clarified that customers with the KB2687324 and KB2596679 updates will be offered the KB2687627 and KB2687497 updates respectively for Microsoft XML Core Services 5.0. See the update FAQ for details.
- V4.2 (April 26, 2013): Corrected update replacement. This is an informational change only. There were no changes to the security update files or detection logic.
Built at 2014-04-18T13:49:36Z-07:00