__________________________________________________________ The U.S. Department of Energy Computer Incident Advisory Capability ___ __ __ _ ___ / | /_\ / \___ __|__ / \ \___ __________________________________________________________ INFORMATION BULLETIN Vulnerabilities in Microsoft Word [Microsoft Security Bulletin MS06-060 (924554)] October 10, 2006 19:00 GMT Number R-010 [REVISED 19 Oct 2006] ______________________________________________________________________________ PROBLEM: A remote code execution vulnerability exists in Microsoft Word. PLATFORM: Tested Software and Security Update Download Locations: Affected Software: • Microsoft Office 2000 Service Pack 3 • Microsoft Word 2000 • Microsoft Office XP Service Pack 3 • Microsoft Word 2002 • Microsoft Office 2003 Service Pack 1 or Service Pack 2 • Microsoft Office Word 2003 • Microsoft Office Word 2003 Viewer • Microsoft Works Suites: • Microsoft Works Suite 2004 • Microsoft Works Suite 2005 • Microsoft Works Suite 2006 • Microsoft Office 2004 for Mac • Microsoft Office v. X for Mac Storage Management Appliance v2.1 Software running on I, II, III DAMAGE: An attacker cold take complete control of an affected system. SOLUTION: Upgrade to the appropriate version. ______________________________________________________________________________ VULNERABILITY The risk is HIGH. An attacker cold take complete control of an ASSESSMENT: affected system. ______________________________________________________________________________ LINKS: CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/r-010.shtml ORIGINAL BULLETIN: Microsoft Security Bulletin MS06-060 http://www.microsoft.com/technet/security/Bulletin/MS06-060.mspx ADDITIONAL LINK: Visit Hewlett-Packard Subscription Service for: HPSBST02161 SSRT061264 rev. 1 CVE: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name= CVE-2006-3647 CVE-2006-3651 CVE-2006-4534 CVE-2006-4693 ______________________________________________________________________________ REVISION HISTORY: 10/19/2006 - revised R-010 to add a link to Hewlett-Packard HPSBST01261 SSRT061264 rev. 1 for Storage Management Appliance Software v2.1 Software running on I, II, III. [***** Start Microsoft Security Bulletin MS06-060 (924554) *****] Microsoft Security Bulletin MS06-060 Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (924554) Published: October 10, 2006 Version: 1.0 Summary Who Should Read this Document: Customers who use Microsoft Word 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 Office 2000 Service Pack 3 - Download the update (KB920910) • Microsoft Word 2000 • Microsoft Office XP Service Pack 3 - Download the update (KB920817) • Microsoft Word 2002 • Microsoft Office 2003 Service Pack 1 or Service Pack 2 - Download the update (KB923094) • Microsoft Office Word 2003 • Microsoft Office Word 2003 Viewer - Download the update (KB923276) • Microsoft Works Suites: • Microsoft Works Suite 2004 - Download the update (KB920817) (same as the Microsoft Word 2002 update) • Microsoft Works Suite 2005 - Download the update (KB920817) (same as the Microsoft Word 2002 update) • Microsoft Works Suite 2006 - Download the update (KB920817) (same as the Microsoft Word 2002 update) • Microsoft Office 2004 for Mac - Download the update (KB924999) • Microsoft Office v. X for Mac- Download the update (KB924998) 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. Top of section General Information Executive Summary Executive Summary: This update addresses several newly discovered, privately reported and public vulnerabilities. Each vulnerability is documented in this bulletin in its own "Vulnerability Details" section. When using vulnerable versions of Office, if a user were logged on with administrative user rights, an attacker who successfully exploited these vulnerabilities could take complete control of the client workstation. 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 immediately. Severity Ratings and Vulnerability Identifiers: Vulnerability Identifiers Impact of Vulnerability Microsoft Word 2000 Microsoft Word 2002 Microsoft Office Word 2003 or Microsoft Office Word 2003 Microsoft Word 2004 for Mac or Microsoft Word v. X for Mac Microsoft Word Vulnerability - CVE-2006-3647 Remote Code Execution Critical Important Important Important Microsoft Word Mail Merge Vulnerability - CVE-2006-3651 Remote Code Execution Critical Important Important Not applicable Microsoft Word Malformed Stack Vulnerability - CVE-2006-4534 Remote Code Execution Critical Important Important Not applicable Microsoft Word for Mac Vulnerability - CVE-2006-4693 Remote Code Execution Not applicable Not applicable Not applicable Important Aggregate Severity of All Vulnerabilities Critical Important 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. Note The severity ratings for Microsoft Works Suite maps to the Microsoft Word versions as follows: • The Microsoft Works Suite 2004 severity rating is the same as the Microsoft Word 2002 severity rating. • The Microsoft Works Suite 2005 severity rating is the same as the Microsoft Word 2002 severity rating. • The Microsoft Works Suite 2006 severity rating is the same as the Microsoft Word 2002 severity rating. Top of section Frequently Asked Questions (FAQ) Related to This Security Update Why does this update address several reported security vulnerabilities? This update addresses several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers can install only this 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 ID Microsoft Word 2000 Microsoft Word 2002 Microsoft Office Word 2003 Microsoft Word 2004 for Mac or Microsoft Word v. X for Mac MS06-027 Replaced Replaced Replaced Not Applicable Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required? The following table provides the MBSA detection summary for this security update. Software MBSA 1.2.1 MBSA 2.0 Microsoft Word 2000 Yes No Microsoft Word 2002 Yes Yes Microsoft Word 2003 Yes Yes Microsoft Word 2004 for Mac No No Microsoft Word v. X for Mac No No Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this security update. For more information about MBSA, visit the MBSA Web site. For more information about MBSA, visit the MBSA Web site. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660. For more detailed information, see Microsoft Knowledge Base Article 910723. Can I use Systems Management Server (SMS) to determine whether this update is required? The following table provides the SMS detection summary for this security update. Software SMS 2.0 SMS 2003 Microsoft Word 2000 Yes Yes Microsoft Word 2002 Yes Yes Microsoft Word 2003 Yes Yes Microsoft Word 2004 for Mac No No Microsoft Word v. X for Mac No No SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to programs that MBSA does not detect. For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about SMS, visit the SMS Web site. Top of section Vulnerability Details Microsoft Word Vulnerability – CVE-2006-3647: A remote code execution vulnerability exists in Word. An attacker could exploit this vulnerability when Word parsed a file that contains a malformed string. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious web site. Viewing or previewing a malformed e-mail message in Outlook could not lead to exploitation of this vulnerability. If a user were 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 affected than users who operate with administrative user rights. Mitigating Factors for Microsoft Word Vulnerability – CVE-2006-3647: • 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. • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. • 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. • Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003. Top of section Workarounds for Microsoft Word Vulnerability – CVE-2006-3647: 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 in the following section. Do not open or save Microsoft Word files that you receive from untrusted sources or that you received unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a file. Top of section FAQ for Microsoft Word Vulnerability – CVE-2006-3647: What is the scope of the vulnerability? A remote code execution vulnerability exists in Word. An attacker could exploit this vulnerability when Word parses a file that contains a malformed string. If a user were 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 affected than users who operate with administrative user rights. What causes the vulnerability? When Microsoft Word opens a specially crafted Word file, it may corrupt system memory in such a way that an attacker could execute arbitrary code. What might an attacker use the vulnerability to do? An attacker who successfully exploited this vulnerability could take complete control of the affected system. How could an attacker exploit the vulnerability? In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by persuading the user to open the file. In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. What systems are primarily at risk from the vulnerability? Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who have sufficient administrative permissions are given the ability 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 Microsoft Word parses the file and validates the string before it passes the message to the allocated buffer. 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. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations. When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued. Top of section Top of section Microsoft Word Mail Merge Vulnerability - CVE-2006-3651: A remote code execution vulnerability exists in Microsoft Word, and could be exploited when Word opens a specially crafted mail merge file. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious web site. Viewing or previewing a malformed e-mail message in an affected version of Outlook could not lead to exploitation of this vulnerability. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution. If a user were 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 affected than users who operate with administrative user rights. Mitigating Factors for Microsoft Word Mail Merge Vulnerability - CVE-2006-3651: • 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. • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. • 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. • Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003. Top of section Workarounds for Microsoft Word Mail Merge Vulnerability - CVE-2006-3651: Do not open or save Microsoft Word files that you receive from untrusted sources or that you received unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a file. Top of section FAQ for Microsoft Word Mail Merge Vulnerability - CVE-2006-3651: What is the scope of the vulnerability? A remote code execution vulnerability exists in Microsoft Word, and could be exploited when Word opens a specially crafted mail merge file. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious web site. Viewing or previewing a malformed e-mail message in an affected version of Outlook could not lead to exploitation of this vulnerability. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution. If a user were 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 affected than users who operate with administrative user rights. What causes the vulnerability? When Microsoft Word opens a specially crafted Word mail merge file, it may corrupt system memory in such a way that an attacker could execute arbitrary code. What might an attacker use the vulnerability to do? An attacker who successfully exploited this vulnerability could cause arbitrary code to run with the privileges of the user who opened the file. How could an attacker exploit the vulnerability? In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by persuading the user to open the file. In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. What systems are primarily at risk from the vulnerability? Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who have sufficient administrative permissions are given the ability 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 Microsoft Word parses the length of a mail merge record before it passes the message to the allocated buffer. 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. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations. When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued. Top of section Top of section Microsoft Word Malformed Stack Vulnerability - CVE-2006-4534: A remote code execution vulnerability exists in Microsoft Word, and could be exploited when Word opens a specially crafted file. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious web site. Viewing or previewing a malformed e-mail message in an affected version of Outlook could not lead to exploitation of this vulnerability. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution. If a user were 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 affected than users who operate with administrative user rights. Mitigating Factors for Microsoft Word Malformed Stack Vulnerability - CVE-2006-4534: • 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. • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. • 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. • Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and Office 2003. Top of section Workarounds for Microsoft Word Malformed Stack Vulnerability - CVE-2006-4534: Do not open or save Microsoft Word files that you receive from untrusted sources or that you received unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a file. Top of section FAQ for Microsoft Word Malformed Stack Vulnerability - CVE-2006-4534: What is the scope of the vulnerability? A remote code execution vulnerability exists in Microsoft Word, and could be exploited when Word opens a specially crafted file. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious web site. Viewing or previewing a malformed e-mail message in an affected version of Outlook could not lead to exploitation of this vulnerability. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution. If a user were 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 affected than users who operate with administrative user rights. What causes the vulnerability? When Microsoft Word opens a specially crafted Word file, it may corrupt system memory in such a way that an attacker could execute arbitrary code. What might an attacker use the vulnerability to do? An attacker who successfully exploited this vulnerability could cause arbitrary code to run with the privileges of the user who opened the file. How could an attacker exploit the vulnerability? In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by persuading the user to open the file. In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. What systems are primarily at risk from the vulnerability? Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who have sufficient administrative permissions are given the ability 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 Microsoft Word parses the length of a record before it passes the message 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 CVE-2006-4534. 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 that has been 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-2006-4534. Top of section Top of section Microsoft Word for Mac Vulnerability - CVE-2006-4693: A remote code execution vulnerability exists in Word for Mac. An attacker could exploit this vulnerability when Word for Mac parses a specially crafted file that contains a malformed string. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious web site. Viewing or previewing a malformed e-mail message in Outlook could not lead to exploitation of this vulnerability. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution. If a user were 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 affected than users who operate with administrative user rights. Mitigating Factors for Microsoft Word for Mac Vulnerability - CVE-2006-4693: • 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. • In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. • 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. Top of section Workarounds for Microsoft Word for Mac Vulnerability - CVE-2006-4693: Do not open or save Microsoft Word files that you receive from untrusted sources or that you received unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a file. Top of section FAQ for Microsoft Word for Mac Vulnerability - CVE-2006-4693: What is the scope of the vulnerability? A remote code execution vulnerability exists in Word for Mac. An attacker could exploit this vulnerability when Word for Mac parses a file that contains a malformed string. If a user were 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 affected than users who operate with administrative user rights. What causes the vulnerability? When Microsoft Word for Mac opens a specially crafted Word file, it may corrupt system memory in such a way that an attacker could execute arbitrary code. What might an attacker use the vulnerability to do? An attacker who successfully exploited this vulnerability could take complete control of the affected system. How could an attacker exploit the vulnerability? In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially-crafted file to the user and by persuading the user to open the file. In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site. What systems are primarily at risk from the vulnerability? Workstations are primarily at risk. Servers could be at more risk if users who have sufficient administrative permissions are given the ability 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 Microsoft Word for Mac parses the file and validates the string. 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. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations. When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited? No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued. Top of section Top of section Top of section Security Update Information 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 must be installed. Microsoft Windows Server 2003, Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) 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 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 2000 Service Pack 3 (SP3) must be installed. Before you install this update, install Office 2000 SP3. For more information about how to install Office 2000 SP3, see Microsoft Knowledge Base Article 326585. For more information about how to determine the version of Office 2000 that is installed on your computer, see Microsoft Knowledge Base Article 255275. Inclusion in Future Service Packs None. Service Pack 3 is the last service pack for Office 2000. Restart Requirement To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. 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. Top of section 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 which installation you have 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 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. Top of section Manual Client Installation Information For detailed information about how to manually install this update, review the following section. Installation Information The security update supports the following setup switches. Supported Security Update Installation 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 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 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 more information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Note The full file office update is intended for both client and administrative deployment scenarios. Client Deployment Information 1. Download this security update for Word 2000. 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 Name Version Date Time Size Winword.exe 9.0.0.8951 08-Sep-2006 18:53 8,831,028 Verifying that the Update Has Been Applied • Microsoft Baseline Security Analyzer Note MBSA 1.2.1 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 the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A 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. Top of section 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 the security update. Supported Security Update Installation Switches 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 Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Administrative Deployment Information To update your administrative installation, follow these steps: 1. Download this security update for Word 2000. 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. Click Start, click Run, type the following command, and then click OK 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. 5. Click Yes to accept the License Agreement. 6. Click Yes if you are prompted to create the folder. 7. If you are familiar with the procedure for updating your administrative installation, click Start, click Run, type the following command, and then click OK: msiexec /a Admin Path\MSI File /p C:\AdminUpdate\MSP File SHORTFILENAMES=TRUE Note 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. 8. Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box. 9. 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 configurations that were originally installed from this administrative installation. To do this, please review the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update. Warning Any workstation configuration 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 Information” section for this workstation. Workstation Deployment Information To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK: msiexec /I Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu Note 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. Product Feature O9PRM, O9PRO, O9SBE, O9PIPC1, O9PIPC2, O9STD, O9WDI, O9WRD WORDFiles Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer. 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 2000: File Name Version Date Time Size Winword.exe 9.0.0.8951 08-Sep-2006 18:53 8,831,028 Verifying that the Update Has Been Applied • Microsoft Baseline Security Analyzer Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this security update. For more information about MBSA, visit the MBSA 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. Top of section Top of section 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 must be installed. Microsoft Windows Server 2003, Windows XP, and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. 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) must be installed. Before you install this update, install Office XP SP3. For more information about how to install Office XP SP3, see Microsoft Knowledge Base Article 832671. For more information about how to determine the version of Office XP that is installed on your computer, see Microsoft Knowledge Base Article 291331. For more information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294. Inclusion in Future Service Packs None. Service Pack 3 is the last service pack for Office XP. Restart Requirement To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. 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. Note For Project 2002 Service Pack 1 and Visio 2002 Service Pack 2, 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. Top of section Automated Client Installation Information Microsoft Update Web Site This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates that are provided by Windows Update and Office Update into one location and lets you choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update 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. Top of section Manual Client Installation Information For detailed information about how to manually install this update, review the following section. Installation Information The security update supports the following setup switches. Supported Security Update Installation 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 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 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 more information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Note The full file office update is intended for both client and administrative deployment scenarios. Client Deployment Information 1. Download this security update for Word 2002. 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 see 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 Name Version Date Time Size Winword.exe 10.0.6818.0 09-Sep-2006 03:56 10,738,448 Top of section 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 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 Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Administrative Deployment Information To update your administrative installation, follow these steps: 1. Download this security update for Word 2002. 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. Click Start, click Run, type the following command, and then click OK 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. 5. Click Yes to accept the License Agreement. 6. Click Yes if you are prompted to create the folder. 7. If you are familiar with the procedure for updating your administrative installation, click Start, click Run, type the following command, and then click OK: msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE Note 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 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. 8. Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box. 9. 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 workstation configurations that were originally installed from this administrative installation. To do this, see the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update. Warning Any workstation configuration 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 Information” section for this workstation. Workstation Deployment Information To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK: msiexec /I Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu Note 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. 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 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 more 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 Name Version Date Time Size Winword.exe 10.0.6818.0 09-Sep-2006 03:56 10,738,448 Verifying that the Update Has Been Applied • Microsoft Baseline Security Analyzer Note MBSA 1.2.1 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 the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A 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. Top of section Top of section Word 2003 Prerequisites and Additional Update Details Important: Before you install this update, make sure that the following requirements have been met: • To update Office 2003, Office 2003 Service Pack 1 or Office 2003 Service Pack 2 must be installed. Before you install this update, install Office 2003 SP1 or Office 2003 SP2. • To update Word Viewer 2003, the latest version of Word 2003 Viewer must be installed. Download the lasted Word 2003 Viewer. For more information about how to determine the version of Office 2003 that is installed on your computer, see Microsoft Knowledge Base Article 821549. For more information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294. 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 restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012. Removal Information To remove this security update, use Add or Remove Programs 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 Add or Remove Programs in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771. Top of section Automated Client Installation Information Microsoft Update Web Site This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates that are provided by Windows Update and Office Update into one location and lets you choose automatic delivery and installation of high-priority and security updates. We recommend that you install this update 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. Top of section Manual Client Installation Information For detailed information about how to manually install this update, review the following section. Installation Information The security update supports the following setup switches. Supported Security Update Installation 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 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 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 more information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Note The full file office update is intended for both client and administrative deployment scenarios. Client Deployment Information 1. Download the security update for Word 2003 and/or Word Viewer 2003. 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 2003: File Name Version Date Time Size Winword.exe 11.0.8106 02-Sep-2006 00:35 12,259,088 Word Viewer 2003 File Name Version Date Time Size Wordview.exe 11.0.8104.0 17-Aug-2006 22:57 6,959,888 Top of section 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 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 Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. For more information about the supported setup switches, see Microsoft Knowledge Base Article 197147. Administrative Deployment Information To update your administrative installation, follow these steps: 1. Download the security update for Word 2003 and/or Word Viewer 2003. 2. 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. Click Start, click Run, type the following command, and then click OK 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. 5. Click Yes to accept the License Agreement. 6. Click Yes if you are prompted to create the folder. 7. If you are familiar with the procedure for updating your administrative installation, click Start, click Run, type the following command, and then click OK: msiexec /a Admin Path\MSI File /p C:\adminUpdate\MSP File SHORTFILENAMES=TRUE Note 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. 8. Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box. 9. 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 configurations that were originally installed from this administrative installation. To do this, please review the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update. Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions such as repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section. Workstation Deployment Information To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK: Msiexec /I Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu Note 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 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. Product Feature STD11, BASIC11, PERS11, PROI11, PRO11, STDP11, WORD11, PRO11SB WORDFiles Word 2003 Viewer WORDVIEWFiles 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 more 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 2003: File Name Version Date Time Size Winword.exe 11.0.8106 02-Sep-2006 00:35 12,259,088 Word Viewer 2003 File Name Version Date Time Size Wordview.exe 11.0.8104.0 17-Aug-2006 22:57 6,959,888 Verifying that the Update Has Been Applied • Microsoft Baseline Security Analyzer Note MBSA 1.2.1 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 the MBSA Web site. For more information about MBSA support, visit the following Microsoft Baseline Security Analyzer 1.2 Q&A 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. Top of section Top of section Office 2004 for Mac Installation Information Restart Requirement This update does not require you to restart your computer. Removal Information This update cannot be uninstalled. Installation Information: 1. Quit any applications that are running, including virus-protection applications, all Microsoft Office applications, Microsoft Messenger for Mac, and Office Notifications, because they might interfere with installation. 2. Open the Microsoft Office 2004 for Mac 11.3.0 Update volume on your desktop. This step might have been performed for you. 3. To start the update process, in the Microsoft Office 2004 for Mac 11.3.0 Update volume window, double-click the Microsoft Office 2004 for Mac 11.3.0 Update application, and follow the instructions on the screen. 4. If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the “Verifying Update Installation” section. To remove the update installer, first drag the Microsoft Office 2004 for Mac 11.3.0 Update volume to the Trash, and then drag the file that you downloaded to the Trash. Verifying Update Installation To verify that a security update is installed on an affected system, follow these steps: 1. In the Finder, navigate to the Application Folder (Microsoft Office 2004: Office). 2. Select the file, Microsoft Component Plugin. 3. On the File menu click Get Info or Show Info. If the Version number is 11.3.0, the update has been successfully installed. Top of section Office v. X for Mac Installation Information: 1. Quit any applications that are running, including virus-protection applications, all Microsoft Office applications, Microsoft Messenger, and Office Notifications, because they might interfere with installation. 2. Open the Microsoft Office v. X for Mac 10.1.8 Update volume on your desktop. This step might have been performed for you 3. To start the update process, in the Microsoft Office v. X for Mac 10.1.8 Update volume window, double-click the Microsoft Office v. X for Mac 10.1.8Update application, and follow the instructions on the screen. 4. If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the “Verifying Update Installation” section. To remove the update installer, first drag the Microsoft Office v. X for Mac 10.1.8 Update volume to the Trash, and then drag the file that you downloaded to the Trash Restart Requirement This update does not require you to restart your computer. Removal Information This update cannot be uninstalled. Verifying Update Installation To verify that a security update is installed on an affected system, follow these steps: 1. In the Finder, navigate to the Application Folder (Microsoft Office X: Office). 2. Select the file, Microsoft Component Plugin. 3. On the File menu click Get Info or Show Info. If the Version number is 10.1.8, the update has been successfully installed. Top of section Top of section Acknowledgments Microsoft thanks the following for working with us to help protect customers: • Chen Xiaobo of McAfee Avert Labs for reporting the Microsoft Word Vulnerability - CVE-2006-3647. • Cu Fang for reporting the Microsoft Office Mail Merge Vulnerability - CVE-2006-3651. • Cu Fang for reporting the Microsoft Word for Mac Vulnerability - CVE-2006-4693. Obtaining Other Security Updates: Updates for other security issues are available at the following locations: • Security updates are available at the Microsoft Download Center. You can find them most easily by doing a keyword search for "security_patch." • Updates for consumer platforms are available at the Microsoft 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. • TechNet Update Management Center • Microsoft Software Update Services • Microsoft Windows Server Update Services • Microsoft Baseline Security Analyzer (MBSA) • Windows Update • Microsoft 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 security updates 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 onto Windows 2000 and later operating systems. For more information about how to deploy security updates 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 Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scan 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 (October 10, 2006): Bulletin published. [***** End Microsoft Security Bulletin MS06-060 (924554) *****] _______________________________________________________________________________ CIAC wishes to acknowledge the contributions of Microsoft for the information contained in this bulletin. _______________________________________________________________________________ CIAC, the Computer Incident Advisory Capability, is the computer security incident response team for the U.S. Department of Energy (DOE) and the emergency backup response team for the National Institutes of Health (NIH). CIAC is located at the Lawrence Livermore National Laboratory in Livermore, California. CIAC is also a founding member of FIRST, the Forum of Incident Response and Security Teams, a global organization established to foster cooperation and coordination among computer security teams worldwide. CIAC services are available to DOE, DOE contractors, and the NIH. CIAC can be contacted at: Voice: +1 925-422-8193 (7x24) FAX: +1 925-423-8002 STU-III: +1 925-423-2604 E-mail: ciac@ciac.org Previous CIAC notices, anti-virus software, and other information are available from the CIAC Computer Security Archive. World Wide Web: http://www.ciac.org/ Anonymous FTP: ftp.ciac.org PLEASE NOTE: Many users outside of the DOE, ESnet, and NIH computing communities receive CIAC bulletins. If you are not part of these communities, please contact your agency's response team to report incidents. Your agency's team will coordinate with CIAC. The Forum of Incident Response and Security Teams (FIRST) is a world-wide organization. A list of FIRST member organizations and their constituencies can be obtained via WWW at http://www.first.org/. This document was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation or favoring by the United States Government or the University of California. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product endorsement purposes. LAST 10 CIAC BULLETINS ISSUED (Previous bulletins available from CIAC) Q-327: Exploits of MDAC (MS06-014) Vulnerability in the Wild R-001: OpenSSL Security Advisory R-002: HP-UX running SLP, Remote Unauthorized Access R-003: HP-UX Running Ignite-UX Server R-004: Mac OS X 10.4.8 Security Update R-005: xfree86 Several Vulnerabilities R-006: Python Security Update R-007: Vulnerability in Windows Explorer R-008: Vulnerabilities in Microsoft PowerPoint R-009: Vulnerabilities in Microsoft Excel