Security Bulletin
Microsoft Security Bulletin MS05-023 - Critical
Vulnerabilities in Microsoft Word May Lead to Remote Code Execution (890169)
Published: April 12, 2005 | Updated: August 09, 2005
Version: 2.0
Summary
Who should read this document: Customers who are using the affected versions of Microsoft Word should apply the appropriate security update at the earliest opportunity.
Impact of Vulnerability: Remote code execution
Maximum Severity Rating: Critical
Recommendation: Customers should apply the update immediately.
Security Update Replacement: This bulletin replaces a prior security update. See the frequently asked questions (FAQ) section of this bulletin for the complete list.
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
- Microsoft Word 2000 and Microsoft Works Suite 2001 - Download the update
- Microsoft Word 2002, Microsoft Works Suite 2002, Microsoft Works Suite 2003, and Microsoft Works Suite 2004 - Download the update
- Microsoft Office Word 2003 - Download the update
- Microsoft Word 2003 Viewer - Download the update
- The software in this list has been tested to determine if the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support lifecycle for your product and version, visit the following Microsoft Support Lifecycle Web site.
General Information
Executive Summary
Executive Summary:
This update resolves two newly-discovered vulnerabilities in Microsoft Word that could allow an attacker to run arbitrary code on a users system. The vulnerabilities are documented in the Vulnerability Details section of this bulletin.
If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
Severity Ratings and Vulnerability Identifiers:
| Vulnerability Identifiers | Impact of Vulnerability | Word 2000 | Word 2002 | Word 2003 | Word 2003 Viewer |
|---|---|---|---|---|---|
| Buffer Overrun in Microsoft Word CAN-2004-0963 | Remote Code Execution\ Elevation of Privilege | Critical\ | Critical\ | Important | Important\ |
| Buffer Overrun in Microsoft Word CAN-2005-0558 | Remote Code Execution\ Elevation of Privilege | Critical | Critical\ | Important | Important |
| Aggregate Severity of All Vulnerabilities | Critical | Critical | Important | Important |
This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.
Frequently asked questions (FAQ) related to this security update
Why is Microsoft reissuing this bulletin?
Subsequent to the release of this bulletin, it was determined that the vulnerability addressed also affects Microsoft Word 2003 Viewer. Microsoft has updated the bulletin with additional information about Microsoft Word 2003 Viewer. Customers who are not using Microsoft Word 2003 Viewer and have previously installed the security updates provided as part of the original release of this bulletin do not need to install the new security update.
Will I have to uninstall any previous versions of Microsoft Word 2003 Viewer?
Yes, you will be required to remove any previous versions of the Word Viewer before installing the updated Word 2003 Viewer. To remove the previous versions use the Add or Remove Programs tool in Control Panel.
What updates does this release replace?
This security update replaces security bulletin MS03-050. The software affected is listed in the following table.
| Bulletin ID | Microsoft Word 2000 | Microsoft Word 2002 | Microsoft Office Word 2003 | Microsoft Office Word 2003 Viewer |
|---|---|---|---|---|
| MS03-050 | Replaced | Replaced | Not Applicable | Not Applicable |
Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine if this update is required?
Yes, but for local scans only. MBSA uses in integrated version of the Office Detection Tool (ODT) which does not support remote scans of this issue. For more information about MBSA, visit the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A; Web site.
Note MBSA does not support Microsoft Word Viewer 2003 and will not detect whether the update is required for that program. However, Microsoft has developed a version of the Enterprise Update Scanning Tool (EST) that will help customers determine if the security update is required.
Can I use Systems Management Server (SMS) to determine if this update is required?
Yes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site
You can deploy this update using the Inventory and Software Distribution feature of SMS.
Vulnerability Details
Buffer Overrun in Microsoft Word CAN-2004-0963:
A vulnerability exists in Microsoft Word that could allow an attacker to run arbitrary code on a users system.
If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges.
Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
Mitigating Factors for Buffer Overrun in Microsoft Word - CAN-2004-0963:
- 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 would be at less risk than users who operate with administrative privileges.
Workarounds for Buffer Overrun in Microsoft Word CAN-2004-0963:
Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified below.
Do not open Microsoft Word documents from unknown or untrusted sources.
Enable prompting for Office documents so that they will not auto-open.
Note By default, Internet Explorer will prompt the user to Open/Save As the document. However, if this functionality has been turned off, the documents will automatically be opened. To re-enable this functionality:
- Go to My Computer and click on Tools, then click Folder Options.
- Select the File Types tab
- For each Office file type, highlight and click Advanced
- Verify that the Confirm open after download setting is checked
- Uncheck the setting to Browse in same Window
- Select Ok and Close
Impact of Workaround:
Microsoft Office will now prompt the user to Open/Save As instead of allowing for malicious code to automatically be run.
FAQ for Buffer Overrun in Word - CAN-2004-0963:
What is the scope of the vulnerability?
This is a buffer overrun vulnerability. If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
What causes the vulnerability?
An unchecked buffer in Microsoft Word.
What might an attacker use the vulnerability to do?
If successfully exploited, an attacker could cause code of their choice to run with additional privileges on the system. This could allow the attacker to add, delete or modify data on the system, or take any other action of the attacker's choice.
Who could exploit the vulnerability?
Any user who could entice another user to open a specially-crafted document can attempt to exploit these vulnerabilities.
How could an attacker exploit the vulnerability?
An attacker could seek to exploit this vulnerability by creating a specially-crafted document that contains malicious code. The attacker could then send this to a user, typically through an e-mail message, and then persuade the user to open the file. An attacker could also host the specially-crafted document on a network share or on a Web site; however, the attacker would still need to persuade the user to open the document.
Microsoft Works Suite is listed as a vulnerable product - why?
Microsoft Works Suite includes Microsoft Word. Microsoft Works users should use Office Update to detect and to install the appropriate update.
What does the update do?
The update removes the vulnerability by modifying the way that Word validates the length of data before it passes the data to the allocated buffer.
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 CAN-2004-0963.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had seen examples of proof of concept code published publicly but had not received any information indicating that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Buffer Overrun in Microsoft Word CAN-2005-0558:
A vulnerability exists in Microsoft Word that could allow an attacker to run arbitrary code on a users system.
If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges.
Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
Mitigating Factors for Buffer Overrun in Microsoft Word - CAN-2005-0558:
- 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 would be at less risk than users who operate with administrative privileges.
Workarounds for Buffer Overrun in Microsoft Word CAN-2005-0558:
Microsoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified below.
Do not open Microsoft Word documents from unknown or untrusted sources.
Enable prompting for Office documents so that they will not auto-open.
Note By default, Internet Explorer will prompt the user to Open/Save As the document. However, if this functionality has been turned off, the documents will automatically be opened. To re-enable this functionality:
- Go to My Computer, click on Tools, then click Folder Options.
- Select the File Types tab
- For each Office file type, highlight and click Advanced
- Verify that the Confirm open after download setting is checked
- Uncheck the setting to Browse in same Window
- Select Ok and Close
Impact of Workaround:
Microsoft Office will now prompt the user to Open/Save As instead of allowing for malicious code to automatically be run.
FAQ for Buffer Overrun in Word - CAN-2005-0558:
What is the scope of the vulnerability?
This is a buffer overrun vulnerability. If a user is logged on with administrative privileges, an attacker who successfully exploited this vulnerability could take complete control of an affected system, including installing programs; viewing, changing, or deleting data; or creating new accounts with full privileges. Users whose accounts are configured to have fewer privileges on the system would be at less risk than users who operate with administrative privileges.
What causes the vulnerability?
An unchecked buffer in Microsoft Word.
What might an attacker use the vulnerability to do?
If successfully exploited, an attacker could cause code of their choice to run with additional privileges on the system. This could allow the attacker to add, delete or modify data on the system, or take any other action of the attacker's choice.
Who could exploit the vulnerability?
Any user who could entice another user to open a specially-crafted document can attempt to exploit these vulnerabilities.
How could an attacker exploit the vulnerability?
An attacker could seek to exploit this vulnerability by creating a specially-crafted document that contains malicious code. The attacker could then send this to a user, typically through an e-mail message, and then persuade the user to open the file. An attacker could also host the specially-crafted document on a network share or on a Web site; however, the attacker would still need to persuade the user to open the document.
Microsoft Works Suite is listed as a vulnerable product - why?
Microsoft Works Suite includes Microsoft Word. Microsoft Works users should use Office Update to detect and to install the appropriate update.
What does the update do?
The update removes the vulnerability by modifying the way that Word validates the length of data before it passes the data to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft had not received any information indicating that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
Security Update Information
Installation Platforms and Prerequisites:
For information about the specific security update for your platform, click the appropriate link:
Word 2000 (887977)
Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or later. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites:
Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition
Office 2000 Service Pack 3 (SP3) or Microsoft Works 2001 must be installed. Before you install this update, install Office 2000 SP3. For additional information about how to install Office 2000 SP3, see Microsoft Knowledge Base Article 326585.
For additional information about how to determine the version of Office on your computer, see Microsoft Knowledge Base Article 255275.
Inclusion in Future Service Packs:
The fix for this issue will be included in a future service pack.
Restart Requirement
No restart is required.
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 CD-ROM.
Automated Client Installation Information
Office Update Web Site
Microsoft recommends that you install the Microsoft Office 2000 client updates by using the Office Update Web site. The Office Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up-to-date.
To have the Office Update Web site detect the required updates that you must install on your computer, visit the Office Update Web site, and then click Check for Updates. After detection is complete, you will receive a list of recommended updates for your approval. Click Agree and Install to complete the process.
Manual Client Installation Information
For detailed information about how to manually install this update please review the following section.
Installation Information
The 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 | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file |
| /r:n | Never restarts the computer after installation. |
| /r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a |
| /r:a | Always restarts the computer after installation |
| /r:s | Restarts the computer after installation without prompting the user |
| /n:v | No version checking - Install the program over any earlier version |
Note These switches do not necessarily work with all updates. If a switch is not available that functionality is necessary for the correct installation of the update. Also, the use of the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should consult your support professional to understand why it failed to install.
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Client Deployment Information
- Download the client version of this security update.
- Click Save this program to disk, and then click OK.
- Click Save.
- Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
- If you are prompted to install the update, click Yes.
- Click Yes to accept the License Agreement.
- Insert your original source CD-ROM when you are prompted to do so, and then click OK.
- When you receive a message that indicates the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.
Client Installation File Information
The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Word 2000:
| File Name | Version | Date | Time | Size |
| Winword.exe | 9.0.0.8929 | 3/9/05 | 2:03 | 8,831,028 |
Verifying Update Installation
Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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.
Administrative Installation Information
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 computer.
Installation Information
The following setup switches are relevant to administrative installations as they allow an administrator to customize the manner in which the files are extracted from within the security update:
| Switch | Description |
|---|---|
| /? | Displays the command-line options |
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /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 | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file |
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Administrative Deployment Information
To update your administrative installation please perform the following procedure:
- Click Save and save the update file to the C:\ADMINUPDATE folder.
- Click Start, click Run, type “cmd” (without the quotes) in the Open box, and then click OK.
- At the command prompt, type the following lines, pressing ENTER after each line:
cd c:\adminupdate
office2000-kb887977-fullfile-enu.exe /c /t:c:\adminupdate - Read the license agreement, and if you agree, click Yes to accept the license agreement.
- At the command prompt, type “exit” (without the quotes) to quit Command Prompt.
- If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box:
- msiexec /a Admin Path\MSI File /p C:\adminupdate\MSP File SHORTFILENAMES=TRUE
- msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, winwordff.msp).
- You can append /qb+ to the command line so that the Administrative Installation dialog box and the End UserLicense Agreement dialog box do not appear.
- Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
- I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations that were originally installed from this administrative installation. To do this, please review the Workstation Deployment section. Any new installations that you run from this administrative installation point will include the update.
Warning Any workstation that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the Workstation Deployment section for this workstation.
Workstation Deployment Information
To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box:
msiexec /i Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu
where Admin Path is the path of your administrative installation point for your application (for example, C:\Office 2000), MSI File is the MSI database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that have to be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can use the following features:
| Product | Feature |
| Microsoft Word 2000 | WORDFiles |
Note Additional instructions are provided in Microsoft Knowledge Base Article 887977. Information concerning this update can also be found on the Microsoft Office 2000 Resource Kit Web site. The Windows Installer Documentation also provides additional information about the parameters supported by the Windows Installer.
Administrative Installation File Information
The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Word 2000:
| File Name | Version | Date | Time | Size |
| Winword.exe | 9.0.0.8929 | 3/9/05 | 2:03 | 8,831,028 |
Verifying Update Installation
Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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 (887978)
Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or later. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites:
Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition
Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
Office XP Service Pack 3 (SP3), Microsoft Works 2002, Microsoft Works 2003, or Microsoft Works 2004 must be installed. Before you install this update, install Office XP SP3. For additional information about how to install Office XP SP3, see Microsoft Knowledge Base Article 832671. The administrative update can also be installed on systems that are running Office XP SP2 or Office XP SP3.
For additional information about how to determine the version of Office XP on your computer, see Microsoft Knowledge Base Article 291331.
Inclusion in Future Service Packs:
The fix for this issue will be included in a future service pack.
Restart Requirement
No restart is required.
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 CD-ROM.
Automated Client Installation Information
Office Update Web Site
Microsoft recommends that you install the Microsoft Office XP client updates by using the Office Update Web site. The Office Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up-to-date.
To have the Office Update Web site detect the required updates that you must install on your computer, visit the Office Update Web site, and then click Check for Updates. After detection is complete, you will receive a list of recommended updates for your approval. Click Agree and Install to complete the process.
Manual Client Installation Information
For detailed information about how to manually install this update please review the following section.
Installation Information
The 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 | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file |
| /r:n | Never restarts the computer after installation. |
| /r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a |
| /r:a | Always restarts the computer after installation |
| /r:s | Restarts the computer after installation without prompting the user |
| /n:v | No version checking - Install the program over any earlier version |
Note These switches do not necessarily work with all updates. If a switch is not available that functionality is necessary for the correct installation of the update. Also, the use of the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should consult your support professional to understand why it failed to install.
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Client Deployment Information
- Download the client version of this security update.
- Click Save this program to disk, and then click OK.
- Click Save.
- Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
- If you are prompted to install the update, click Yes.
- Click Yes to accept the License Agreement.
- Insert your original source CD-ROM when you are prompted to do so, and then click OK.
- When you receive a message that indicates the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.
Client Installation File Information
The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Word 2002:
| File Name | Version | Date | Time | Size |
| Winword.exe | 10.0.6754.0 | 3/2/05 | 21:38 | 10,635,976 |
Verifying Update Installation
Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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.
Administrative Installation Information
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 computer.
Installation Information
The following setup switches are relevant to administrative installations as they allow an administrator to customize the manner in which the files are extracted from within the security update:
| Switch | Description |
|---|---|
| /? | Displays the command-line options |
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /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 | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file |
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Administrative Deployment Information
To update your administrative installation please perform the following procedure:
- Click Save and save the update file to the C:\ADMINUPDATE folder.
- Click Start, click Run, type “cmd” (without the quotes) in the Open box, and then click OK.
- At the command prompt, type the following lines, pressing ENTER after each line:
cd c:\adminupdate
officeXP-kb887978-fullfile-enu.exe /c /t:c:\adminupdate - Read the license agreement, and if you agree, click Yes to accept the license agreement.
- At the command prompt, type “exit” (without the quotes) to quit Command Prompt.
- If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box:
- msiexec /a Admin Path\MSI File /p C:\adminupdate\MSP File SHORTFILENAMES=TRUE
- msi database package for the application (for example, Proplus.msi), and MSP File is the name of the administrative update (for example, Winwordff.msp).
- You can append /qb+ to the command line so that the Administrative Installation dialog box and the End UserLicense Agreement dialog box do not appear.
- Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
- I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations that were originally installed from this administrative installation. To do this, please review the Workstation Deployment section. Any new installations that you run from this administrative installation point will include the update.
Warning Any workstation that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the Workstation Deployment section for this workstation.
Workstation Deployment Information
To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box:
msiexec /i Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu
where Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeXP), MSI File is the MSI database package for the application (for example, Proplus.msi), and Feature List is the list of feature names (case sensitive) that have to be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can use the following features:
| Product | Feature |
| Microsoft Word 2002 | WORDFiles |
Note Additional instructions are provided in Microsoft Knowledge Base Article 887978. Information concerning this update can also be found on the Microsoft Office XP Resource Kit Web site. The Windows Installer Documentation also provides additional information about the parameters supported by the Windows Installer.
Administrative Installation File Information
The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Word 2002:
| File Name | Version | Date | Time | Size |
| Winword.exe | 10.0.6754 | 3/2/05 | 21:38 | 10,635,976 |
Verifying Update Installation
Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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 (887979)
Prerequisites and Additional Update Details
Important: Before you install this update, make sure that the following requirements have been met:
Office 2003 (Word 2003) Service Pack 1 must be installed. Before you install this update, install Office 2003 SP1. For additional information about how to install Office 2003 SP1, see Microsoft Knowledge Base Article 842532. The administrative update can also be installed on systems that are running Office 2003 RTM.
For additional information about how to determine the version of Office 2003 on your computer, see Microsoft Knowledge Base Article 821549.
Inclusion in Future Service Packs:
The fix for this issue will be included in a future service pack.
Restart Requirement
No restart is required.
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 CD-ROM.
Automated Client Installation Information
Office Update Web Site
Microsoft recommends that you install the Microsoft Office 2003 client updates by using the Office Update Web site. The Office Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up-to-date.
To have the Office Update Web site detect the required updates that you must install on your computer, visit the Office Update Web site, and then click Check for Updates. After detection is complete, you will receive a list of recommended updates for your approval. Click Agree and Install to complete the process.
Manual Client Installation Information
For detailed information about how to manually install this update please review the following section.
Installation Information
The 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 | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file |
| /r:n | Never restarts the computer after installation. |
| /r:I | Prompts the user to restart the computer if a restart is required, except when used with /q:a |
| /r:a | Always restarts the computer after installation |
| /r:s | Restarts the computer after installation without prompting the user |
| /n:v | No version checking - Install the program over any earlier version |
Note These switches do not necessarily work with all updates. If a switch is not available that functionality is necessary for the correct installation of the update. Also, the use of the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should consult your support professional to understand why it failed to install.
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Client Deployment Information
- Download the client version of this security update.
- Click Save this program to disk, and then click OK.
- Click Save.
- Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
- If you are prompted to install the update, click Yes.
- Click Yes to accept the License Agreement.
- Insert your original source CD-ROM when you are prompted to do so, and then click OK.
- When you receive a message that indicates the installation was successful, click OK.
Note If the security update is already installed on your computer, you receive the following error message: This update has already been applied or is included in an update that has already been applied.
Client Installation File Information
The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Word 2003:
| File Name | Version | Date | Time | Size |
| Winword.exe | 11.0.6502.0 | 4/1/05 | 20:00 | 12,053,704 |
Verifying Update Installation
Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool, which allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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.
Administrative Installation Information
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 computer.
Installation Information
The following setup switches are relevant to administrative installations as they allow an administrator to customize the manner in which the files are extracted from within the security update.
| Switch | Description |
|---|---|
| /? | Displays the command-line options |
| /q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
| /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 | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file |
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Administrative Deployment Information
To update your administrative installation please perform the following procedure:
- Click Save and save the update file to the C:\ADMINUPDATE folder.
- Click Start, click Run, type “cmd” (without the quotes) in the Open box, and then click OK.
- At the command prompt, type the following lines, pressing ENTER after each line:
cd c:\adminupdate
office2003-kb887979-fullfile-enu.exe /c /t:c:\adminupdate - Read the license agreement, and if you agree, click Yes to accept the license agreement.
- At the command prompt, type “exit” (without the quotes) to quit Command Prompt.
- If you are familiar with the procedure for updating your administrative installation, click Start, and then click Run. Type the following command in the Open box:
- msiexec /a Admin Path\MSI File /p C:\adminupdate\MSP File SHORTFILENAMES=TRUE
- msi database package for the application (for example, Proplus.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp).
- You can append /qb+ to the command line so that the Administrative Installation dialog box and the End UserLicense Agreement dialog box do not appear.
- Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
- I accept the terms in the License Agreement, and then click Install.
At this point, your administrative installation point is updated. Next, you must update the workstations that were originally installed from this administrative installation. To do this, please review the Workstation Deployment section. Any new installations that you run from this administrative installation point will include the update.
Warning Any workstation that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the Workstation Deployment section for this workstation.
Workstation Deployment Information
To deploy the update to the client workstations, click Start, and then click Run. Type the following command in the Open box:
msiexec /i Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu
where Admin Path is the path of your administrative installation point for your application (for example, C:\Office2003), MSI File is the MSI database package for the application (for example, Pro11.msi), and Feature List is the list of feature names (case sensitive) that have to be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can use the following features:
| Product | Feature |
| Microsoft Office Word 2003 | WORDFiles |
Note Additional instructions are provided in Microsoft Knowledge Base Article 887979. Information concerning this update can also be found on the Microsoft Office 2003 Resource Kit Web site. The Windows Installer Documentation also provides additional information about the parameters supported by the Windows Installer.
Administrative Installation File Information
The English version of this update has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Word 2003:
| File Name | Version | Date | Time | Size |
| Winword.exe | 11.0.6502.0 | 3/3/05 | 22:16 | 12,053,704 |
Verifying Update Installation
Microsoft Baseline Security Analyzer
To verify that a security update is installed on an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. This tool allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. 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 Viewer (887979)
Prerequisites and Additional Update Details
Note Microsoft Word 2003 Viewer is not part of the Office 2003 suite.
Restart Requirement
No restart is required.
Removal Information
To remove this update, use the Add or Remove Programs tool in Control Panel.
Installation Information
For detailed information about how to manually install this update please review the following section.
Installation Information
The 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 | Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file |
| /r:n | Never restarts the computer after installation. |
| /r:i | Prompts the user to restart the computer if a restart is required, except when used with /q:a |
| /r:a | Always restarts the computer after installation |
| /r:s | Restarts the computer after installation without prompting the user |
| /n:v | No version checking - Install the program over any earlier version |
Note These switches do not necessarily work with all updates. If a switch is not available that functionality is necessary for the correct installation of the update. Also, the use of the /N:V switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should consult your support professional to understand why it failed to install.
For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.
Word Viewer 2003:
| File Name | Version | Date | Time | Size |
| Wordview.exe | 11.0.6506.0 | 5/3/2005 | 19:09 | 6,864,584 |
Verifying Update Installation
File Version Verification
Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. 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 computer by comparing it to the version that is documented in the appropriate file information table.
Note Attributes other than 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 the update installation. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
• Alex Li for reporting the Word vulnerability (CAN-2005-0558).
Obtaining Other Security Updates:
Updates for other security issues are available from the following locations:
- Security updates are available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch."
- Updates for consumer platforms are available from the Windows Update Web site.
Support:
- Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
- International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Security Resources:
- The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
- Microsoft Software Update Services
- Microsoft Baseline Security Analyzer (MBSA)
- Windows Update
- Windows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.
- Office Update
Software Update Services:
By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.
For more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site.
Systems Management Server:
Microsoft Systems Management Server (SMS) delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and to perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, see the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.
Note SMS uses the Microsoft Baseline Security Analyzer and the Microsoft Office Detection Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, see the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.
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 12, 2005): Bulletin published
- V1.1 (April 14, 2005): Bulletin updated to reflect a revised “Security Update Information” section for the Word 2003 security update
- V1.2 (May 4 2005): Bulletin updated to add msiexec in the administrative installation in “Administrative Deployment” section for all versions
- V1.3 (May 18 2005): Bulletin updated Word 2000 file version for Winword.exe
- V2.0 (August 9, 2005): Bulletin updated to reflect an additional affected product- Microsoft Word 2003 Viewer
Built at 2014-04-18T13:49:36Z-07:00