Security Bulletin
Microsoft Security Bulletin MS08-069 - Critical
Vulnerabilities in Microsoft XML Core Services Could Allow Remote Code Execution (955218)
Published: November 11, 2008 | Updated: July 12, 2011
Version: 4.0
General Information
Executive Summary
This security update resolves several vulnerabilities in Microsoft XML Core Services. The most severe vulnerability could allow remote code execution if a user viewed a specially crafted Web page using Internet Explorer. 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.
This security update is rated Critical for Microsoft XML Core Services 3.0 and Important for Microsoft XML Core Services 4.0, Microsoft XML Core Services 5.0, and Microsoft XML Core Services 6.0. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerabilities by modifying the way that Microsoft XML Core Services parses XML content, handles external document type definitions (DTD), and sets HTTP request fields. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update immediately.
Known Issues. Microsoft Knowledge Base Article 955218 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.
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
| Software | Component | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|---|
| Windows 2000 | ||||
| Microsoft Windows 2000 Service Pack 4 | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | MS07-042 |
| Microsoft Windows 2000 Service Pack 4 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Important | MS07-042 |
| Microsoft Windows 2000 Service Pack 4 | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Important | MS07-042 |
| Windows XP | ||||
| Windows XP Service Pack 2 | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | MS07-042 |
| Windows XP Service Pack 3 | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | None |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Important | MS07-042 |
| Windows XP Service Pack 2 | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Important | MS07-042 |
| Windows XP Service Pack 3 | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Important | None |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | MS07-042 |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Important | MS07-042 |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Important | MS07-042 |
| Windows Server 2003 | ||||
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | MS07-042 |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | MS07-042 |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Low | MS07-042 |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | MS07-042 |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | MS07-042 |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Low | MS07-042 |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | MS07-042 |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | MS07-042 |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Low | MS07-042 |
| Windows Vista | ||||
| Windows Vista | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | MS07-042 |
| Windows Vista Service Pack 1 | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | None |
| Windows Vista and Windows Vista Service Pack 1 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Important | MS07-042 |
| Windows Vista Service Pack 2 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Important | None |
| Windows Vista | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Important | MS07-042 |
| Windows Vista Service Pack 1 | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Important | None |
| Windows Vista x64 Edition | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | MS07-042 |
| Windows Vista x64 Edition Service Pack 1 | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | None |
| Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Important | MS07-042 |
| Windows Vista x64 Edition Service Pack 2 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Important | None |
| Windows Vista x64 Edition | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Important | MS07-042 |
| Windows Vista x64 Edition Service Pack 1 | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Important | None |
| Windows Server 2008 | ||||
| Windows Server 2008 for 32-bit Systems* | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | None |
| Windows Server 2008 for 32-bit Systems* | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | MS07-042 |
| Windows Server 2008 for 32-bit Systems Service Pack 2* | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | None |
| Windows Server 2008 for 32-bit Systems* | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Low | None |
| Windows Server 2008 for x64-based Systems* | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | None |
| Windows Server 2008 for x64-based Systems* | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | MS07-042 |
| Windows Server 2008 for x64-based Systems Service Pack 2* | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | None |
| Windows Server 2008 for x64-based Systems* | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Low | None |
| Windows Server 2008 for Itanium-based Systems | Microsoft XML Core Services 3.0 (KB955069) | Remote Code Execution | Critical | None |
| Windows Server 2008 for Itanium-based Systems | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | MS07-042 |
| Windows Server 2008 for Itanium-based Systems Service Pack 2 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | None |
| Windows Server 2008 for Itanium-based Systems | Microsoft XML Core Services 6.0 (KB954459) | Information Disclosure | Low | None |
| Windows 7 | ||||
| Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Important | None |
| Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Important | None |
| Windows Server 2008 R2 | ||||
| Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1* | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | None |
| Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Microsoft XML Core Services 4.0 (KB954430) | Information Disclosure | Low | None |
| Microsoft Office | ||||
| Microsoft Office 2003 Service Pack 3 | Microsoft XML Core Services 5.0 (KB951535) | Information Disclosure | Important | None |
| Microsoft Word Viewer 2003 Service Pack 3 | Microsoft XML Core Services 5.0 (KB951535) | Information Disclosure | Important | None |
| 2007 Microsoft Office System | Microsoft XML Core Services 5.0 (KB951550) | Information Disclosure | Important | MS07-042 |
| 2007 Microsoft Office System Service Pack 1 | Microsoft XML Core Services 5.0 (KB951550) | Information Disclosure | Important | None |
| Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats | Microsoft XML Core Services 5.0 (KB951550) | Information Disclosure | Important | MS07-042 |
| Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 | Microsoft XML Core Services 5.0 (KB951550) | Information Disclosure | Important | None |
| Microsoft Expression Web | Microsoft XML Core Services 5.0 (KB951550) | Information Disclosure | Important | MS07-042 |
| Microsoft Expression Web 2 | Microsoft XML Core Services 5.0 (KB951550) | Information Disclosure | Important | None |
| Microsoft Office SharePoint Server 2007 (32-bit editions) | Microsoft XML Core Services 5.0 (KB951597) | Information Disclosure | Important | MS07-042 |
| Microsoft Office SharePoint Server 2007 Service Pack 1 (32-bit editions) | Microsoft XML Core Services 5.0 (KB951597) | Information Disclosure | Important | None |
| Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (64-bit editions) | Microsoft XML Core Services 5.0 (KB951597) | Information Disclosure | Important | None |
| Microsoft Office Groove Server 2007 | Microsoft XML Core Services 5.0 (KB951597) | Information Disclosure | Important | MS07-042 |
*Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the MSDN articles, Server Core and Server Core for Windows Server 2008 R2. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Non-Affected Software
| Software |
|---|
| Microsoft XML Core Services 3.0 on 32-bit and x64-based editions of Windows Vista Service Pack 2 |
| Microsoft XML Core Services 3.0 on 32-bit, x64-based, and Itanium-based editions of Windows Server 2008 Service Pack 2 |
| Microsoft XML Core Services 6.0 on 32-bit and x64-based editions of Windows Vista Service Pack 2 |
| Microsoft XML Core Services 6.0 on 32-bit, x64-based, and Itanium-based editions of Windows Server 2008 Service Pack 2 |
| Microsoft Office 2000 Service Pack 3 |
| Microsoft Office XP Service Pack 3 |
| Microsoft Office SharePoint Portal Server 2001 Service Pack 3 |
| Microsoft Office SharePoint Portal Server 2003 Service Pack 3 |
| Microsoft Excel Viewer 2003 Service Pack 3 |
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 955218.
Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.
Does this update contain any security-related changes to functionality?
The security updates offered in this bulletin contain changes to functionality no longer allowing MSXML the ability to control transfer encoding.
In addition to the changes that are listed in the Vulnerability Information section of this bulletin, this update includes a defense-in-depth change to XMLHTTP to prevent HTTP-only cookies from being accessed through a client-side script.
Does this update contain any non-security related changes to functionality?
The updates that are offered by this security bulletin will also include additional updates that are in the current Service Pack offerings for the respective versions of MSXML.
What is Microsoft XML Core Services (MSXML)?
Microsoft XML Core Services (MSXML) allows customers who use JScript, Visual Basic Scripting Edition (VBScript), and Microsoft Visual Studio 6.0 to develop XML-based applications that provide interoperability with other applications that adhere to the XML 1.0 standard. For more information, see the MSDN site, MSXML.
What version of Microsoft XML Core Services is installed on my system?
Microsoft XML Core Services is included in additional non-operating system software from Microsoft and is also available as separate downloads. For information about the different Microsoft XML Core Services versions that are available and the products that install them, see Microsoft Knowledge Base Article 269238.
Note Depending on which versions of Microsoft XML Core Services you have installed on your system, you may be offered more than one security update from this security bulletin.
2007 Microsoft Office System installs Microsoft XML Core Services 5.0 and Microsoft XML Core Services 6.0, but the update for 2007 Microsoft Office System only contains Microsoft XML Core Services 5.0. Am I still vulnerable if I only apply the 2007 Microsoft Office System update?
Customers should apply the Microsoft XML Core Services 6.0 update when Microsoft XML Core Services 6.0 is installed on their system. Customers who have already applied the Microsoft XML Core Services 6.0 update and then later install 2007 Microsoft Office System will not need to reapply the Microsoft XML Core Services 6.0 update to remain protected.
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. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.
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. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.
Customers who require custom support for older releases 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 Microsoft Worldwide Information, select the country, 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 Windows Operating System Product Support Lifecycle FAQ.
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
| Affected Software | MSXML Memory Corruption Vulnerability - CVE-2007-0099 | MSXML DTD Cross-Domain Scripting Vulnerability - CVE-2008-4029 | MSXML Header Request Vulnerability - CVE-2008-4033 | Aggregate Severity Rating |
|---|---|---|---|---|
| Windows 2000 | ||||
| Microsoft XML Core Services 3.0 on Microsoft Windows 2000 Service Pack 4 | Critical Remote Code Execution | Important Information Disclosure | Important Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Microsoft Windows 2000 Service Pack 4 | Not applicable | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Windows XP | ||||
| Microsoft XML Core Services 3.0 on Windows XP Service Pack 2 and Windows XP Service Pack 3 | Critical Remote Code Execution | Important Information Disclosure | Important Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3 | Not applicable | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft XML Core Services 6.0 when installed on Windows XP Service Pack 2 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 6.0 on Windows XP Service Pack 3 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 3.0 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Critical Remote Code Execution | Important Information Disclosure | Important Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Not applicable | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft XML Core Services 6.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Windows Server 2003 | ||||
| Microsoft XML Core Services 3.0 on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Critical Remote Code Execution | Low Information Disclosure | Low Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Not applicable | Low Information Disclosure | Low Information Disclosure | Low |
| Microsoft XML Core Services 6.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Not applicable | Not applicable | Low Information Disclosure | Low |
| Microsoft XML Core Services 3.0 on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Critical Remote Code Execution | Low Information Disclosure | Low Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Not applicable | Low Information Disclosure | Low Information Disclosure | Low |
| Microsoft XML Core Services 6.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Not applicable | Not applicable | Low Information Disclosure | Low |
| Microsoft XML Core Services 3.0 on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Critical Remote Code Execution | Low Information Disclosure | Low Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Not applicable | Low Information Disclosure | Low Information Disclosure | Low |
| Microsoft XML Core Services 6.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Not applicable | Not applicable | Low Information Disclosure | Low |
| Windows Vista | ||||
| Microsoft XML Core Services 3.0 on Windows Vista and Windows Vista Service Pack 1 | Critical Remote Code Execution | Important Information Disclosure | Important Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | Not applicable | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft XML Core Services 6.0 on Windows Vista and Windows Vista Service Pack 1 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 3.0 on Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Critical Remote Code Execution | Important Information Disclosure | Important Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | Not applicable | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft XML Core Services 6.0 on Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Windows Server 2008 | ||||
| Microsoft XML Core Services 3.0 on Windows Server 2008 for 32-bit Systems* | Critical Remote Code Execution | Low Information Disclosure | Low Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* | Not applicable | Low Information Disclosure | Low Information Disclosure | Low |
| Microsoft XML Core Services 6.0 on Windows Server 2008 for 32-bit Systems* | Not applicable | Not applicable | Low Information Disclosure | Low |
| Microsoft XML Core Services 3.0 on Windows Server 2008 for x64-based Systems* | Critical Remote Code Execution | Low Information Disclosure | Low Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* | Not applicable | Low Information Disclosure | Low Information Disclosure | Low |
| Microsoft XML Core Services 6.0 on Windows Server 2008 for x64-based Systems* | Not applicable | Not applicable | Low Information Disclosure | Low |
| Microsoft XML Core Services 3.0 on Windows Server 2008 for Itanium-based Systems | Critical Remote Code Execution | Low Information Disclosure | Low Information Disclosure | Critical |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Not applicable | Low Information Disclosure | Low Information Disclosure | Low |
| Microsoft XML Core Services 6.0 on Windows Server 2008 for Itanium-based Systems | Not applicable | Not applicable | Low Information Disclosure | Low |
| Windows 7 | ||||
| Microsoft XML Core Services 4.0 when installed on Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | Not applicable | Important Information Disclosure | Important Information Disclosure | Important |
| Microsoft XML Core Services 4.0 when installed on Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | Not applicable | Important Information Disclosure | Important Information Disclosure | Important |
| Windows Server 2008 R2 | ||||
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1* | Not applicable | Low Information Disclosure | Low Information Disclosure | Low |
| Microsoft XML Core Services 4.0 when installed on Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | Not applicable | Low Information Disclosure | Low Information Disclosure | Low |
| Microsoft Office | ||||
| Microsoft XML Core Services 5.0 on Microsoft Office 2003 Service Pack 3 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 5.0 on Microsoft Word Viewer 2003 Service Pack 3 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 5.0 on 2007 Microsoft Office System and 2007 Microsoft Office System Service Pack 1 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 5.0 on Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 5.0 on Microsoft Expression Web and Microsoft Expression Web 2 | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 5.0 on Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (32-bit editions) | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 5.0 on Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (64-bit editions) | Not applicable | Not applicable | Important Information Disclosure | Important |
| Microsoft XML Core Services 5.0 on Microsoft Office Groove Server 2007 | Not applicable | Not applicable | Important Information Disclosure | Important |
*Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the MSDN articles, Server Core and Server Core for Windows Server 2008 R2. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
MSXML Memory Corruption Vulnerability - CVE-2007-0099
A remote code execution vulnerability exists in the way that Microsoft XML Core Services parses XML content. The vulnerability could allow remote code execution if a user browses a Web site that contains specially crafted content or opens specially crafted HTML e-mail. 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-2007-0099.
Mitigating Factors for MSXML Memory Corruption Vulnerability - CVE-2007-0099
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 could host a Web site that contains a Web page that is used to exploit this vulnerability In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. An attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
- An attacker who successfully exploited this vulnerability could gain the same user rights as the local 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.
Workarounds for MSXML Memory Corruption Vulnerability - CVE-2007-0099
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:
Restrict access to msxml3.dll For Windows XP Service Pack 2 and Windows XP Service Pack 3:
Run the following command from an elevated administrator command prompt:
cacls %windir%\system32\msxml3.dll /E /P everyone:NRestart
Impact of workaround. Web sites that use XML may no longer display or function correctly.
How to undo the workaround.
Run the following command from an elevated administrator command prompt:
cacls %windir%\system32\msxml3.dll /E /R everyoneRestart
For all supported 32-bit editions of Windows Vista and Windows Server 2008:
Run the following commands from an elevated administrator command prompt:
takeown /f %windir%\system32\msxml3.dllicacls %windir%\system32\msxml3.dll /save %TEMP%\MSXML3 _ACL.TXTicacls %windir%\system32\msxml3.dll /deny everyone:(F)Restart
Impact of workaround. Web sites that use XML may no longer display or function correctly.
How to undo the workaround.
Run the following command from an elevated administrator command prompt
icacls %windir%\system32\ /restore %TEMP%\MSXML3_ACL.TXTRestart
FAQ for MSXML Memory Corruption Vulnerability - CVE-2007-0099
What is the scope of the vulnerability?
This is a remote code execution vulnerability. 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.
What causes the vulnerability?
When XML content is parsed, MSXML may corrupt the system state in such a way that an attacker could run arbitrary code.
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 Web site that is designed to invoke MSXML through Internet Explorer. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. 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 Web site 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 removes the vulnerability by ensuring that XML content is parsed correctly.
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-2007-0099.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
MSXML DTD Cross-Domain Scripting Vulnerability - CVE-2008-4029
An information disclosure vulnerability exists in the way that Microsoft XML Core Services handles error checks for external document type definitions (DTDs). The vulnerability could allow information disclosure if a user browses a Web site that contains specially crafted content or opens specially crafted HTML e-mail. An attacker who successfully exploited this vulnerability could read data from a Web page in another domain in Internet Explorer. In all cases, however, an attacker would have no way to force users to visit these Web sites.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4029.
Mitigating Factors for MSXML DTD Cross-Domain Scripting Vulnerability - CVE-2008-4029
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 could host a Web site that contains a Web page that is used to exploit this vulnerability In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. An attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
- By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps reduce the number of successful attacks that exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail, they could still be vulnerable to this issue through the Web-based attack scenario.
- By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that have not been added to Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
Workarounds for MSXML DTD Cross-Domain Scripting Vulnerability - CVE-2008-4029
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:
Configure Internet Explorer to prompt before running Active Scripting or to 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.
Impact of Workaround: Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site 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.
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 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 Web sites 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 system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.
Set Internet and Local intranet security zone settings to “High” to prompt before running ActiveX Controls and Active Scripting in these zones
You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls. You can do this by setting your browser security to High.
To raise the browsing security level in Microsoft Internet Explorer, follow these steps:
- On the Internet Explorer Tools menu, click Internet Options.
- In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
- Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.
Note If no slider is visible, click Default Level, and then move the slider to High.
Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site 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 even with the security setting set to High.
Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls 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 ActiveX controls. If you do not want to be prompted for all these sites, use the steps outlined in the heading "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 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 Web sites 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 system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.
FAQ for MSXML DTD Cross-Domain Scripting Vulnerability - CVE-2008-4029
What is the scope of the vulnerability?
This is an information disclosure vulnerability. An attacker who successfully exploited this vulnerability could read data from a Web page in another domain in Internet Explorer.
What causes the vulnerability?
MSXML incorrectly handles external DTDs, allowing a violation of cross-domain policy.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could read data from another domain in Internet Explorer.
How could an attacker exploit the vulnerability?
An attacker could exploit the vulnerability by hosting a specially crafted Web site that is designed to invoke MSXML through Internet Explorer. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. 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 Web site for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
I am running Internet Explorer for Windows Server 2003 or Windows Server 2008. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See also Managing Internet Explorer Enhanced Security Configuration.
What does the update do?
The update removes the vulnerability by properly handling external DTDs.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
MSXML Header Request Vulnerability - CVE-2008-4033
An information disclosure vulnerability exists in the way that Microsoft XML Core Services handles transfer-encoding headers. The vulnerability could allow information disclosure if a user browses a Web site that contains specially crafted content or opens specially crafted HTML e-mail. An attacker who successfully exploited this vulnerability could read data from a Web page in another domain in Internet Explorer. In all cases, however, an attacker would have no way to force users to visit these Web sites.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4033.
Mitigating Factors for MSXML Header Request Vulnerability - CVE-2008-4033
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:
- In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability In addition, Web sites that accept or host user-provided content, or compromised Web sites and advertisement servers could contain specially crafted content that could exploit this vulnerability. An attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
- By default, all supported versions of Microsoft Outlook and Microsoft Outlook Express open HTML e-mail messages in the Restricted sites zone. The Restricted sites zone helps reduce the number of successful attacks that exploit this vulnerability by preventing Active Scripting and ActiveX controls from being used when reading HTML e-mail. However, if a user clicks on a link within an e-mail, they could still be vulnerable to this issue through the Web-based attack scenario.
- By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. This mode sets the security level for the Internet zone to High. This is a mitigating factor for Web sites that have not been added to Internet Explorer Trusted sites zone. See the FAQ subsection of this vulnerability section for more information about Internet Explorer Enhanced Security Configuration.
Workarounds for MSXML Header Request Vulnerability - CVE-2008-4033
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:
Configure Internet Explorer to prompt before running Active Scripting or to 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.
Impact of Workaround: Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site 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..
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 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 Web sites 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 system. 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.
Set Internet and Local intranet security zone settings to "High" to prompt before running ActiveX Controls and Active Scripting in these zones
You can help protect against this vulnerability by changing your settings for the Internet security zone to prompt before running ActiveX controls. You can do this by setting your browser security to High.
To raise the browsing security level in Microsoft Internet Explorer, follow these steps:
- On the Internet Explorer Tools menu, click Internet Options.
- In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
- Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.
Note If no slider is visible, click Default Level, and then move the slider to High.
Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site 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 even with the security setting set to High.
Impact of Workaround: There are side effects to prompting before running ActiveX controls. Many Web sites that are on the Internet or on an intranet use ActiveX to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX controls to provide menus, ordering forms, or even account statements. Prompting before running ActiveX controls 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 ActiveX controls. If you do not want to be prompted for all these sites, use the steps outlined in the heading, "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 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 Web sites 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 system. 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.
FAQ for MSXML Header Request Vulnerability - CVE-2008-4033
What is the scope of the vulnerability?
This is an information disclosure vulnerability. An attacker who successfully exploited this vulnerability could read data from a Web page in another domain in Internet Explorer.
What causes the vulnerability?
MSXML allows certain HTTP request fields to be set by clients, enabling session state corruption, leading to the possibility of information disclosure.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could read data from another domain in Internet Explorer.
How could an attacker exploit the vulnerability?
An attacker could exploit the vulnerability by hosting a specially crafted Web site that is designed to invoke MSXML through Internet Explorer. This can also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger request that takes users to the attacker's Web site. 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 Web site for any malicious action to occur. Therefore, any systems where Internet Explorer is used frequently, such as workstations or terminal servers, are at the most risk from this vulnerability.
I am running Internet Explorer for Windows Server 2003 or Windows Server 2008. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer on Windows Server 2003 and Windows Server 2008 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone. See also Managing Internet Explorer Enhanced Security Configuration.
What does the update do?
The update removes the vulnerability by no longer allowing clients to set certain HTTP request fields.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Update Information
Detection and Deployment Tools and Guidance
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 Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update, Windows Update, and Office 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 has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.
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 2.1 |
|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Yes |
| Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | Yes |
| Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | Yes |
| Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes |
| Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Yes |
| Windows Server 2008 for Itanium-based Systems and 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* |
| Microsoft Office 2003 Service Pack 3 | Yes |
| Microsoft Word Viewer 2003 Service Pack 3 | Yes |
| 2007 Microsoft Office System and 2007 Microsoft Office System Service Pack 1 | Yes |
| Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 | Yes |
| Microsoft Expression Web and Microsoft Expression Web 2 | Yes |
| Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (32-bit editions) | Yes |
| Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (64-bit editions) | Yes |
| Microsoft Office Groove Server 2007 | Yes |
| Microsoft XML Core Services 4.0 | Yes |
| Microsoft XML Core Services 6.0 | Yes |
*The latest MBSA supports this rerelease.
For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.
Windows Server Update Services
By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
| Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | Configuration Manager 2007 |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 | Yes | Yes | Yes | Yes |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 | Yes | Yes | Yes | Yes |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | No | No | Yes | Yes |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Yes | Yes | Yes | Yes |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | No | No | Yes | Yes |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | No | No | Yes | Yes |
| Windows Vista, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Vista x64 Edition, Windows Vista x64 Edition Service Pack 1, and Windows Vista x64 Edition Service Pack 2 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | No | No | See Note for Windows Vista and Windows Server 2008 below | Yes |
| Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 | No* | No* | No* | Yes* |
| Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 | No* | No* | No* | Yes* |
| Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 | No* | No* | No* | Yes* |
| Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 | No* | No* | No* | Yes* |
| Microsoft Office 2003 Service Pack 3 | Yes | Yes | Yes | Yes |
| Microsoft Word Viewer 2003 Service Pack 3 | Yes | Yes | Yes | Yes |
| 2007 Microsoft Office System and 2007 Microsoft Office System Service Pack 1 | No | No | Yes | Yes |
| Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 | No | No | Yes | Yes |
| Microsoft Expression Web and Microsoft Expression Web 2 | No | No | Yes | Yes |
| Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (32-bit editions) | No | No | Yes | Yes |
| Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (64-bit editions) | No | No | Yes | Yes |
| Microsoft Office Groove Server 2007 | No | No | Yes | Yes |
| Microsoft XML Core Services 4.0 | Yes | Yes | Yes | Yes |
| Microsoft XML Core Services 6.0 | Yes | Yes | Yes | Yes |
*The latest SMS supports this rerelease.
For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.
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. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
Note for Windows Vista and Windows Server 2008 Microsoft Systems Management Server 2003 with Service Pack 3 includes support for Windows Vista and Windows Server 2008 manageability.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Note for Microsoft Office SharePoint Server 2007 The detection table described above is based on single-server Microsoft Office SharePoint Server 2007 deployments. The detection tools do not detect the applicability of the update on systems configured as part of a multiple-system SharePoint server farms. For more information about deploying updates on both stand-alone and multi server configurations, see Deploy software updates for Office SharePoint Server 2007.
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 5.0.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft 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 2000 (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 may be included in a future update rollup |
|---|---|
| Deployment | |
| Installing without user intervention | For Microsoft XML Core Services 3.0 on Microsoft Windows 2000 Service Pack 4:\ Windows2000-KB955069-x86-enu /quiet |
| For Microsoft XML Core Services 4.0 when installed on Microsoft Windows 2000 Service Pack 4:\ msxml4-KB954430-enu /quiet | |
| For Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4:\ msxml6-KB954459-enu-x86 /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on Microsoft Windows 2000 Service Pack 4:\ Windows2000-KB955069-x86-enu /norestart |
| For Microsoft XML Core Services 4.0 when installed on Microsoft Windows 2000 Service Pack 4:\ msxml4-KB954430-enu /norestart | |
| For Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4:\ msxml6-KB954459-enu-x86 /norestart | |
| Update log file | For Microsoft XML Core Services 3.0 on Microsoft Windows 2000 Service Pack 4:\ KB955069.log |
| For Microsoft XML Core Services 4.0 when installed on Microsoft Windows 2000 Service Pack 4:\ msxml4-KB954430-enu.log | |
| For Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4:\ msxml6-KB954459-enu-x86.log | |
| Further information | See the subsection, 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 | Microsoft XML Core Services 3.0 on Microsoft Windows 2000 Service Pack 4:\ Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB955069$\Spuninst folder |
| Microsoft XML Core Services 4.0 when installed on Microsoft Windows 2000 Service Pack 4:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in the Removing the Update section to remove the security update. | |
| Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4:\ 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 | See Microsoft Knowledge Base Article 955218 |
| Registry Key Verification | Microsoft XML Core Services 3.0 on Microsoft Windows Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB955069\Filelist |
| Microsoft XML Core Services 4.0 when installed on Microsoft Windows 2000 Service Pack 4:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP2\Q954430 | |
| Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4:\ Note A registry key does not exist to validate the presence of this update. |
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, visit the Microsoft TechNet Web site.
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. Note Not applicable for Microsoft XML Core Services 4.0 or Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4, Windows XP Service Pack 2, Windows XP Professional x64 Edition, Windows XP Professional x64 Edition Service Pack 2, Windows Server 2003 Service Pack 1, or Windows Server 2003 Service Pack 2. |
| /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. |
| /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
Removing MSXML 4.0
This version of Microsoft XML Core Services is installed in a side-by-side mode with pervious versions of MSXML4. Follow these steps to remove the security update:
- Remove the security update by using the Add or Remove Programs tool in Control Panel.
- Delete the msxml4.dll file from the %SystemRoot%\System32 folder.
- Repair previous msxml4.dll by using the Add or Remove Programs tool in Control Panel.
Note The previous versions of the msxml4.dll and msxml4r.dll files are restored to both the %SystemRoot%\System32 folder and the side-by-side folder %SystemRoot%\WinSxS.
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 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 2 and Windows XP Service Pack 3:\ WindowsXP-KB955069-x86-enu /quiet |
| For Microsoft XML Core Services 3.0 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB955069-x64-enu /quiet | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:\ msxml4-KB954430-enu /quiet | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Service Pack 2:\ msxml6-KB954459-enu-x86 / quiet | |
| For Microsoft XML Core Services 6.0 on Windows XP Service Pack 3:\ WindowsXP-KB954459-x86-enu / quiet | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ msxml4-KB954430-enu /quiet | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ msxml6-KB954459-enu-amd64 /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on Windows XP Service Pack 2 and Windows XP Service Pack 3:\ WindowsXP-KB955069-x86-enu /norestart |
| For Microsoft XML Core Services 3.0 on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ WindowsServer2003.WindowsXP-KB955069-x64-enu /norestart | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:\ msxml4-KB954430-enu /norestart | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Service Pack 2:\ msxml6-KB954459-enu-x86 / norestart | |
| For Microsoft XML Core Services 6.0 on Windows XP Service Pack 3:\ WindowsXP-KB954459-x86-enu / norestart | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ msxml4-KB954430-enu /norestart | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ msxml6-KB954459-enu-amd64 /norestart | |
| Update log file | For Microsoft XML Core Services 3.0 on all supported editions of Windows XP:\ KB955069.log |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:\ msxml4-KB954430-enu.log | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Service Pack 2:\ msxml6-KB954459-enu-x86.log | |
| For Microsoft XML Core Services 6.0 on Windows XP Service Pack 3:\ KB954459.log | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ msxml4-KB954430-enu.log | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ msxml6-KB954459-enu-x86.log | |
| Further information | See the subsection, 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 | For Microsoft XML Core Services 3.0 on all supported editions of Windows XP:\ Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB955069$\Spuninst folder |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in the Removing the Update section to remove the security update. | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Service Pack 2 and on Windows XP Service Pack 3:\ 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 for Windows XP Service Pack 2. | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in the Removing the Update section to remove the security update. | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition 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 for Windows XP Professional x64 Edition Service Pack 2. | |
| File Information | See Microsoft Knowledge Base Article 955218 |
| 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\KB955069\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\KB955069\Filelist | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Service Pack 2 and Windows XP Service Pack 3:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP2\Q954430 | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Service Pack 2:\ Note A registry key does not exist to validate the presence of this update\ \ For Microsoft XML Core Services 6.0 when installed on Windows XP Service Pack 3:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB954459\Filelist | |
| For Microsoft XML Core Services 4.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\MSXML4SP2\Q954430 | |
| For Microsoft XML Core Services 6.0 when installed on Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2:\ Note A registry key does not exist to validate the presence of this update |
Note For supported versions of Windows XP Professional x64 Edition, this security update is the same as supported versions of the Windows Server 2003 x64 Edition security update.
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, visit the Microsoft TechNet Web site.
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. Note Not applicable for Microsoft XML Core Services 4.0 or Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4, Windows XP Service Pack 2, Windows XP Professional x64 Edition, Windows XP Professional x64 Edition Service Pack 2, Windows Server 2003 Service Pack 1, or Windows Server 2003 Service Pack 2. |
| /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
Removing MSXML 4.0
This version of Microsoft XML Core Services is installed in a side-by-side mode with pervious versions of MSXML4. Follow these steps to remove the security update:
- Remove the security update by using the Add or Remove Programs tool in Control Panel.
- Delete the Msxml4.dll file from the %SystemRoot%\System32 folder.
- Repair previous Msxml4.dll by using the Add or Remove Programs tool in Control Panel.
Note The previous versions of the Msxml4.dll and Msxml4r.dll files are restored to both the %SystemRoot%\System32 folder and the side-by-side folder %SystemRoot%\WinSxS.
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-KB955069-x86-enu /quiet |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Server 2003:\ WindowsServer2003.WindowsXP-KB955069-x64-enu /quiet | |
| For Microsoft XML Core Services 3.0 on all supported Itanium-based editions of Windows Server 2003:\ WindowsServer2003-KB955069-ia64-enu /quiet | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:\ msxml4-KB954430-enu /quiet | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:\ msxml6-KB954459-enu-x86 /quiet | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:\ msxml4-KB954430-enu /quiet | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:\ msxml6-KB954459-enu-amd64 /quiet | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ msxml4-KB954430-enu /quiet | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ msxml6-KB954459-enu-ia64 /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on all supported 32-bit editions of Windows Server 2003:\ Windowsserver2003-kb955069-x86-enu /norestart |
| For Microsoft XML Core Services 3.0 on all supported x64-based editions of Windows Server 2003:\ WindowsServer2003.WindowsXP-KB955069-x64-enu /norestart | |
| For Microsoft XML Core Services 3.0 on all supported Itanium-based editions of Windows Server 2003:\ WindowsServer2003-KB955069-ia64-enu /norestart | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:\ msxml4-KB954430-enu /norestart | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:\ msxml6-KB954459-enu-x86 /norestart | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:\ msxml4-KB954430-enu /norestart | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:\ msxml6-KB954459-enu-amd64 /norestart | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ msxml4-KB954430-enu /norestart | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ msxml6-KB954459-enu-ia64 /norestart | |
| Update log file | For Microsoft XML Core Services 3.0 on all supported editions of Windows Server 2003:\ KB955069.log |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:msxml4-KB954430-enu.log | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:\ msxml6-KB954459-enu-x86.log | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:msxml4-KB954430-enu.log | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:\ msxml6-KB954459-enu-amd64.log | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ Not applicable | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ Not applicable | |
| Further information | See the subsection, 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 | 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 tool in Control Panel or the Spuninst.exe utility located in the %Windir%$NTUninstallKB955069$\Spuninst folder |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in the Removing the Update section to remove the security update. | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 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. | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in the Removing the Update section to remove the security update. | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition 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. | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in the Removing the Update section to remove the security update. | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ 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 | See Microsoft Knowledge Base Article 955218 |
| 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\KB955069\Filelist |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP2\Q954430 | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2:\ Note A registry key does not exist to validate the presence of this update | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\MSXML4SP2\Q954430 | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2:\ Note A registry key does not exist to validate the presence of this update | |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\MSXML4SP2\Q954430 | |
| For Microsoft XML Core Services 6.0 when installed on Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems:\ Note A registry key does not exist to validate the presence of this update |
Deployment Information
Installing the Update
When you install this security update, the installer checks to see if 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, visit the Microsoft TechNet Web site.
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. Note Not applicable for Microsoft XML Core Services 4.0 or Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4, Windows XP Service Pack 2, Windows XP Professional x64 Edition, Windows XP Professional x64 Edition Service Pack 2, Windows Server 2003 Service Pack 1, or Windows Server 2003 Service Pack 2. |
| /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
Removing MSXML 4.0
This version of Microsoft XML Core Services is installed in a side-by-side mode with pervious versions of MSXML4. Follow these steps to remove the security update:
- Remove the security update by using the Add or Remove Programs tool in Control Panel.
- Delete the Msxml4.dll file from the %SystemRoot%\System32 folder.
- Repair previous Msxml4.dll by using the Add or Remove Programs tool in Control Panel.
Note The previous versions of the Msxml4.dll and Msxml4r.dll files are restored to both the %SystemRoot%\System32 folder and the side-by-side folder %SystemRoot%\WinSxS.
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 Windows Vista for 32-bit Systems and Windows Vista for 32-bit Systems Service Pack 1:\ Windows6.0-KB955069-x86 /quiet\ \ For Microsoft XML Core Services 3.0 on Windows Vista for x64-based Systems and Windows Vista for x64-based Systems Service Pack 1:\ Windows6.0-KB955069-x64 /quiet |
| For Microsoft XML Core Services 4.0 when installed on Windows Vista for 32-bit Systems, Windows Vista for 32-bit Systems Service Pack 1, and Windows Vista for 32-bit Systems Service Pack 2:\ msxml4-KB954430-enu /quiet\ \ For Microsoft XML Core Services 4.0 when installed on Windows Vista for x64-based Systems, Windows Vista for x64-based Systems Service Pack 1, and Windows Vista for x64-based Systems Service Pack 2:\ msxml4-KB954430-enu /quiet | |
| For Microsoft XML Core Services 6.0 Windows Vista for 32-bit Systems and Windows Vista for 32-bit Systems Service Pack 1:\ Windows6.0-KB954459-x86 /quiet\ \ For Microsoft XML Core Services 6.0 on Windows Vista for x64-based Systems and Windows Vista for x64-based Systems Service Pack 1:\ Windows6.0-KB954459-x64 /quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on Windows Vista for 32-bit Systems and Windows Vista for 32-bit Systems Service Pack 1:\ Windows6.0-KB955069-x86 /quiet /norestart\ \ For Microsoft XML Core Services 3.0 on Windows Vista for x64-based Systems and Windows Vista for x64-based Systems Service Pack 1:\ Windows6.0-KB955069-x64 /quiet /norestart |
| For Microsoft XML Core Services 4.0 when installed on Windows Vista for 32-bit Systems, Windows Vista for 32-bit Systems Service Pack 1, and Windows Vista for 32-bit Systems Service Pack 2:\ msxml4-KB954430-enu /norestart\ \ For Microsoft XML Core Services 4.0 when installed on Windows Vista for x64-based Systems, Windows Vista for x64-based Systems Service Pack 1, and Windows Vista for x64-based Systems Service Pack 2:\ msxml4-KB954430-enu /norestart | |
| For Microsoft XML Core Services 6.0 on Windows Vista for 32-bit Systems and Windows Vista for 32-bit Systems Service Pack 1:\ Windows6.0-KB954459-x86 /quiet /norestart\ \ For Microsoft XML Core Services 6.0 on Windows Vista for x64-based Systems and Windows Vista for x64-based Systems Service Pack 1:\ Windows6.0-KB954459-x64 /quiet /norestart | |
| Update log file | For Microsoft XML Core Services 3.0 on all supported 32-bit and x64-based editions of Windows Vista:\ Not applicable |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit and x64-based editions of Windows Vista:\ msxml4-KB954430-enu.log | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit and x64-based editions of Windows Vista:\ Not applicable | |
| Further information | See the subsection, 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 | For Microsoft XML Core Services 3.0 and Microsoft XML Core Services 6.0 on all supported 32-bit and 64-based 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 32-bit and 64-based 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 the Removing the Update section to remove the security update. |
| File Information | See Microsoft Knowledge Base Article 955218 |
| Registry Key Verification | For Microsoft XML Core Services 3.0 on all supported 32-bit and x64-based editions of Windows Vista: \ Note A registry key does not exist to validate the presence of this update. |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows Vista: \ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP2\Q954430\ \ For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Vista: \ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\MSXML4SP2\Q954430 | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit and x64-based editions of Windows Vista: \ Note A registry key does not exist to validate the presence of this update. |
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.
Removing the Update
Removing MSXML 4.0
This version of Microsoft XML Core Services is installed in a side-by-side mode with pervious versions of MSXML4. Follow these steps to remove the security update:
- Remove the security update by using the Add or Remove Programs tool in Control Panel.
- Delete the Msxml4.dll file from the %SystemRoot%\System32 folder.
- Repair previous Msxml4.dll by using the Add or Remove Programs tool in Control Panel.
Note The previous versions of the Msxml4.dll and Msxml4r.dll files are restored to both the %SystemRoot%\System32 folder and the side-by-side folder %SystemRoot%\WinSxS.
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 Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on 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 may also click on 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 Windows Server 2008 for 32-bit Systems:\ Windows6.0-KB955069-x86 /quiet\ \ For Microsoft XML Core Services 3.0 on Windows Server 2008 for x64-based Systems:\ Windows6.0-KB955069-x64 /quiet\ \ For Microsoft XML Core Services 3.0 on Windows Server 2008 for Itanium-based Systems:\ Windows6.0-KB955069-ia64 /quiet |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2:\ msxml4-KB954430-enu /quiet\ \ For Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2:\ msxml4-KB954430-enu /quiet\ \ For Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2:\ msxml4-KB954430-enu / quiet | |
| For Microsoft XML Core Services 6.0 on Windows Server 2008 for 32-bit Systems:\ Windows6.0-KB954459-x86 /quiet\ \ For Microsoft XML Core Services 6.0 on Windows Server 2008 for x64-based Systems:\ Windows6.0-KB954459-x64 /quiet\ \ For Microsoft XML Core Services 6.0 on Windows Server 2008 for Itanium-based Systems:\ Windows6.0-KB954459-ia64 / quiet | |
| Installing without restarting | For Microsoft XML Core Services 3.0 on Windows Server 2008 for 32-bit Systems:\ Windows6.0-KB955069-x86 /quiet /norestart\ \ For Microsoft XML Core Services 3.0 on Windows Server 2008 for x64-based Systems:\ Windows6.0-KB955069-x64 /quiet /norestart\ \ For Microsoft XML Core Services 3.0 on Windows Server 2008 for Itanium-based Systems:\ Windows6.0-KB955069-ia64 /quiet /norestart |
| For Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2:\ msxml4-KB954430-enu /norestart\ \ For Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2:\ msxml4-KB954430-enu /norestart\ \ For Microsoft XML Core Services 4.0 when installed on Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2:\ msxml4-KB954430-enu / norestart | |
| For Microsoft XML Core Services 6.0 on Windows Server 2008 for 32-bit Systems:\ Windows6.0-KB954459-x86 /quiet /norestart\ \ For Microsoft XML Core Services 6.0 on Windows Server 2008 for x64-based Systems:\ Windows6.0-KB954459-x64 /quiet /norestart\ \ For Microsoft XML Core Services 6.0 on Windows Server 2008 for Itanium-based Systems:\ Windows6.0-KB954459-ia64 / quiet /norestart | |
| Update log file | For Microsoft XML Core Services 3.0 on all supported 32-bit, x64-based, and Itanium-based editions of Windows Server 2008:\ Not applicable |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit, x64-based, and Itanium-based editions of Windows Server 2008:\ msxml4-KB954430-enu.log | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit, x64-based, and Itanium-based 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 for 32-bit, x64-based, and Itanium-based Systems:\ 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 on all supported editions of Windows Server 2008 for 32-bit, x64-based, and Itanium-based Systems:\ This version of Microsoft XML Core Services is installed in a side-by-side mode with previous versions of MSXML4. Follow the steps in the Removing the Update section to remove the security update. |
| File Information | See Microsoft Knowledge Base Article 955218 |
| Registry Key Verification | For Microsoft XML Core Services 3.0 on all supported 32-bit, x64-based, and Itanium-based editions of Windows Server 2008:\ Note A registry key does not exist to validate the presence of this update. |
| For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows Server 2008: \ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\MSXML4SP2\Q954430\ \ For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Server 2008: \ HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\MSXML4SP2\Q954430 | |
| For Microsoft XML Core Services 6.0 on all supported 32-bit, x64-based, and Itanium-based editions of Windows Server 2008:\ Note A registry key does not exist to validate the presence of this update. |
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.
Removing the Update
Removing MSXML 4.0
This version of Microsoft XML Core Services is installed in a side-by-side mode with pervious versions of MSXML4. Follow these steps to remove the security update:
- Remove the security update by using the Add or Remove Programs tool in Control Panel.
- Delete the Msxml4.dll file from the %SystemRoot%\System32 folder.
- Repair previous Msxml4.dll by using the Add or Remove Programs tool in Control Panel.
Note The previous versions of the Msxml4.dll and Msxml4r.dll files are restored to both the %SystemRoot%\System32 folder and the side-by-side folder %SystemRoot%\WinSxS.
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 Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on 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 may also click on 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 4.0 when installed on all supported 32-bit editions of Windows 7 and Windows 7 Service Pack 1:\ msxml4-KB954430-enu /quiet\ \ For Microsoft XML Core Services 4.0 when installed on all x64-based editions of Windows 7 and Windows 7 Service Pack 1:\ msxml4-KB954430-enu /quiet |
| Installing without restarting | For Microsoft XML Core Services 4.0 when installed on all supported 32-bit editions of Windows 7 and Windows 7 Service Pack 1:\ msxml4-KB954430-enu /norestart\ \ For Microsoft XML Core Services 4.0 when installed on all x64-based editions of Windows 7 and Windows 7 Service Pack 1:\ msxml4-KB954430-enu /norestart |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update. |
| HotPatching | Not applicable. |
| Removal Information | 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. |
| File Information | See Microsoft Knowledge Base Article 954430 |
| Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
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 Start Search.
- When the file appears under Programs, right-click on the file name and click Properties.
- Under the General tab, compare the file size with the file information tables provided in the bulletin KB article.
- You may also click on 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 may also click on 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 4.0 when installed on all supported x64-based editions of Windows Server 2008 R2 and Windows Server 2008 R2 Service Pack 1:\ msxml4-KB954430-enu /quiet |
| For Microsoft XML Core Services 4.0 when installed on all supported Itanium-based editions of Windows Server 2008 R2 and Windows Server 2008 R2 Service Pack 1:\ msxml4-KB954430-enu /quiet | |
| Installing without restarting | For Microsoft XML Core Services 4.0 when installed on all supported x64-based editions of Windows Server 2008 R2 and Windows Server 2008 R2 Service Pack 1:\ msxml4-KB954430-enu /quiet /norestart |
| For Microsoft XML Core Services 4.0 when installed on all supported Itanium-based editions of Windows Server 2008 R2 and Windows Server 2008 R2 Service Pack 1:\ msxml4-KB954430-enu /quiet /norestart | |
| Further information | See the subsection, Detection and Deployment Tools and Guidance |
| Restart Requirement | |
| Restart required? | Yes, you must restart your system after you apply this security update. |
| Hotpatching | Not applicable. |
| Removal Information | 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. |
| Registry Key Verification | Note A registry key does not exist to validate the presence of this update. |
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 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.
Office 2003 and Word Viewer 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 | Office2003-KB951535-FullFile-enu /q:a |
| Installing without restarting | Office2003-KB951535-FullFile-enu /r:n |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the subsection, **Detection and Deployment Tools and Guidance.**For features you can selectively install, see the Office Features subsection in this section. |
| Restart Requirement | |
| Restart required | This update does not require a restart. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool 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 tool 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 955218 |
| Registry Key Verification | Not applicable |
Office Features for Administrative Installations
Server administrators who use a Windows Installer Administrative Installation must update the server location. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
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 |
| WORDVIEW | WORDVIEWFiles |
| 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 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 Web sites:
- 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 Windows 2000
- Windows Installer 2.0 Redistributable for 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.
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 versions and 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 version of the operating system or programs installed, 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.
2007 Microsoft Office System; Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats; and Microsoft Expression Web (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 | Office2007-KB951550-FullFile-x86-glb /passive |
| Installing without restarting | Office2007-KB951550-FullFile-x86-glb /norestart |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the subsection, **Detection and Deployment Tools and Guidance.**For features you can selectively install, see the Office Features subsection in this section. |
| Restart Requirement | |
| Restart required | This update does not require a restart. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 955218 |
| 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 be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 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. |
| /quiet /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 tool in Control Panel.
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 “Microsoft baseline Security Analyzer” heading under the section, Microsoft Detection and Deployment Tools and Guidance.
File Version Verification
Note Because there are several versions and 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.
Microsoft Office SharePoint Server 2007 and Microsoft Office Groove Server 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 | Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (32-bit editions):\ Office2007-KB951597-FullFile-x86-glb /passive |
| Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (64-bit editions) and Microsoft Office Groove Server 2007:\ Office2007-KB951597-FullFile-x64-glb /passive | |
| Installing without restarting | Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (32-bit editions):\ Office2007-KB951597-FullFile-x86-glb /norestart |
| For Microsoft Office SharePoint Server 2007 and Microsoft Office SharePoint Server 2007 Service Pack 1 (64-bit editions) and Microsoft Office Groove Server 2007:\ Office2007-KB951597-FullFile-x64-glb /norestart | |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the subsection, **Detection and Deployment Tools and Guidance.**For features you can selectively install, see the Office Features subsection in this section. |
| Restart Requirement | |
| Restart required | This update does not require a restart. |
| Hotpatching | Not applicable |
| Removal Information | This update can not be removed. |
| File Information | See Microsoft Knowledge Base Article 955218 |
| 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.
Note Installation of this update does not require or cause a database upgrade.
This security update requires that Windows Installer 3.1 or later be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
- 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 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.
| 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
This update can not be removed.
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 “Microsoft baseline Security Analyzer” heading under the section, Microsoft Detection and Deployment Tools and Guidance.
File Version Verification
Note Because there are several versions and 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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Gregory Fleischer for reporting the MSXML DTD Cross-Domain Scripting Vulnerability (CVE-2008-4029)
- Stefano Di Paola of Minded Security for reporting the MSXML Header Request Vulnerability (CVE-2008-4033)
- Robert Hansen of SecTheory for reporting the additional HTTP-only defense-in-depth issue
Support
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
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 (November 11, 2008): Bulletin published.
- V1.1 (December 10, 2008): Removed the kill bit workaround from Workarounds for MSXML DTD Cross-Domain Scripting Vulnerability - CVE-2008-4029. Also added a note to the Supported Security Update Installation Switches tables clarifying that the /overwriteoem installation switch is not applicable for Microsoft XML Core Services 4.0 or Microsoft XML Core Services 6.0 when installed on Microsoft Windows 2000 Service Pack 4, Windows XP Service Pack 2, Windows XP Professional x64 Edition, Windows XP Professional x64 Edition Service Pack 2, Windows Server 2003 Service Pack 1, or Windows Server 2003 Service Pack 2.
- V1.2 (December 17, 2008): Added log file entries in the Security Update Deployment section Reference table for Microsoft XML Core Services 6.0 when installed on Windows Server 2003 Service Pack 1, Windows Server 2003 Service Pack 2, Windows Server 2003 x64 Edition, and Windows Server 2003 x64 Edition Service Pack 2.
- V2.0 (April 29, 2009): Added Microsoft XML Core Services 4.0 (KB954430) on 32-bit and x64-based editions of Windows Vista Service Pack 2 and on 32-bit, x64-based, and Itanium-based editions of Windows Server 2008 Service Pack 2 as affected software. Also added as non-affected software: Microsoft XML Core Services 3.0 and Microsoft XML Core Services 6.0 on 32-bit and x64-based editions of Windows Vista Service Pack 2 and on 32-bit, x64-based, and Itanium-based editions of Windows Server 2008 Service Pack 2. This is a detection change only; there were no changes to the binaries. Customers who have already successfully installed KB954430 do not need to reinstall.
- V3.0 (October 13, 2009): Added Microsoft XML Core Services 4.0 (KB954430) when installed on 32-bit and x64-based editions of Windows 7 and on x64-based and Itanium-based editions of Windows Server 2008 R2 as affected software. This is a detection change only; there were no changes to the binaries. Customers who have already successfully installed KB954430 do not need to reinstall.
- V4.0 (July 12, 2011): Added Microsoft XML Core Services 4.0 (KB954430) when installed on 32-bit and x64-based editions of Windows 7 Service Pack 1 and on x64-based and Itanium-based editions of Windows Server 2008 R2 Service Pack 1 as affected software. This is a detection change only; there were no changes to the binaries. The latest MBSA and SMS support this rerelease. Customers who have already successfully installed KB954430 do not need to reinstall.
Built at 2014-04-18T13:49:36Z-07:00