Microsoft Security Bulletin MS09-010 - Critical
Vulnerabilities in WordPad and Office Text Converters Could Allow Remote Code Execution (960477)
Published: | Updated:
Version: 1.3
General Information
Executive Summary
This security update resolves two publicly disclosed vulnerabilities and two privately reported vulnerabilities in Microsoft WordPad and Microsoft Office text converters. The vulnerabilities could allow remote code execution if a specially crafted file is opened in WordPad or Microsoft Office Word. Do not open Microsoft Office, RTF, Write, or WordPerfect files from untrusted sources using affected versions of WordPad or Microsoft Office Word.
This security update is rated Critical for supported editions of Microsoft Office Word 2000. This security update is also rated Important for supported editions of Microsoft Office Word 2002; Microsoft Office Converter Pack; and WordPad on all supported editions of Microsoft Windows 2000, Windows XP, and Windows Server 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.
This security update addresses the vulnerabilities by modifying the way that Microsoft Office Word and Office text converters handle opening specially crafted Word 6.0, Windows Write, and WordPerfect documents. This security update also addresses the vulnerabilities by implementing fixes to WordPad and by preventing WordPad on affected platforms from opening Word 6.0 and Windows Write files. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
This security update also addresses the vulnerability first described in Microsoft Security Advisory 960906.
Recommendation. Microsoft recommends that customers apply the update immediately.
Known Issues. Microsoft Knowledge Base Article 960477 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
Windows Operating System and Components
| Operating System | Component | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|---|
| Microsoft Windows 2000 Service Pack 4 (KB923561) | Not applicable | Remote Code Execution | Important | None |
| Windows XP Service Pack 2 and Windows XP Service Pack 3 (KB923561) | Not applicable | Remote Code Execution | Important | None |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 (KB923561) | Not applicable | Remote Code Execution | Important | None |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 (KB923561) | Not applicable | Remote Code Execution | Important | None |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 (KB923561) | Not applicable | Remote Code Execution | Important | None |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems (KB923561) | Not applicable | Remote Code Execution | Important | None |
Microsoft Office
| Office Suite and Other Software | Component | Maximum Security Impact | Aggregate Severity Rating | Bulletins Replaced by this Update |
|---|---|---|---|---|
| Microsoft Office Suites and Components | ||||
| Microsoft Office 2000 Service Pack 3 | Microsoft Office Word 2000 Service Pack 3 (KB921606) | Remote Code Execution | Critical | MS04-027 |
| Microsoft Office XP Service Pack 3 | Microsoft Office Word 2002 Service Pack 3 (KB933399) | Remote Code Execution | Important | MS04-027 |
| Other Office Software | ||||
| Microsoft Office Converter Pack (KB960476) | Not applicable | Remote Code Execution | Important | MS08-044 |
Non-Affected Software
| Windows Operating System |
|---|
| Windows Vista and Windows Vista Service Pack 1 |
| Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 |
| Windows Server 2008 for 32-bit Systems |
| Windows Server 2008 for x64-based Systems |
| Windows Server 2008 for Itanium-based Systems |
| Office and Other Software |
| Microsoft Office Word 2003 Service Pack 3 |
| Microsoft Office Word 2007 Service Pack 1 |
| Microsoft Office Word Viewer 2003 Service Pack 3 |
| Microsoft Office Word Viewer |
| Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats |
| Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 |
| Microsoft Office 2004 for Mac |
| Microsoft Office 2008 for Mac |
| Open XML File Format Converter for Mac |
| Microsoft Works 8.0 |
| Microsoft Works 8.5 |
| Microsoft Works 9.0 |
| Microsoft Works Suite 2006 |
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin revised on May 20, 2009?
This bulletin was revised to communicate that the More information about this security update sections in the associated Microsoft Knowledge Base Article 921606 and Microsoft Knowledge Base Article 933399 have been updated. The updated information is to clarify the expected installation behavior for the Html32.cnv, Mswrd832.cnv, and Msconv97.dll files provided in the Microsoft Office Word 2000 Service Pack 3 (KB921606) and Microsoft Office Word 2002 Service Pack 3 (KB933399) update packages.
Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 960477.
What are the known issues that customers may experience when installing this security update?
Microsoft Knowledge Base Article 960477 documents the currently known issues that customers may experience when they install this security update. The article also documents recommended solutions for these issues.
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?
Yes, in addition to implementing solutions for the security vulnerabilities, this security update also addresses the vulnerabilities by preventing WordPad on affected platforms from opening Word 6.0 and Write files. When WordPad attempts to open a Word 6.0 or Write file, the file will not open and a dialog box will be displayed. For more information, see Microsoft Knowledge Base Article 960477.
Does this update contain any additional changes to the converters?
In addition to addressing the vulnerabilities described in this bulletin, this update also replaces RTF, HTML and Word 97 text converters used by WordPad and Microsoft Office. These text converters are being replaced to resolve additional issues identified during the investigation of the vulnerabilities described in this security bulletin.
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
The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the April bulletin summary. For more information, see Microsoft Exploitability Index.
| Affected Software | WordPad and Office Text Converter Memory Corruption Vulnerability - CVE-2009-0087 | WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2008-4841 | Word 2000 WordPerfect 6.x Converter Stack Corruption Vulnerability - CVE-2009-0088 | WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2009-0235 | Aggregate Severity Rating |
|---|---|---|---|---|---|
| Operating System and Components | |||||
| Microsoft Windows 2000 Service Pack 4 | Important Remote Code Execution | Important Remote Code Execution | Not applicable | Important Remote Code Execution | Important |
| Windows XP Service Pack 2 | Moderate Remote Code Execution | Important Remote Code Execution | Not applicable | Important Remote Code Execution | Important |
| Windows XP Service Pack 3 | Moderate Remote Code Execution | Not applicable | Not applicable | Important Remote Code Execution | Important |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 | Moderate Remote Code Execution | Important Remote Code Execution | Not applicable | Important Remote Code Execution | Important |
| Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 | Moderate Remote Code Execution | Important Remote Code Execution | Not applicable | Important Remote Code Execution | Important |
| Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 | Moderate Remote Code Execution | Important Remote Code Execution | Not applicable | Important Remote Code Execution | Important |
| Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium-based Systems | Moderate Remote Code Execution | Important Remote Code Execution | Not applicable | Important Remote Code Execution | Important |
| Office Software and Components | |||||
| Microsoft Office Word 2000 Service Pack 3 | Critical Remote Code Execution | Not applicable | Critical Remote Code Execution | Not applicable | Critical |
| Microsoft Office Word 2002 Service Pack 3 | Important Remote Code Execution | Not applicable | Not applicable | Not applicable | Important |
| Microsoft Office Converter Pack | Not applicable | Not applicable | Important Remote Code Execution | Not applicable | Important |
WordPad and Office Text Converter Memory Corruption Vulnerability - CVE-2009-0087
A remote code execution vulnerability exists in the way that text converters in WordPad and Microsoft Office process memory when a user opens a specially crafted Word 6 file that includes malformed data.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0087.
Mitigating Factors for WordPad and Office Text Converter Memory Corruption Vulnerability - CVE-2009-0087
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
- The vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
- An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.
- All supported editions of Windows XP and Windows Server 2003 are at a reduced risk to this vulnerability because the affected component is disabled by default. These operating systems are only vulnerable if an administrator has manually enabled the affected component. All supported editions of Windows Vista and Windows Server 2008 do not contain the affected component and are also unaffected.
Microsoft Windows 2000 Service Pack 4 systems are more at risk because the converter is still active in a default installation. However, on Microsoft Windows 2000 Service Pack 4 systems that have applied the MS04-041 update, the Word for Windows 6.0 converter will be disabled by default. - Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancelbefore opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and later editions of Office.
Workarounds for WordPad and Office Text Converter Memory Corruption Vulnerability - CVE-2009-0087
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:
- Do not open or save Microsoft Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources with affected versions of WordPad or Microsoft Office.
Do not open Office, RTF or Write files from untrusted sources using any software listed as affected in this bulletin on systems that are not updated with the security updates that accompany this bulletin. This vulnerability could be exploited when a user opens a specially crafted file.
This includes files that have .wri, .rtf, and .doc file associations. WordPad and Office could also be used to manually open documents. This includes all files that have .wri, .rtf, and .doc file extensions as well files with other extensions. Be aware that WordPad could also be used to open specially crafted documents regardless of the file name extension.
- Disable the Word 6 converter by restricting access
An administrator can apply an access control list to affected converters to ensure that the converter is no longer loaded by WordPad and Office. This effectively prevents exploitation of the issue using this attack vector.
Warning Undo this workaround before installing this security update.
In order to apply the access list, run the following commands from the command prompt. Note that some of these may result in an error message, this is expected.
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd6.wpc" /E /P everyone:N
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\mswrd632.wpc" /E /P everyone:N
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\mswrd632.cnv" /E /P everyone:N
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\mswrd632.wpc" /E /P everyone:N
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\mswrd632.cnv" /E /P everyone:N
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd664.wpc" /E /P everyone:N
echo y| cacls "%ProgramFiles(x86)%\Windows NT\Accessories\mswrd6.wpc" /E /P everyone:NImpact of workaround. Upon implementing the workaround, the user will no longer be able to convert Word 6 documents to WordPad RTF or Word 2003 documents. Microsoft Office Word will return an error saying, "The file appears to be corrupted."
How to undo the workaround.
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd6.wpc" /E /R everyone
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\mswrd632.wpc" /E /R everyone
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\mswrd632.cnv" /E /R everyone
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\mswrd632.wpc" /E /R everyone
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\mswrd632.cnv" /E /R everyone
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd664.wpc" /E /R everyone
echo y| cacls "%ProgramFiles(x86)%\Windows NT\Accessories\mswrd6.wpc" /E /R everyone
FAQ for WordPad and Office Text Converter Memory Corruption Vulnerability - CVE-2009-0087
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 remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
A vulnerability exists in WordPad and Office text converters that allows an attacker to execute remote code when a user opens a specially crafted attacker-supplied document. The specific vulnerability exists in the way that the Word 6 converter parses the specially crafted document.
What are WordPad Text Converters and Office Text Converters?
WordPad is a default component of Microsoft Windows operating systems. Text converters in WordPad allow users who do not have Microsoft Office Word installed to open documents in Microsoft Windows Write (.wri) and Microsoft Office Word 6.0, Microsoft Office Word 97, Microsoft Office Word 2000, and Microsoft Office Word 2002 (.doc) file formats. These text converters also allow users to save documents in the Word 6.0 file format.
Text converters are also a default component of Microsoft Office that allow users to open and save as older Office file formats, including the Word 6.0 file format.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code 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?
This vulnerability requires that a user open a specially crafted document with an affected version of WordPad or Microsoft Office Word.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted file to the user and by convincing the user to open the file using either WordPad or Microsoft Office.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a document that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site.
How are supported editions of Microsoft Windows 2000, Windows XP, and Windows Server 2003 affected by this vulnerability?
The Word for Windows 6.0 converter is not enabled by default on systems running supported editions of Windows XP and Windows Server 2003. However, if the Word for Windows 6.0 converter has been manually enabled, such as per the instructions in Microsoft Knowledge Base Article 870883, the system will be at risk of this vulnerability. See the workaround, Disable the Word 6 converter by restricting access, for details on disabling the Word for Windows 6.0 converter if it has been enabled.
On Microsoft Windows 2000 Service Pack 4 systems, the bulletin is rated with severity of Important because the converter is still active in a default installation. However, on Microsoft Windows 2000 Service Pack 4 systems that have applied the MS04-041 update, the Word for Windows 6.0 converter will be disabled by default.
What systems are primarily at risk from the vulnerability?
All systems with WordPad or Microsoft Office Word where Word documents are opened from untrusted sources are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
This update removes the vulnerability by disabling the WordPad Word 6 and Windows Write text converters.
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-2009-0087.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Exploit code is publicly available of a variant of this issue that may cause a Denial of Service condition in WordPad. Microsoft is not currently aware of publicly available exploit code of this issue that leads to remote code execution.
Does applying this security update help protect customers from the code, published publicly, that attempts to exploit this vulnerability?
Yes. This security update addresses the vulnerability that is currently being exploited.
WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2008-4841
A remote code execution vulnerability exists in the way that Microsoft WordPad processes memory when parsing a specially crafted Word 97 document. The vulnerability could allow remote code execution if a user opens a specially crafted Word file that includes a malformed list structure.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2008-4841.
Mitigating Factors for WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2008-4841
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
- In a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
- The vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
- An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.
- A website attempting to exploit the vulnerability would cause a dialog box to appear. The user would be prompted to decide if they wanted to open the file or not, unless the user had previously unchecked the option "Always ask before opening this type of file."
Workarounds for WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2008-4841
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:
- Do not open or save Microsoft Office, RTF or Write files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.
This includes all files that have .wri, .rtf, and .doc file extensions as well files with other extensions. Be aware that WordPad could also be used to open specially crafted documents regardless of the file name extension.
- Disable the Word 6 converter by restricting access to mswrd8.wpc
An administrator can apply an access control list to the affected converter to ensure it is no longer loaded by WordPad. This effectively prevents exploitation of the issue.
Warning Undo this workaround before installing this security update.
In order to apply the access control list, run the following commands from the command prompt. Note that some of these commands may result in an error message. This error message is expected.
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\mswrd832.cnv" /E /P everyone:N
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\mswrd832.cnv" /E /P everyone:N
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd8.wpc" /E /P everyone:N
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd864.wpc" /E /P everyone:N
echo y| cacls "%ProgramFiles(x86)%\Windows NT\Accessories\mswrd8.wpc" /E /P everyone:NImpact of workaround. WordPad will no longer load Word 97 (Word 6.0) documents.
How to undo the workaround.
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\mswrd832.cnv" /E /R everyone
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\mswrd832.cnv" /E /R everyone
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd8.wpc" /E /R everyone
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd864.wpc" /E /R everyone
echo y| cacls "%ProgramFiles(x86)%\Windows NT\Accessories\mswrd8.wpc" /E /R everyone
FAQ for WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2008-4841
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 remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
This vulnerability requires that a user open a specially crafted Word 97 document with an affected version of WordPad.
What are WordPad Text Converters?
WordPad is a default component of Microsoft Windows operating systems. Text converters in WordPad allow users who do not have Microsoft Office Word installed to open documents in Microsoft Windows Write (.wri) and Microsoft Office Word 6.0, Microsoft Office Word 97, Microsoft Office Word 2000, and Microsoft Office Word 2002 (.doc) file formats. These text converters also allow users to save documents in the Word 6.0 file format.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code 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?
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Word 97 file to the user and by convincing the user to open the file.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word 97 document that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's web site.
What systems are primarily at risk from the vulnerability?
All systems where WordPad is used to open Word documents from untrusted sources, such as workstations or terminal servers, are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
This update removes the vulnerability by changing the way that the WordPad Text Converters handle opening specially crafted Word 97 files.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability had been publicly disclosed when this security bulletin was originally issued. It has been assigned the Common Vulnerability and Exposure number CVE-2008-4841. This vulnerability was first described in Microsoft Security Advisory 960906.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. Microsoft is aware of limited, targeted attacks attempting to exploit the vulnerability.
Word 2000 WordPerfect 6.x Converter Stack Corruption Vulnerability - CVE-2009-0088
A remote code execution vulnerability exists in the way that the WordPerfect 6.x converter that is included with Microsoft Office Word 2000 processes memory when parsing a specially crafted WordPerfect document.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0088.
Mitigating Factors for Word 2000 WordPerfect 6.x Converter Stack Corruption Vulnerability - CVE-2009-0088
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, compromised Web sites and Web sites that accept or host user-provided content or advertisements 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 Instant Messenger message that takes users to the attacker's Web site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
- The vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
- An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.
- Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancelbefore opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and later editions of Office.
Workarounds for Word 2000 WordPerfect 6.x Converter Stack Corruption Vulnerability - CVE-2009-0088
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:
- Do not open or save Microsoft Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.
- Disable the Office text converter by restricting access to wpft632.cnv
An administrator can apply an access list to the affected converter to ensure it is no longer loaded by Microsoft Office Word. This effectively prevents exploitation of the issue.
Warning Undo this workaround before installing this security update.
In order to apply the access list, run the following command from the command prompt.
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wpft632.cnv" /E /P everyone:N
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\wpft632.cnv" /E /P everyone:NImpact of workaround. Microsoft Office Word will no longer load WordPerfect documents.
How to undo the workaround.
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\wpft632.cnv" /E /R everyone
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\wpft632.cnv" /E /R everyone
FAQ for Word 2000 WordPerfect 6.x Converter Stack Corruption Vulnerability - CVE-2009-0088
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 remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
This vulnerability requires that a user open a specially crafted WordPerfect 6.x document with Microsoft Office Word 2000.
What are the Microsoft Office WordPerfect 6.x Converter and the Microsoft Office Converter Pack?
The Microsoft Office WordPerfect 6.x Converter helps users convert documents from Corel WordPerfect 6.x file formats to MicrosoftOffice Word file formats. The WordPerfect 6.x Converter is included in all versions of Office and is also available separately in the Microsoft Office Converter Pack.
The Microsoft Office Converter Pack combines file converters and filters that were not included in earlier versions of Office. These converters and filters allow Office to use additional document formats that were not natively supported. The Microsoft Office Converter Pack is available as a Web download.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code 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?
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted WordPerfect 6.x file to the user and by convincing the user to open the file.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a WordPerfect 6.x document that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's web site.
What systems are primarily at risk from the vulnerability?
All systems where WordPad is used to open up Word documents from untrusted sources, such as workstations or terminal servers, are primarily at risk of this vulnerability. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this..
What does the update do?
The update removes the vulnerability by modifying the way that Word validates the length of a string when parsing a WordPerfect document.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No, 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.
WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2009-0235
A remote code execution vulnerability exists in WordPad as a result of memory corruption when a user opens a specially crafted Word file.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0235.
Mitigating Factors for WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2009-0235
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, compromised Web sites and Web sites that accept or host user-provided content or advertisements 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 Instant Messenger message that takes users to the attacker's Web site. After they click the link, they would be prompted to perform several actions. An attack could only occur after they performed these actions.
- The vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
- An attacker who successfully exploited this vulnerability could gain the same privileges as the user. Users whose accounts are configured to have fewer privileges on the system could be less impacted than users who operate with administrative privileges.
- A website attempting to exploit the vulnerability would cause a dialog box to appear. The user would be prompted to decide if they wanted to open the file or not, unless the user had previously unchecked the option "Always ask before opening this type of file."
Workarounds for WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2009-0235
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:
- Do not open or save Microsoft Office, RTF or Write files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file. This includes all files that have .wri, .rtf, and .doc file extensions as well files with other extensions. Be aware that WordPad could also be used to open specially crafted documents regardless of the file name extension.
- Disable the Word 6 converter by restricting access to mswrd8.wpc
An administrator can apply an access control list to the affected converter to ensure it is no longer loaded by WordPad. This effectively prevents exploitation of the issue.
Warning Undo this workaround before installing this security update.
In order to apply the access list, run the following commands from the command prompt. Note that some of these may result in an error message, this is expected.
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\mswrd832.cnv" /E /P everyone:N
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\mswrd832.cnv" /E /P everyone:N
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd8.wpc" /E /P everyone:N
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd864.wpc" /E /P everyone:N
echo y| cacls "%ProgramFiles(x86)%\Windows NT\Accessories\mswrd8.wpc" /E /P everyone:NImpact of workaround. Upon implementing the workaround, the user will no longer be able to convert Word 6 documents to WordPad RTF or Word 2003 documents. Microsoft Office Word will return an error saying, "The file appears to be corrupted."
How to undo the workaround.
echo y| cacls "%ProgramFiles%\Common Files\Microsoft Shared\TextConv\mswrd832.cnv" /E /R everyone
echo y| cacls "%ProgramFiles(x86)%\Common Files\Microsoft Shared\TextConv\mswrd832.cnv" /E /R everyone
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd8.wpc" /E /R everyone
echo y| cacls "%ProgramFiles%\Windows NT\Accessories\mswrd864.wpc" /E /R everyone
echo y| cacls "%ProgramFiles(x86)%\Windows NT\Accessories\mswrd8.wpc" /E /R everyone
FAQ for WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2009-0235
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 remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
This vulnerability requires that a user open a specially crafted Word 97 document with an affected version of WordPad.
What are WordPad Text Converters?
WordPad is a default component of Microsoft Windows operating systems. Text converters in WordPad allow users who do not have Microsoft Office Word installed to open documents in Microsoft Windows Write (.wri) and Microsoft Office Word 6.0, Microsoft Office Word 97, Microsoft Office Word 2000, and Microsoft Office Word 2002 (.doc) file formats. These text converters also allow users to save documents in the Word 6.0 file format.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code 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?
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Word 97 file to the user and by convincing the user to open the file.
In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word 97 document that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content 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 Instant Messenger message that takes users to the attacker's Web site.
What systems are primarily at risk from the vulnerability?
All systems where WordPad is used to open Word documents from untrusted sources, such as workstations or terminal servers, are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.
What does the update do?
This update removes the vulnerability by changing the way that the WordPad Text Converters handle opening specially crafted Word 97 files.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No, 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 | Yes |
| 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 |
| Microsoft Office Word 2000 Service Pack 3 | No |
| Microsoft Office Word 2002 Service Pack 3 | Yes |
| Microsoft Office Converter Pack | Yes |
For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.
Note For customers using legacy software not supported by MBSA 2.1, Microsoft Update, and Windows Server Update Services: please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
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 | Yes | Yes | Yes | Yes |
| 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 |
| Microsoft Office Word 2000 Service Pack 3 | Yes | Yes | No | No |
| Microsoft Office Word 2002 Service Pack 3 | Yes | Yes | Yes | Yes |
| Microsoft Office Converter Pack | Yes | Yes | Yes | Yes |
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.
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 If you have used an Administrative Installation Point (AIP) for deploying Office 2000, Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline. For more information, see the Office Administrative Installation Point heading in this section.
Office Administrative Installation Point
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your system.
- For supported versions of Microsoft Office 2000, see How to Create an Administrative Installation Point. For more information about how to change the source for a client system from an updated administrative installation point to an Office 2000 Service Pack 3 (SP3), see Microsoft Knowledge Base Article 932889.
Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office 2000 Clients from a Patched Administrative Image. - For supported versions of Microsoft Office XP, see Creating an Administrative Installation Point. For more information on how to change the source for a client system from an updated administrative installation point to an Office XP original baseline source, see Microsoft Knowledge Base Article 922665.
Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office XP Clients from a Patched Administrative Image. - For supported versions of Microsoft Office 2003, see Creating an Administrative Installation Point. For more information on how to change the source for a client computer from an updated administrative installation point to an Office 2003 original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 902349.
Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article, Distributing Office 2003 Product Upgrades. - For supported versions of the 2007 Microsoft Office system, see Create a network installation point for the 2007 Office system.
Note If you plan to manage security updates centrally, use Windows Server Update Services. For more information about how to deploy security updates for the 2007 Microsoft Office system using Windows Server Update Services, visit the Windows Server Update Services Web site.
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 Windows 2000 Service Pack 4: Windows2000-KB923561-x86-ENU /quiet |
| Installing without restarting | For Microsoft Windows 2000 Service Pack 4: Windows2000-KB923561-x86-ENU /norestart |
| Update log file | For Microsoft Windows 2000 Service Pack 4: kb923561.log |
| 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 | Microsoft Windows 2000 Service Pack 4: Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB923561$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 960477 |
| Registry Key Verification | For Microsoft Windows Service Pack 4: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows 2000\SP5\KB923561\Filelist |
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. |
| /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
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 | |
| /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 | Windows XP Service Pack 2 and Windows XP Service Pack 3: WindowsXP-KB923561-x86-ENU /quiet |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB923561-x64-ENU /quiet | |
| Installing without restarting | Windows XP Service Pack 2 and Windows XP Service Pack 3: WindowsXP-KB923561-x86-ENU /norestart |
| Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2: WindowsServer2003.WindowsXP-KB923561-x64-ENU /norestart | |
| Update log file | KB923561.log |
| 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 | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB923561$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 960477 |
| Registry Key Verification | For all supported 32-bit editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB923561\Filelist |
| For all supported x64-based editions of Windows XP: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB923561/filelist |
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. |
| /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
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 | |
| /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 all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB923561-x86-ENU /quiet |
| For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB923561-x64-ENU /quiet | |
| For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB923561-ia64-ENU /quiet | |
| Installing without restarting | For all supported 32-bit editions of Windows Server 2003: WindowsServer2003-KB923561-x86-ENU /norestart |
| For all supported x64-based editions of Windows Server 2003: WindowsServer2003.WindowsXP-KB923561-x64-ENU /norestart | |
| For all supported Itanium-based editions of Windows Server 2003: WindowsServer2003-KB923561-ia64-ENU /norestart | |
| Update log file | KB923561.log |
| 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 | This security update does not support HotPatching. For more information about HotPatching, see Microsoft Knowledge Base Article 897341. |
| Removal Information | Use Add or Remove Programs tool in Control Panel or the Spuninst.exe utility located in the %Windir%\$NTUninstallKB923561$\Spuninst folder |
| File Information | See Microsoft Knowledge Base Article 960477 |
| Registry Key Verification | HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB923561\Filelist |
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. |
| /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
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 | |
| /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.
Office 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 | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
| Deployment | |
| Installing without user intervention | office2000-kb921606-fullfile-enu /q:a |
| Installing without restarting | office2000-kb921606-fullfile-enu /r:n |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. For features you can selectively install, see the Office Features for Administrative Installations subsection in this section. |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| Hotpatching | Not applicable |
| Removal Information | After you install the update, you cannot remove it. To revert to an installation before the update was installed; you must remove the application, and then install it again from the original media. |
| File Information | See Microsoft Knowledge Base Article 960477 |
| 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 |
|---|---|
| MSPUB, O9PUB, 09PB | ProductFiles,PubPrimary,MSDrawFiles |
| O9EXL | ProductFiles, EXCELNonBootFiles |
| O9PRM | ProductFiles, OUTLOOKNonBootFiles, WORDNonBootFiles, ACCESSNonBootFiles, EXCELNonBootFiles, FPClientNonBootFiles, PPTNonBootFiles, ProductNonBootFiles |
| O9PRO | ProductFiles, OUTLOOKNonBootFiles, WORDNonBootFiles, ACCESSNonBootFiles, EXCELNonBootFiles, PPTNonBootFiles |
| O9SBE, 9327_o9procd1_sbe_coxs_slv_data1 product | ProductFiles, OUTLOOKNonBootFiles,WORDNonBootFiles, EXCELNonBootFiles |
| O9FP | ProductFiles, FPClientNonBootFiles, ProductNonBootFiles |
| O9PIPC1 | ProductFiles, OUTLOOKNonBootFiles, MSDrawFiles, WORDNonBootFiles, EXCELNonBootFiles |
| O9PIPC2 | ProductFiles, MSDrawFiles, WORDNonBootFiles, EXCELNonBootFiles |
| O9PRMCD2 | ProductFiles,AccessRuntimeMaster, PubPrimary, MSDrawFiles, SBCMNonBootFiles |
| O9STD | ProductFiles, OUTLOOKNonBootFiles, WORDNonBootFiles, EXCELNonBootFiles, PPTNonBootFiles |
Note Administrators working in managed environments can find 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 setup switches 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.
| 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 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
After you install the update, you cannot remove it. To revert to an installation before the update was installed; you must remove the application, and then install it again from the original media.
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 Office, 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.
Office 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 | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
| Deployment | |
| Installing without user intervention | officexp-KB933399-FullFile-ENU /q:a |
| Installing without restarting | officexp-KB933399-FullFile-ENU /r:n |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. For features you can selectively install, see the Office Features for Administrative Installations subsection in this section. |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office XP 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 960477 |
| Registry Key Verification | Not applicable |
Office Features
The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features:
| Product | Feature |
|---|---|
| ACCESS, FP, OUTLOOK, PPT, ACCESSRT, PUB | ProductFiles |
| PIPC1, PROPLUS, PRO, SBE, STD, STDEDU | ProductFiles |
| EXCEL | EXCELNonBootFiles, ProductFiles |
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.
| 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 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. Note When you remove this update, you may be prompted to insert the Microsoft Office XP 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.
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.
Microsoft Office Converter Pack
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 | There are no more service packs planned for this software. The update for this issue may be included in a future update rollup. |
| Deployment | |
| Installing without user intervention | Office2003-kb960476-fullfile-enu /q:a |
| Installing without restarting | Office2003-kb960476-fullfile-enu /r:n |
| Update log file | Not applicable |
| Further information | For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. |
| Restart Requirement | |
| Restart required? | In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. |
| Hotpatching | Not applicable |
| Removal Information | Use Add or Remove Programs tool in Control Panel. |
| File Information | See Microsoft Knowledge Base Article 960477 |
| 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 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.
| Switch | Description |
|---|---|
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /q:u | Specifies user-quiet mode, which presents some dialog boxes to the user. |
| /q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. |
| /t:path | Specifies the target folder for extracting files. |
| /c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
| /c:path | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. |
| /r:n | Never restarts the system after installation. |
| /r:I | Prompts the user to restart the system if a restart is required, except when used with /q:a. |
| /r:a | Always restarts the system after installation. |
| /r:s | Restarts the system after installation without prompting the user. |
| /n:v | No version checking - Install the program over any earlier version. |
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
To remove this security update, use the Add or Remove Programs 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.
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.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
- Sean Larsson and Jun Mao of VeriSign iDefense Labs for reporting the WordPad Word 97 Text Converter Stack Overflow Vulnerability - CVE-2009-0235 (CVE-2009-0235)
- A researcher with Fortinet’s FortiGuard Global Security Research Team for reporting the WordPad and Office Text Converter Memory Corruption Vulnerability (CVE-2009-0087)
- A researcher with VeriSign iDefense Labs for reporting the Word 2000 WordPerfect 6.x Converter Stack Corruption Vulnerability (CVE-2009-0088)
Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Support
- Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
- 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 (April 14, 2009): Bulletin published.
- V1.1 (April 16, 2009): Added a warning message to the workarounds for disabling the converters, stating you must undo the workaround before installing this security update. This is an informational change only.
- V1.2 (May 20, 2009): Added entry to the section, Frequently Asked Questions (FAQ) Related to This Security Update, to communicate that the associated Microsoft Knowledge Base Article 921606 and Microsoft Knowledge Base Article 933399 have been updated with regards to the expected installation behavior for certain update files. This is an informational change only.
- V1.3 (June 17, 2009): Corrected bulletin replacement for the Microsoft Office Converter Pack (KB960476) update package. This is an informational change only. Customers who have already successfully installed the update do not need to reinstall.