Security Bulletin

Microsoft Security Bulletin MS08-042 - Important

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

Published: August 12, 2008

Version: 1.0

General Information

Executive Summary

This security update resolves a publicly reported vulnerability in Microsoft Word. This vulnerability could allow remote code execution if a user opens a specially crafted Word file. 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.

This security update is rated Important for supported editions of Microsoft Word 2002 and Microsoft Word 2003. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerability by modifying the way that Microsoft Word handles specially crafted Word files. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

This security update also addresses the vulnerability first described in Microsoft Security Advisory 953635.

Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. None

Affected and Non-Affected Software

The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.

Affected Software

Office Suite and Other Software Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Microsoft Office Suites and Components
Microsoft Office XP Service Pack 3 [Microsoft Word 2002 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=c7146dfc-e1be-4d13-877b-1d9bcacc4a64) (KB954463) Remote Code Execution Important [MS08-026](http://go.microsoft.com/fwlink/?linkid=117295)
Microsoft Office 2003 Service Pack 2 [Microsoft Word 2003 Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=13a37b76-9fec-426f-8176-3c95f934efe0) (KB954464) Remote Code Execution Important [MS08-026](http://go.microsoft.com/fwlink/?linkid=117295)
Microsoft Office 2003 Service Pack 3 [Microsoft Word 2003 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=13a37b76-9fec-426f-8176-3c95f934efe0) (KB954464) Remote Code Execution Important [MS08-026](http://go.microsoft.com/fwlink/?linkid=117295)
**Non-Affected Software**
Office and Other Software Component
Microsoft Office 2000 Service Pack 3 Microsoft Word 2000 Service Pack 3
2007 Microsoft Office System Microsoft Word 2007
2007 Microsoft Office System Service Pack 1 Microsoft Word 2007 Service Pack 1
Microsoft Word Viewer 2003
Microsoft Word Viewer 2003 Service Pack 3
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1
Microsoft Works 8.0
Microsoft Works 8.5
Microsoft Works 9.0
Microsoft Works Suite 2005
Microsoft Works Suite 2006
Microsoft Office 2004 for Mac
Microsoft Office 2008 for Mac

Where are the file information details?
The file information details can be found in Microsoft Knowledge Base Article 955048.

I use Microsoft Office 2003 Service Pack 2. Are any additional security features included in this update?
Yes, as part of the servicing model for Microsoft Office 2003, when users of Microsoft Office 2003 Service Pack 2 install this update, their systems will be upgraded to security functionality that was initially released with Microsoft Office 2003 Service Pack 3. All updates released after January 1, 2008 for Microsoft Office 2003 Service Pack 2 will include these security features, which were introduced in Microsoft Office 2003 Service Pack 3. We have thoroughly tested this update, but as with all updates, we recommend that users perform testing appropriate to the environment and configuration of their systems. For more information on this issue, please see Microsoft Knowledge Base Article 951646.

I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. To determine the support life cycle for your software release, visit Microsoft Support Lifecycle.

It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit Microsoft Support Lifecycle. For more information about the extended security update support period for these software versions or editions, visit Microsoft Product Support Services.

Customers who require custom support for older releases must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit Microsoft Worldwide Information, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Windows Operating System Product Support Lifecycle FAQ.

The Office component discussed in this article is part of the Office Suite that I have installed on my system; however, I did not choose to install this specific component. Will I be offered this update?
Yes, if the version of the Office Suite installed on your system shipped with the component discussed in this bulletin, the system will be offered updates for it whether the component is installed or not. The detection logic used to scan for affected systems is designed to check for updates for all components that shipped with the particular Office Suite and offer the updates to a system. Users who choose not to apply an update for a component that is not installed, but is included in the version of the Office Suite, will not increase the security risk of that system. However, users who do choose to install the update will not have a negative impact on the security or performance of a system. For more information on this issue, please see Microsoft Knowledge Base Article 830335.

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

Affected Software Word Record Parsing Vulnerability - CVE-2008-2244 Aggregate Severity Rating
Microsoft Word 2002 Service Pack 3 Important
Remote Code Execution
Important
Microsoft Word 2003 Service Pack 2 Important
Remote Code Execution
Important
Microsoft Word 2003 Service Pack 3 Important
Remote Code Execution
Important
Word Record Parsing Vulnerability - CVE-2008-2244 ------------------------------------------------- A remote code execution vulnerability exists in the way that Microsoft Word handles specially crafted Word files. The vulnerability could allow remote code execution if a user opens a specially crafted Word file that includes a malformed record value. 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. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2008-2244](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2008-2244). #### Mitigating Factors for Word Record Parsing Vulnerability - CVE-2008-2244 Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation: - The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message. - In a Web-based attack scenario, a Web site could contain a Word file that is used to exploit this vulnerability. An attacker would have to convince users to visit the Web site and open a specially crafted Word file, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site, and then convincing them to open the specially crafted Word file. - An attacker who successfully exploited this vulnerability could gain the same user rights as the local user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. #### Workarounds for Word Record Parsing Vulnerability - CVE-2008-2244 Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality - Use [Microsoft Office Word 2003 Viewer](http://www.microsoft.com/downloads/details.aspx?familyid=95e24c87-8732-48d5-8689-ab826e7b8fdf&displaylang=en) or [Microsoft Office Word 2003 Viewer Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=c6e56e97-17d7-4c48-9b2e-474cb3cdcc45&displaylang=en) to open and view Microsoft Word files. - Do not open or save Microsoft Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file. #### FAQ for Word Record Parsing Vulnerability - CVE-2008-2244 **What is the scope of the vulnerability?** This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. **What causes the vulnerability?**  The vulnerability is caused by a memory handling error when parsing record values in a specially crafted Word file. The error may corrupt system memory in such a way that an attacker could execute arbitrary code. **What might an attacker use the vulnerability to do?**  An attacker who successfully exploited this vulnerability could take complete control of an affected system. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. **How could an attacker exploit the vulnerability?**  This vulnerability requires that a user open a specially crafted Word file with an affected version of Microsoft Word. In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Word file to the user and by convincing the user to open the file. In a Web-based attack scenario, a Web site could contain a Word file that is used to exploit this vulnerability. An attacker would have to convince users to visit the Web site and open a specially crafted Word file, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site, and then convincing them to open the specially crafted Word file. **What systems are primarily at risk from the vulnerability?**  Systems where Microsoft Word is used, including workstations and terminal servers, are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this. **What does the update do?**  The update removes the vulnerability by modifying the way that Word initializes memory in processing record values when opening Word files. **When this security bulletin was issued, had this vulnerability been publicly disclosed?** Yes. This vulnerability had been publicly disclosed when this security bulletin was originally issued. It has been assigned the Common Vulnerability and Exposure number [CVE-2008-2244](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2008-2244). This vulnerability was first described in [Microsoft Security Advisory 953635](http://technet.microsoft.com/security/advisory/953635). **When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?**  Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited. **Does applying this security update help protect customers from the code, published publicly, that attempts to exploit this vulnerability?**  Yes. This security update addresses the vulnerability that is currently being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number [CVE-2008-2244](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2008-2244). ### Update Information Detection and Deployment Tools and Guidance ------------------------------------------- Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the [TechNet Update Management Center](http://go.microsoft.com/fwlink/?linkid=69903). The [Microsoft TechNet Security Web site](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products. Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747), [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130), and [Office Update](http://go.microsoft.com/fwlink/?linkid=21135). Security updates are also available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129). You can find them most easily by doing a keyword search for "security update." Finally, security updates can be downloaded from the [Microsoft Update Catalog](http://go.microsoft.com/fwlink/?linkid=96155). The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, “MS07-036”), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the [Microsoft Update Catalog FAQ](http://go.microsoft.com/fwlink/?linkid=97900). **Detection and Deployment Guidance** Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/910723). **Microsoft Baseline Security Analyzer** Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit [Microsoft Baseline Security Analyzer](http://www.microsoft.com/technet/security/tools/mbsahome.mspx). The following table provides the MBSA detection summary for this security update. | Software | MBSA 2.1 | |------------------------------------|----------| | Microsoft Word 2002 Service Pack 3 | Yes | | Microsoft Word 2003 Service Pack 2 | Yes | | Microsoft Word 2003 Service Pack 3 | Yes | For more information about MBSA 2.1, see [MBSA 2.1 Frequently Asked Questions](http://www.microsoft.com/technet/security/tools/mbsa2/qa.mspx). **Note** For customers using legacy software not supported by MBSA 2.1, Microsoft Update, and Windows Server Update Services: please visit [Microsoft Baseline Security Analyzer](http://www.microsoft.com/technet/security/tools/mbsahome.mspx) and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools. **Windows Server Update Services** By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. For more information about how to deploy this security update using Windows Server Update Services, visit the [Windows Server Update Services Web site](http://go.microsoft.com/fwlink/?linkid=50120). **Systems Management Server** The following table provides the SMS detection and deployment summary for this security update. | Software | SMS 2.0 | SMS 2003 with SUSFP | SMS 2003 with ITMU | Configuration Manager 2007 | |------------------------------------|---------|---------------------|--------------------|----------------------------| | Microsoft Word 2002 Service Pack 3 | Yes | Yes | Yes | Yes | | Microsoft Word 2003 Service Pack 2 | Yes | Yes | Yes | Yes | | Microsoft Word 2003 Service Pack 3 | Yes | Yes | Yes | Yes | For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also [Downloads for Systems Management Server 2.0](http://technet.microsoft.com/en-us/sms/bb676799.aspx). For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by [Microsoft Update](http://update.microsoft.com/microsoftupdate) and that are supported by [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). For more information about the SMS 2003 ITMU, see [SMS 2003 Inventory Tool for Microsoft Updates](http://technet.microsoft.com/en-us/sms/bb676783.aspx). SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see [SMS 2003 Software Update Scanning Tools](http://technet.microsoft.com/en-us/sms/bb676786.aspx). See also [Downloads for Systems Management Server 2003](http://technet.microsoft.com/en-us/sms/bb676766.aspx). System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit [System Center Configuration Manager 2007](http://technet.microsoft.com/en-us/library/bb735860.aspx). For more information about SMS, visit the [SMS Web site](http://go.microsoft.com/fwlink/?linkid=21158). For more detailed information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/910723): Summary list of monthly detection and deployment guidance articles. **Note** If you have used an Administrative Installation Point (AIP) for deploying Office 2000, Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline. For more information, see the **Office Administrative Installation Point** heading in this section. **Office Administrative Installation Point** If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your system. - For supported versions of Microsoft Office 2000, see [How to Create an Administrative Installation Point](http://office.microsoft.com/en-us/ork2000/ha011380221033.aspx). For more information about how to change the source for a client system from an updated administrative installation point to an Office 2000 Service Pack 3 (SP3), see [Microsoft Knowledge Base Article 932889](http://support.microsoft.com/kb/932889). **Note** If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article [Updating Office 2000 Clients from a Patched Administrative Image](http://office.microsoft.com/en-us/ork2000/ha011525661033.aspx?pid=ch102053491033). - For supported versions of Microsoft Office XP, see [Creating an Administrative Installation Point](http://office.microsoft.com/en-us/orkxp/ha011363091033.aspx). For more information on how to change the source for a client system from an updated administrative installation point to an Office XP original baseline source, see [Microsoft Knowledge Base Article 922665](http://support.microsoft.com/kb/922665). **Note** If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article [Updating Office XP Clients from a Patched Administrative Image](http://office.microsoft.com/en-us/orkxp/ha011525721033.aspx). - For supported versions of Microsoft Office 2003, see [Creating an Administrative Installation Point](http://office.microsoft.com/en-us/ork2003/ha011401931033.aspx). For more information on how to change the source for a client computer from an updated administrative installation point to an Office 2003 original baseline source or Service Pack 2 (SP2), see [Microsoft Knowledge Base Article 902349](http://support.microsoft.com/kb/902349). **Note** If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article, [Distributing Office 2003 Product Upgrades](http://office.microsoft.com/en-us/ork2003/ha011402381033.aspx?pid=ch011480761033). - For supported versions of the 2007 Microsoft Office system, see [Create a network installation point for the 2007 Office system](http://technet2.microsoft.com/office/f/?en-us/library/72c9ae03-1342-4524-8242-1524fbd068a51033.mspx). **Note** If you plan to manage security updates centrally, use Windows Server Update Services. For more information about how to deploy security updates for the 2007 Microsoft Office system using Windows Server Update Services, visit the [Windows Server Update Services Web site](http://go.microsoft.com/fwlink/?linkid=50120). **Update Compatibility Evaluator and Application Compatibility Toolkit** Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the [Update Compatibility Evaluator](http://technet2.microsoft.com/windowsvista/en/library/4279e239-37a4-44aa-aec5-4e70fe39f9de1033.mspx?mfr=true) components included with [Application Compatibility Toolkit 5.0](http://www.microsoft.com/downloads/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en). The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment. Security Update Deployment -------------------------- **Affected Software** For information about the specific security update for your affected software, click the appropriate link: #### Word 2002 **Reference Table** The following table contains the security update information for this software. You can find additional information in the subsection, **Deployment Information**, in this section.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user intervention officexp-kb954463-fullfile-enu /q:a
Installing without restarting officexp-kb954463-fullfile-enu /r:n
Update log file Not applicable
Further information For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required? This update does not require a restart.
Hotpatching Not applicable
Removal Information Use Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office XP CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
File Information See Microsoft Knowledge Base Article 955048
Registry Key Verification Not applicable
#### Office Features The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use **REINSTALL=ALL** or you can install the following features: | Product | Feature | |---------------------------------------------|-----------| | PIPC1, PROPLUS, PRO, SBE, STD, STDEDU, WORD | WORDFiles | **Note** Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the **Update Resources** section for the software version you are updating. The [Windows Installer Documentation](http://go.microsoft.com/fwlink/?linkid=21685) also provides more information about the parameters supported by Windows Installer. #### Deployment Information **Installing the Update** You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the **Office Administrative Installation Point** information in the **Detection and deployment Tools and Guidance** subsection. This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit one of the following Microsoft Web sites: - [Windows Installer 3.1 Redistributable](http://www.microsoft.com/downloads/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en) - [Windows Installer 2.0 Redistributable for Windows 2000 and Windows NT 4.0](http://go.microsoft.com/fwlink/?linkid=33338) - [Windows Installer 2.0 Redistributable for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition](http://go.microsoft.com/fwlink/?linkid=33337) For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684). This security update supports the following setup switches. | Switch | Description | |-------------|---------------------------------------------------------------------------------------------------------------------| | **/q** | Specifies quiet mode, or suppresses prompts, when files are being extracted. | | **/q:u** | Specifies user-quiet mode, which presents some dialog boxes to the user. | | **/q:a** | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. | | **/t:path** | Specifies the target folder for extracting files. | | **/c** | Extracts the files without installing them. If **/t:path** is not specified, you are prompted for a target folder. | | **/c:path** | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. | | **/r:n** | Never restarts the system after installation. | | **/r:I** | Prompts the user to restart the system if a restart is required, except when used with **/q:a**. | | **/r:a** | Always restarts the system after installation. | | **/r:s** | Restarts the system after installation without prompting the user. | | **/n:v** | No version checking - Install the program over any earlier version. | **Note** You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841). **Removing the Update** To remove this security update, use the Add or Remove Programs tool in Control Panel. **Note** When you remove this update, you may be prompted to insert the Microsoft Office XP CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see [Microsoft Knowledge Base Article 903771](http://support.microsoft.com/kb/903771). **Verifying That the Update Has Been Applied** - **Microsoft Baseline Security Analyzer** To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the “Microsoft Baseline Security Analyzer” heading under the section, **Detection and Deployment Tools and Guidance,** earlier in this bulletin for more information. - **File Version Verification** Because there are several versions and editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 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 system by comparing it to the version that is documented in the appropriate file information table. **Note** Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. #### Word 2003 (all editions) **Reference Table** The following table contains the security update information for this software. You can find additional information in the subsection, **Deployment Information**, in this section.

Inclusion in Future Service Packs There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user intervention office2003-kb954464-fullfile-enu /q:a
Installing without restarting office2003-kb954464-fullfile-enu /r:n
Update log file Not applicable
Further information For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.

For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required? This update does not require a restart.
Hotpatching Not applicable
Removal Information Use Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
File Information See Microsoft Knowledge Base Article 955048
Registry Key Verification Not applicable
#### Office Features The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use **REINSTALL=ALL** or you can install the following features: | Product | Feature | |----------------------------------------------------------------|-----------| | BASIC11, PERS11, PRO11SB, PROI11, PRO11, STDP11, STD11, WORD11 | WORDFiles | **Note** Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the **Update Resources** section for the software version you are updating. The [Windows Installer Documentation](http://go.microsoft.com/fwlink/?linkid=21685) also provides more information about the parameters supported by Windows Installer. #### Deployment Information **Installing the Update** You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the **Office Administrative Installation Point** information in the **Detection and deployment Tools and Guidance** subsection. This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit one of the following Microsoft Web sites: - [Windows Installer 3.1 Redistributable](http://www.microsoft.com/downloads/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en) - [Windows Installer 2.0 Redistributable for Windows 2000 and Windows NT 4.0](http://go.microsoft.com/fwlink/?linkid=33338) - [Windows Installer 2.0 Redistributable for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition](http://go.microsoft.com/fwlink/?linkid=33337) For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684). This security update supports the following setup switches. | Switch | Description | |-------------|---------------------------------------------------------------------------------------------------------------------| | **/q** | Specifies quiet mode, or suppresses prompts, when files are being extracted. | | **/q:u** | Specifies user-quiet mode, which presents some dialog boxes to the user. | | **/q:a** | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. | | **/t:path** | Specifies the target folder for extracting files. | | **/c** | Extracts the files without installing them. If **/t:path** is not specified, you are prompted for a target folder. | | **/c:path** | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. | | **/r:n** | Never restarts the system after installation. | | **/r:I** | Prompts the user to restart the system if a restart is required, except when used with **/q:a**. | | **/r:a** | Always restarts the system after installation. | | **/r:s** | Restarts the system after installation without prompting the user. | | **/n:v** | No version checking - Install the program over any earlier version. | **Note** You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841). **Removing the Update** To remove this security update, use the Add or Remove Programs tool in Control Panel. **Note** When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see [Microsoft Knowledge Base Article 903771](http://support.microsoft.com/kb/903771). **Verifying that the Update Has Been Applied** - **Microsoft Baseline Security Analyzer** To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the “Microsoft Baseline Security Analyzer” heading under the section, **Detection and Deployment Tools and Guidance,** earlier in this bulletin for more information. - **File Version Verification** Because there are several versions and editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 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 system by comparing it to the version that is documented in the appropriate file information table. **Note** Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. ### Other Information #### Acknowledgments Microsoft [thanks](http://go.microsoft.com/fwlink/?linkid=21127) the following for working with us to help protect customers: - [ISC/SANS](http://isc.sans.org/) for reporting the Word Record Parsing Vulnerability (CVE-2008-2244). #### Support - Customers in the U.S. and Canada can receive technical support from [Microsoft Product Support Services](http://go.microsoft.com/fwlink/?linkid=21131) 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](http://go.microsoft.com/fwlink/?linkid=21155). #### 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 (August 12, 2008): Bulletin published. *Built at 2014-04-18T13:49:36Z-07:00*