Vulnerabilities in Microsoft Office Word Could Allow Remote Code Execution (969514)
Published: June 09, 2009
Version: 1.0
General Information
Executive Summary
This security update resolves two privately reported vulnerabilities that could allow remote code execution if a user opens a specially crafted Word file. An attacker who successfully exploited either vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
This security update is rated Critical for all supported editions of Microsoft Office Word 2000. For all supported editions of Microsoft Office Word 2002, Microsoft Office Word 2003, Microsoft Office Word 2007, Microsoft Office 2004 for Mac, and Microsoft Office 2008 for Mac, and all supported versions of Open XML File Format Converter for Mac, Microsoft Office Compatibility Pack, and Microsoft Office Word Viewers, this security update is rated Important. For more information, see the subsection, Affected and Non-Affected Software, in this section
The update addresses the vulnerabilities by modifying the way that Word opens and parses files. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. Microsoft recommends that customers apply the update immediately.
Known Issues.Microsoft Knowledge Base Article 969514 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Frequently Asked Questions (FAQ) Related to This Security Update
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
What are the known issues that customers may experience when installing this security update? Microsoft Knowledge Base Article 969514 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.
MS09-017 and MS09-021 also describe vulnerabilities in Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, and Open XML File Format Converter for Mac. How do MS09-017 and MS09-021 relate to this bulletin (MS09-027)?
The security update packages in this bulletin, MS09-027, for Microsoft Office 2004 for Mac (KB969661), Microsoft Office 2008 for Mac (KB971822), and Open XML File Format Converter for Mac (KB971824) also address the vulnerabilities described in MS09-017 and MS09-021. Users with Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, or Open XML File Format Converter for Mac installed will only need to install these security update packages once.
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.
What components of the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats are updated by this bulletin?
The update included with this security bulletin applies only to the specific component within the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats that is affected. For example, in an Excel bulletin, only the Excel compatibility pack component files are included in the update packages and not Word or PowerPoint compatibility pack component files. Word compatibility pack component files are updated in a Word bulletin and PowerPoint compatibility pack component files are updated in a PowerPoint bulletin.
What is Microsoft Office Word Viewer?
Microsoft Office Word Viewer is a replacement for Word Viewer 2003 and all previous Word Viewer versions. For information on how to obtain the latest Word Viewer, see Microsoft Knowledge Base Article 891090.
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 June bulletin summary. For more information, see Microsoft Exploitability Index.
Affected Software
Word Buffer Overflow Vulnerability - CVE-2009-0563
Word Buffer Overflow Vulnerability - CVE-2009-0565
Aggregate Severity Rating
Microsoft Office Suites and Components
Microsoft Office Word 2000 Service Pack 3
Not applicable
Critical Remote Code Execution
Critical
Microsoft Office Word 2002 Service Pack 3
Important Remote Code Execution
Important Remote Code Execution
Important
Microsoft Office Word 2003 Service Pack 3
Important Remote Code Execution
Not applicable
Important
Microsoft Office Word 2007 Service Pack 1 and Microsoft Office Word 2007 Service Pack 2
Important Remote Code Execution
Important Remote Code Execution
Important
Microsoft Office for Mac
Microsoft Office for Mac 2004
Important Remote Code Execution
Important Remote Code Execution
Important
Microsoft Office for Mac 2008
Important Remote Code Execution
Important Remote Code Execution
Important
Open XML File Format Converter for Mac
Important Remote Code Execution
Important Remote Code Execution
Important
Other Office Software
Microsoft Office Word Viewer 2003 Service Pack 3
Important Remote Code Execution
Not applicable
Important
Microsoft Office Word Viewer
Important Remote Code Execution
Not applicable
Important
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2
Important Remote Code Execution
Important Remote Code Execution
Important
Word Buffer Overflow Vulnerability - CVE-2009-0563
A remote code execution vulnerability exists in the way that Microsoft Office Word handles a specially crafted Word file that includes a malformed record. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0563.
Mitigating Factors for Word Buffer Overflow Vulnerability - CVE-2009-0563
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 an Office file 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, and then convince them to open the specially crafted Office file.
The vulnerability cannot 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 user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
Workarounds for Word Buffer Overflow Vulnerability - CVE-2009-0563
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:
Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents from unknown or untrusted sources and locations
The following registry scripts can be used to set the File Block policy.
Note Modifying the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from incorrect modification of the Registry can be solved. Modify the Registry at your own risk.
For Office 2003
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Security\FileOpenBlock]
"BinaryFiles"=dword:00000001
Note In order to use 'FileOpenBlock' with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.
For 2007 Office system
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
"BinaryFiles"=dword:00000001
Note In order to use 'FileOpenBlock' with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.
Impact of workaround. Users who have configured the File Block policy and have not configured a special “exempt directory” as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.
How to undo the workaround:
For Office 2003
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Security\FileOpenBlock]
"BinaryFiles"=dword:00000000
For 2007 Office system
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
"BinaryFiles"=dword:00000000
Do not open or save Word 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.
FAQ for Word Buffer Overflow Vulnerability - CVE-2009-0563
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?
When Microsoft Office Word opens a specially crafted Word file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.
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 Word file with an affected version of Microsoft Office Word.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Word document 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 an Office file 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, and then convince them to open the specially crafted Word file.
What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office Word is used, including workstations and 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 addresses the vulnerability by modifying the way that Microsoft Office Word opens specially crafted Word files.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received 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.
Word Buffer Overflow Vulnerability - CVE-2009-0565
A remote code execution vulnerability exists in the way that Microsoft Office Word handles a specially crafted Word file that includes a malformed record. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0565.
Mitigating Factors for Word Buffer Overflow Vulnerability - CVE-2009-0565
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 an Office file 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, and then convince them to open the specially crafted Office file.
The vulnerability cannot 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 user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before 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 Buffer Overflow Vulnerability - CVE-2009-0565
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:
Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents from unknown or untrusted sources and locations
The following registry scripts can be used to set the File Block policy.
Note Modifying the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from incorrect modification of the Registry can be solved. Modify the Registry at your own risk.
For 2007 Office system
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
"BinaryFiles"=dword:00000001
Note In order to use 'FileOpenBlock' with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.
Impact of workaround. Users who have configured the File Block policy and have not configured a special “exempt directory” as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.
How to undo the workaround:
For 2007 Office system
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
"BinaryFiles"=dword:00000000
Do not open or save Word 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.
FAQ for Word Buffer Overflow Vulnerability - CVE-2009-0565
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?
When Microsoft Office Word opens a specially crafted Word file, it may corrupt system memory in such a way that an attacker could execute arbitrary code.
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 Word file with an affected version of Microsoft Office Word.
In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Word 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 an Office file 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, and then convince them to open the specially crafted Word file.
What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office Word is used, including workstations and 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 addresses the vulnerability by modifying the way that Microsoft Office Word opens specially crafted Word files.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received 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.
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 Office Word 2000 Service Pack 3
No
Microsoft Office Word 2002 Service Pack 3
Yes
Microsoft Office Word 2003 Service Pack 3
Yes
Microsoft Office Word 2007 Service Pack 1 and Microsoft Office Word 2007 Service Pack 2
Yes
Microsoft Office 2004 for Mac
No
Microsoft Office 2008 for Mac
No
Open XML File Format Converter for Mac
No
Microsoft Office Word Viewer 2003 Service Pack 3
Yes
Microsoft Office Word Viewer
Yes
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2
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 Office Word 2000 Service Pack 3
Yes
Yes
No
No
Microsoft Office Word 2002 Service Pack 3
Yes
Yes
Yes
Yes
Microsoft Office Word 2003 Service Pack 3
Yes
Yes
Yes
Yes
Microsoft Office Word 2007 Service Pack 1 and Microsoft Office Excel 2007 Service Pack 2
No
No
Yes
Yes
Microsoft Office 2004 for Mac
No
No
No
No
Microsoft Office 2008 for Mac
No
No
No
No
Open XML File Format Converter for Mac
No
No
No
No
Microsoft Office Word Viewer 2003 Service Pack 3
Yes
Yes
Yes
Yes
Microsoft Office Word Viewer
Yes
Yes
Yes
Yes
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2
No
No
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.
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.
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 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.
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:
Word 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-kb969600-fullfile-enu /q:a
Installing without restarting
Office2000-kb969600-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.
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
O9PRO, O9STD
WORDFiles
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:
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.
Word 2002 (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-kb969602-fullfile-enu /q:a
Installing without restarting
OfficeXP-kb969602-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.
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
PIPC1, PROPLUS, PRO, SBE, STD, STDEDU, WORD
WORDFiles
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:
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.
Word 2003 (all editions), Word Viewer 2003, and Word Viewer
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
For Word 2003:\ office2003-KB969603-FullFile-ENU /q:a\ \ For Word Viewer 2003 and Word Viewer:\ Office2003-kb969614-fullfile-enu /q:a
Installing without restarting
For Word 2003:\ office2003-KB969603-FullFile-ENU /r:n\ \ For Word Viewer 2003 and Word Viewer:\ Office2003-kb969614-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 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.
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:
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:
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.
Word 2007 (all editions) and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats
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 Word 2007:\ word2007-kb969604-fullfile-x86-glb /passive\ \ For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats:\ Office2007-kb969613-fullfile-x86-glb /passive
Installing without restarting
For Word 2007:\ word2007-kb969604-fullfile-x86-glb /norestart\ \ For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats:\ Office2007-kb969613-fullfile-x86-glb /norestart
Update log file
Not applicable
Further information
For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement
Restart required?
In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.
This security update requires that Windows Installer 3.1 or later be installed on the system.
To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:
This security update supports the following setup switches.
Switch
Description
/? or /help
Displays usage dialog.
/passive
Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quiet
Specifies quiet mode, or suppresses prompts, when files are being extracted.
/norestart
Suppresses restarting the system if the update requires a restart.
/forcerestart
Automatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extract
Extracts the files without installing them. You are prompted for a target folder.
/extract:<path>
Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/lang:<LCID>
Forces the use of a specific language, when the update package supports that language.
/log:<log file>
Enables logging, by both Vnox and Installer, during the update installation.
Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.
Removing the Update
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 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs 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.
Office 2004 for Mac
Deployment Information
Prerequisites
Mac OS X version 10.2.8 or later on a G3, Mac OS X-compatible processor or higher
Mac OS X user accounts must have administrator privileges to install this security update
Installing the Update
Download and install the appropriate language version of the Microsoft Office 2004 for Mac 11.5.5 Update from the Microsoft Download Center.
Quit any applications that are running, including virus-protection applications, all Microsoft Office applications, Microsoft Messenger for Mac, and Office Notifications, because they might interfere with installation.
Open the Microsoft Office 2004 for Mac 11.5.5 Update volume on your desktop. This step might have been performed for you.
To start the update process, in the Microsoft Office 2004 for Mac 11.5.5 Update volume window, double-click the Microsoft Office 2004 for Mac 11.5.5 Update application, and follow the instructions on the screen.
If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following “Verifying Update Installation” heading. To remove the update installer, first drag the Microsoft Office 2004 for 11.5.5 Update volume to the Trash, and then drag the file that you downloaded to the Trash.
Verifying Update Installation
To verify that a security update is installed on an affected system, follow these steps:
In the Finder, navigate to the Application Folder (Microsoft Office 2004: Office).
Select the file, Microsoft Component Plugin.
On the File menu, click Get Info or Show Info.
If the Version number is 11.5.5, the update has been successfully installed.
Restart Requirement
This update does not require you to restart your computer.
Removing the Update
This security update cannot be uninstalled.
Additional Information
If you have technical questions or problems downloading or using this update, visit Microsoft for Mac Supportto learn about the support options that are available to you.
Office 2008 for Mac
Deployment Information
Prerequisites
Mac OS X version 10.4.9 or later on an Intel, PowerPC G5, or PowerPC G4 (500 MHz or faster) processor
Mac OS X user accounts must have administrator privileges to install this security update
Installing the Update
Download and install the appropriate language version of the Microsoft Office 2008 for Mac 12.1.9 Update from the Microsoft Download Center.
Quit any applications that are running, including virus-protection applications, all Microsoft Office applications, Microsoft Messenger for Mac, and Office Notifications, because they might interfere with installation.
Open the Microsoft Office 2008 for Mac 12.1.9 Update volume on your desktop. This step might have been performed for you.
To start the update process, in the Microsoft Office 2008 for Mac 12.1.9 Update volume window, double-click the Microsoft Office 2008 for Mac 12.1.9 Update application, and follow the instructions on the screen.
If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following “Verifying Update Installation” heading. To remove the update installer, first drag the Microsoft Office 2008 for Mac 12.1.9 Update volume to the Trash, and then drag the file that you downloaded to the Trash.
Verifying Update Installation
To verify that a security update is installed on an affected system, follow these steps:
In the Finder, navigate to the Application Folder (Microsoft Office 2008: Office).
Select the file, Microsoft Component Plugin.
On the File menu, click Get Info or Show Info.
If the Version number is 12.1.9, the update has been successfully installed.
Restart Requirement
This update does not require you to restart your computer.
Removing the Update
This security update cannot be uninstalled.
Additional Information
If you have technical questions or problems downloading or using this update, visit Microsoft for Mac Supportto learn about the support options that are available to you.
Open XML File Converter For Mac
Deployment Information
Prerequisites
Mac OS X version 10.4.9 or later on an Intel, PowerPC G5, or PowerPC G4 (500 MHz or faster) processor
Mac OS X user accounts must have administrator privileges to install this security update
Installing the Update
Download and install the appropriate language version of the Open XML File Converter for Mac 1.0.3 Update from the Microsoft Download Center.
Quit any applications that are running, including virus-protection applications, all Microsoft Office applications, Microsoft Messenger for Mac, and Office Notifications, because they might interfere with installation.
Open the Open XML File Converter for Mac 1.0.3 Update volume on your desktop. This step might have been performed for you.
To start the update process, in the Open XML File Converter for Mac 1.0.3 Update volume window, double-click the Open XML File Converter for Mac 1.0.3 Update application, and follow the instructions on the screen.
If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following “Verifying Update Installation” heading. To remove the update installer, first drag the Open XML File Converter for Mac 1.0.3 Update volume to the Trash, and then drag the file that you downloaded to the Trash.
Verifying Update Installation
To verify that a security update is installed on an affected system, follow these steps:
In the Finder, navigate to the Application Folder (Open XML File Converter for Mac : Office).
Select the file, Microsoft Component Plugin.
On the File menu, click Get Info or Show Info.
If the Version number is 1.0.3, the update has been successfully installed.
Restart Requirement
This update does not require you to restart your computer.
Removing the Update
This security update cannot be uninstalled.
Additional Information
If you have technical questions or problems downloading or using this update, visit Microsoft for Mac Supportto learn about the support options that are available to you.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
Wushi of team509, working with the Zero Day Initiative, for reporting the Word Buffer Overflow Vulnerability (CVE-2009-0563)
Nicolas Joly of VUPEN Security for reporting the Word Buffer Overflow Vulnerability (CVE-2009-0565)
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.
Learn how to use Windows Server Update Services to deploy operating system updates to computers on your network. Select the appropriate deployment option and combine WSUS with Microsoft Azure Update Management to manage server updates.