Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Microsoft Security Bulletin MS05-035 - Critical

Vulnerability in Microsoft Word Could Allow Remote Code Execution (903672)

Published: July 12, 2005

Version: 1.0

Summary

Who should read this document: Customers who use Microsoft Word 2000, Microsoft Word 2002 or Microsoft Works Suite

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update at the earliest opportunity.

Security Update Replacement: This bulletin replaces the MS05-023 security update.

Caveats: None

Tested Software and Security Update Download Locations:

Affected Software:

Non-Affected Software:

  • Microsoft Office 2003 Word
  • Microsoft Office Word 2003 Viewer

The software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.

General Information

Executive Summary:

This update resolves a newly-discovered, privately-reported vulnerability. The vulnerability is documented in the “Vulnerability Details” section of this bulletin.

If a user is logged on with administrative user rights, 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.

We recommend that customers apply the update at the earliest opportunity.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityMicrosoft Word 2000Microsoft Word 2002
Font Parsing Vulnerability CAN-2005-0564Remote Code ExecutionCriticalImportant

Note The severity ratings for Microsoft Works Suite maps to the Microsoft Word versions as follows:

  • The Microsoft Works Suite 2000, 2001, 2002, 2003 and 2004 severity rating is the same as the Microsoft Word 2000 severity rating.

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.

Why is Microsoft Works Suite is listed in affected software?
Microsoft Works Suite is listed in affected software because it includes Microsoft Word. Microsoft Works users should use Office Update to detect and to install the appropriate update.

What updates does this release replace?
This security update replaces a prior security update. The security bulletin ID and affected operating systems are listed in the following table.

Bulletin IDMicrosoft Word 2000Microsoft Word 2002Microsoft Works Suite 2000, 2001, 2002, 2003 and 2004
MS05-023ReplacedReplacedReplaced

Can I use the Microsoft Baseline Security Analyzer (MBSA) 1.2.1 to determine whether this update is required?
Yes, but for local scans only. MBSA uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this issue. For more information about MBSA, visit theMBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A Web site.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.

Note MBSA 2.0 does not support Microsoft Office 2000.

Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. SMS uses MBSA for detection; therefore, SMS has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect.

SMS can also use the Microsoft Office Inventory Tool to detect for required updates for Microsoft Office applications.

For more information about SMS, visit the SMS Web site.

Can I use SMS to determine if other programs are installed that have to be updated?
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.

Font Parsing Vulnerability in Word - CAN-2005-0564:

A remote code execution vulnerability exists in Word that could allow an attacker who successfully exploited this vulnerable to take complete control of the affected system.

Mitigating Factors for Font Parsing Vulnerability in Word - CAN-2005-0564:

  • 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.
  • The vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.

Workarounds for Font Parsing Vulnerability in Word - CAN-2005-0564:

Do not open or save Microsoft Word files that you receive from un-trusted sources.
This vulnerability could be exploited when a user opens a file.

FAQ for Font Parsing Vulnerability in Word - Vulnerability - CAN-2005-0564:

What is the scope of the vulnerability?
This is a remote code execution vulnerability. If a user is logged on with administrative user rights, 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. However, user interaction is required to exploit this vulnerability.

What causes the vulnerability?
An unchecked buffer in the process used by the affected software to process fonts.

What might an attacker use the vulnerability to do?
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.

Who could exploit the vulnerability?
Anyone who could persuade a user to open a specially-crafted document can attempt to exploit these vulnerabilities.

How could an attacker exploit the vulnerability?
An attacker could exploit the vulnerability by sending a specially-crafted document to the user and by persuading the user to open the file. If the user opened the file, the affected software could fail and could allow the attacker to execute arbitrary code.

Can the vulnerability be exploited automatically through an e-mail message?
No. A user must open a specially-crafted document that an attacker provided in order for the attacker to attempt to exploit the vulnerability. Viewing an e-mail message, even if Microsoft Word had been selected as the default e-mail editor for Microsoft Outlook, would not expose the vulnerability.

What does the update do?
The update addresses the vulnerability by modifying the way that the affected software validates the length of a message before it passes the message to the allocated buffer.

What systems are primarily at risk from the vulnerability?
Workstations and terminal servers are primarily at risk. Servers are only at risk if users who do not have sufficient administrative credentials are given the ability to log on to servers and to run programs. However, best practices strongly discourage allowing this.

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.

Affected Software:

For information about the specific security update for your affected software, click the appropriate link:

Word 2000

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 or later 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 the following Microsoft Web site: Windows Installer 2.0 for Windows 2000 and Windows NT4.0.
  • Office 2000 Service Pack 3 (SP3) or Microsoft Works 2000 or 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 may be included in a future service pack.

Restart Requirement

To help reduce the chance that a reboot 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.

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

We recommend 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:

Supported Security Update Installation Switches
SwitchDescription
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted
/q:uSpecifies user-quiet mode, which presents some dialog boxes to the user
/q:aSpecifies administrator-quiet mode, which does not present any dialog boxes to the user
/t:pathSpecifies the target folder for extracting files
/cExtracts the files without installing them. If /t:path is not specified, you are prompted for a target folder
/c:pathOverride install command defined by author. Specifies the path and name of the Setup.inf or .exe file
/r:nNever restarts the computer after installation.
/r:iPrompts the user to restart the computer if a restart is required, except when used with /q:a
/r:aAlways restarts the computer after installation
/r:sRestarts the computer after installation without prompting the user
/n:vNo 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 required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.

For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Client Deployment Information

  1. Download the client version of this security update.
  2. Click Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
  5. If you are prompted to install the update, click Yes.
  6. Click Yes to accept the License Agreement.
  7. Insert your original source CD-ROM when you are prompted to do so, and then click OK.
  8. When you receive a message that states 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 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 NameVersionDateTimeSize
Winword.exe9.0.0.893010-June-20054:108,831,028

Verifying that the Update Has Been Applied

  • 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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. 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.
    5. 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 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.

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 how the files are extracted from within the security update.

Supported Security Update Installation Switches
SwitchDescription
/?Displays the command-line options
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/t:pathSpecifies the target folder for extracting files
/cExtracts the files without installing them. If /t:path is not specified, you are prompted for a target folder
/c:pathOverride 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, perform the following procedure:

  1. Download the administrative version of this security update.
  2. Click Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, locate the folder that contains the saved file and run the following command line to extract the .msp file:

[path\name of EXE file] /c /t:C:\AdminUpdate

Note  Double-clicking the .exe file does not extract the .msp file it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.

  1. Click Yes to accept the License Agreement.
  2. Click Yes if you are prompted to create the folder.
  3. 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

Where Admin Path is the path of your administrative installation point for your application (for example, C:\Office2000), MSI File is the .msi database package for the application (for example, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp).

Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.

  1. Click Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
  2. Click 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:\Office2000), 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 must be reinstalled for the update. To install all features, you can use REINSTALL=ALL, or you can install the following features.

ProductFeature
Microsoft Word 2000WORDFiles

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization on the Office Admin Update Center. On the home page of that site, look under the Update Strategies section for the software version you are updating. 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 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.

Office 2000:

File NameVersionDateTimeSize
Winword.exe9.0.0.893010-June-20054:108,831,028

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. MBSA 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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. 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.
    5. 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 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

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 or later 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 the following Microsoft Web site: Windows Installer 2.0 for Windows 2000 and Windows NT4.0.
  • Office XP Service Pack 3 (SP3) or Microsoft Works 2002, 2003 or 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.

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

To help reduce the chance that a reboot 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.

Removal Information

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

Automated Client Installation Information

Microsoft Update Web Site

This update will be available through the Microsoft Update Web site for Word 2002 only. Microsoft Update consolidates updates provided by Windows Update and Office Update into one location and enables you to choose automatic delivery and installation of high-priority and security updates. We recommend that you install the Microsoft Office XP client updates by using the Microsoft Update Web site. The Microsoft 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 Microsoft Update Web site detect the required updates that you must install on your computer, visit the Microsoft Update Web site. You will be given the choice of Express (Recommended) or Custom. After detection is complete, you will receive a list of recommended updates for your approval. Click Install Updates or Review and Install Updates 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:

Supported Security Update Installation Switches
SwitchDescription
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted
/q:uSpecifies user-quiet mode, which presents some dialog boxes to the user
/q:aSpecifies administrator-quiet mode, which does not present any dialog boxes to the user
/t:pathSpecifies the target folder for extracting files
/cExtracts the files without installing them. If /t:path is not specified, you are prompted for a target folder
/c:pathOverride install command defined by author. Specifies the path and name of the Setup.inf or .exe file
/r:nNever restarts the computer after installation.
/r:iPrompts the user to restart the computer if a restart is required, except when used with /q:a
/r:aAlways restarts the computer after installation
/r:sRestarts the computer after installation without prompting the user
/n:vNo 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 required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.

For additional information about the supported setup switches, see Microsoft Knowledge Base Article 197147.

Client Deployment Information

  1. Download the client version of this security update.
  2. Click Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file.
  5. If you are prompted to install the update, click Yes.
  6. Click Yes to accept the License Agreement.
  7. Insert your original source CD-ROM when you are prompted to do so, and then click OK.
  8. When you receive a message that states 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 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 NameVersionDateTimeSize
Winword.exe10.00.6764.031-May-20056:1410,635,976

Verifying that the Update Has Been Applied

  • 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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. 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.
    5. 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 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.

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 how the files are extracted from within the security update.

Supported Security Update Installation Switches
SwitchDescription
/?Displays the command-line options
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/t:pathSpecifies the target folder for extracting files
/cExtracts the files without installing them. If /t:path is not specified, you are prompted for a target folder
/c:pathOverride 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, perform the following procedure:

  1. Download the administrative version of this security update.
  2. Click Save this program to disk, and then click OK.
  3. Click Save.
  4. Using Windows Explorer, locate the folder that contains the saved file and run the following command line to extract the .msp file:

[path\name of EXE file] /c /t:C:\AdminUpdate

Note  Double-clicking the .exe file does not extract the .msp file it applies the update to the local computer. In order to update an administrative image, you must first extract the .msp file.

  1. Click Yes to accept the License Agreement.
  2. Click Yes if you are prompted to create the folder.
  3. 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

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, Data1.msi), and MSP File is the name of the administrative update (for example, SHAREDff.msp).

Note You can append /qb+ to the command line so that the Administrative Installation dialog box and the End User License Agreement dialog box do not appear.

  1. Click Next in the provided dialog box. Do not change your CD Key, installation location, or company name in the provided dialog box.
  2. Click 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, Data1.msi), and Feature List is 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.

ProductFeature
Microsoft Word 2002WORDFiles

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization on the Office Admin Update Center. On the home page of that site, look under the Update Strategies section for the software version you are updating. 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 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 NameVersionDateTimeSize
Winword.exe10.0.6764.031-May-20056:1410,635,976

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. MBSA 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.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. 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.
    5. 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 the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Other Information

Acknowledgments

Microsoft thanks the following for working with us to help protect customer:

  • Lord Yup working with iDEFENSE for reporting the Font Parsing Vulnerability in Word - Vulnerability - CAN-2005-0564

Obtaining Other Security Updates:

Updates for other security issues are available at the following locations:

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:

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 by using Software Update Services, visit the Software Update Services Web site.

Windows Server Update Services:

By using Windows Server Update Services (WSUS), administrators can quickly and reliably 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 to Windows 2000 and later operating systems.

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:

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 can 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, visit 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 Analyze, Microsoft Office Detection Tool, and the Enterprise Update Scanning 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, visit 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 (July 12, 2005): Bulletin published

Built at 2014-04-16T02:39:51Z-07:00

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.