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

Microsoft Security Bulletin MS07-014 - Critical

Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (929434)

Published: February 13, 2007

Version: 1.0

Summary

Who Should Read this Document: Customers who use Microsoft Office or Microsoft Works

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:

Non-Affected Software:

  • 2007 Microsoft Office System
    • Microsoft Office Word 2007

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

General Information

Executive Summary:

This update resolves several newly discovered, privately and publicly reported vulnerabilities. Each vulnerability is documented in its own subsection in the "Vulnerability Details" section of this bulletin.

If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

We recommend that customers apply the update immediately.

Severity Ratings and Vulnerability Identifiers:

Vulnerability IdentifiersImpact of VulnerabilityMicrosoft Word 2000 Microsoft Word 2002 Microsoft Word 2003 Microsoft Office 2004 for MacMicrosoft Word Viewer 2003
Word Malformed String Vulnerability - CVE-2006-5994Remote Code Execution
CriticalImportantImportantImportantNone
Word Malformed Data Structures Vulnerability - CVE-2006-6456Remote Code Execution
Critical
ImportantImportantImportantImportant
Word Count Vulnerability – CVE-2006-6561Remote Code Execution
CriticalImportantImportantImportantImportant
Word Macro Vulnerability – CVE-2007-0208Remote Code ExecutionNoneImportantImportantImportantNone
Word Malformed Drawing Object Vulnerability - CVE-2007-0209Remote Code ExecutionCriticalImportantNoneImportantNone
Word Malformed Function Vulnerability - CVE-CVE-2007-0515 Remote Code ExecutionCriticalNoneNoneImportantNone
Aggregate Severity of All Vulnerabilities   Critical Important 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, 2005, and 2006 severity rating is the same as the Microsoft Word 2002 severity rating.

Why does this update address several reported security vulnerabilities?
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers 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 IDMicrosoft Word 2000 Microsoft Word 2002Microsoft Word 2003Microsoft Office 2004 for MacMicrosoft Word Viewer 2003
MS06-060 ReplacedReplacedReplacedReplacedReplaced

Note Microsoft Word 2002 replacement also replaces Microsoft Works Suite 2004, 2005, and 2006.

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.

SoftwareMBSA 1.2.1MBSA 2.0
Microsoft Word 2000YesNo
Microsoft Word XPYesYes
Microsoft Word 2003YesYes
Microsoft Word Viewer 2003YesYes
Microsoft Office 2004 for MacNoNo

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.

Note Microsoft Works 2004, 2005 and 2006 updates are the same as the Microsoft Word 2002 update.

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.

SoftwareSMS 2.0SMS 2003
Microsoft Word 2000YesNo
Microsoft Word 2002YesYes
Microsoft Word 2003YesYes
Microsoft Word Viewer 2003YesYes
Microsoft Word v.X for MacNoNo
Microsoft Word 2004 for MacNoNo

SMS 2.0 and SMS 2003 Software Update Services (SUS) Feature Pack can use MBSA 1.2.1 for detection and therefore have the same limitation that is listed earlier in this bulletin related to programs that MBSA 1.2.1 does not detect.

For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about SUIT, visit the following Microsoft Web site. For more information about the limitations of SUIT, 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 (ITMU) 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 ITMU, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.

Note If you have used an Administrative Installation Point 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 about how to change the source for a client computer from an updated administrative installation point to an Office 2000 original baseline source or Service Pack 3 (SP3) see, Microsoft Knowledge Base Article 932889.
  • For more information on how to change the source for a client computer from an updated administrative installation point to an Office XP original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 922665.
  • For more information about 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.

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

For more detailed information, see Microsoft Knowledge Base Article 910723.

Word Malformed String Vulnerability - CVE-2006-5994:

A remote code execution vulnerability exists in the way Microsoft Word handles Word files with a specially crafted string. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious Web site. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution.

Mitigating Factors for Word Malformed String Vulnerability - CVE-2006-5994:

  • 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.
  • Microsoft Office Word 2007 is not affected by this vulnerability.
  • Microsoft Word Viewer 2003 is not affected by this vulnerability.

Workarounds for Word Malformed String Vulnerability - CVE-2006-5994

  • 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.
  • Use Microsoft Word Viewer 2003 to open and view files. The Microsoft Word Viewer 2003 is not affected by the issue. Users can download Microsoft Word Viewer 2003 from the Microsoft Download Center.

FAQ for Word Malformed String Vulnerability - CVE-2006-5994:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Word. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability?
Word does not perform sufficient data validation when processing the contents of a file. When Word opens a specially crafted Word file and parses a malformed string, 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 convincing the user to open the file. The vulnerability cannot be exploited via HTML or Rich Text Format (RTF) e-mail even if a user has configured Word as their e-mail editor.

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 does the update do?
The update removes the vulnerability by modifying the way that Microsoft Word handles certain strings.

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

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.

Word Malformed Data Structures Vulnerability - CVE-2006-6456:

A remote code execution vulnerability exists in the way Microsoft Word handles Word files with a specially crafted data structure. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious Web site. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution. Viewing or previewing a malformed e-mail message in an affected version of Outlook could not lead to exploitation of this vulnerability.

Mitigating Factors for Word Malformed Data Structures Vulnerability - CVE-2006-6456:

  • 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.
  • Microsoft Office Word 2007 is not affected by this vulnerability.

Workarounds for Word Malformed Data Structures Vulnerability - CVE-2006-6456:

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

FAQ for Word Malformed Data Structures Vulnerability - CVE-2006-6456:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Word. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability?
Word does not perform sufficient data validation when processing the contents of a file. When Word opens a specially crafted Word file and parses a malformed data structure, 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 does the update do?
The update removes the vulnerability by modifying the way that Microsoft Word handles certain data structures.

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

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.

Word Count Vulnerability – CVE-2006-6561:

A remote code execution vulnerability exists in Microsoft Word. An attacker could exploit this vulnerability when Word parses a file and processes an unchecked count. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious Web site. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution. Viewing or previewing a malformed e-mail message in an affected version of Outlook could not lead to exploitation of this vulnerability.

Mitigating Factors for Word Count Vulnerability – CVE-2006-6561:

  • 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.
  • Microsoft Office Word 2007 is not affected by this vulnerability.

Workarounds for Word Count Vulnerability – CVE-2006-6561:

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

FAQ for Word Count Vulnerability – CVE-2006-6561:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Word. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability?
Word does not perform sufficient data validation when processing the contents of a file. When Word opens a specially crafted Word file and parses an unchecked count, 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 does the update do?
The update removes the vulnerability by modifying the way that Microsoft Word checks the count, 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-6561.

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.

Word Macro Vulnerability – CVE-2007-0208:

A remote code execution vulnerability exists in Microsoft Word. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

Mitigating Factors for Word Macro Vulnerability – CVE-2007-0208:

  • 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.
  • Microsoft Office Word 2007 is not affected by this vulnerability.
  • Microsoft Word 2000 and Microsoft Word Viewer 2003 are not affected by this vulnerability.

Workarounds for Word Macro Vulnerability – CVE-2007-0208:

  • 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.
  • Use Word Viewer 2003 to open and view files. The Word Viewer 2003 is not affected by this issue. Users can download Microsoft Word Viewer 2003 from the Microsoft Download Center.

FAQ for Word Macro Vulnerability – CVE-2007-0208:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Word. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability?
The vulnerability results because Word incorrectly checks properties in a modified document, causing it to not prompt the user with a macro security warning when macros are present in the document.

What is a Macro?
Generally, the term macro refers to a small program that automates frequently-performed tasks in an operating system or in a program. For example, all members of the Office family of products support the use of macros. This allows companies to develop macros that perform as sophisticated productivity tools that run in Word, in Excel, or in other programs. Like any computer program, macros can be misused. Malicious software may be written as macros and then embedded in Office documents. To mitigate this threat, Office has a security model that is designed to make sure that macros can only run when the user wants them to run. By using this vulnerability, an attacker might be able to run a macro without warning the user that a macro is present in the document.

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 this vulnerability?
An attacker could seek to exploit this vulnerability by creating a specially-crafted Word document that contained a malicious macro. The attacker could then send it to a user, typically through an e-mail message, and then persuade the user to open the document. As a result, if the user were attacked by means of this vulnerability, the user's macro security level could be reduced and other macros that would otherwise be stopped by Word could be allowed to run. An attacker could also host the specially-crafted Word document on a network share or on a Web site; however, the attacker would still need to persuade the user to open the document.

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 does the update do?
The update removes the vulnerability by modifying the way that Microsoft Word performs certain macro security controls when it opens a document.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

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.

Word Malformed Drawing Object Vulnerability - CVE-2007-0209:

A remote code execution vulnerability exists in Microsoft Word. An attacker could exploit this vulnerability when Word parses a file and processes a malformed drawing object. Such a specially crafted file might be included as an e-mail attachment or hosted on a malicious Web site. An attacker could exploit the vulnerability by constructing a specially crafted Word file that could allow remote code execution.

Mitigating Factors for Word Malformed Drawing Object Vulnerability - CVE-2007-0209:

  • 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.
  • Microsoft Word 2003 and Microsoft Word Viewer 2003 are not affected by this vulnerability.
  • Microsoft Office Word 2007 is not affected by this vulnerability.

Workarounds for Word Malformed Drawing Object Vulnerability - CVE-2007-0209:

  • 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.
  • Use Word Viewer 2003 to open and view files. The Word Viewer 2003 is not affected by this issue. Users can download Microsoft Word Viewer 2003 from the Microsoft Download Center.

FAQ for Word Malformed Drawing Object Vulnerability - CVE-2007-0209:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Word. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability?
Word does not perform sufficient data validation when processing the contents of a file. When Word opens a specially crafted Word file and parses a malformed drawing object, 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 does the update do?
The update removes the vulnerability by modifying the way that Microsoft Word handles certain drawing objects.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure.

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.

Word Malformed Function Vulnerability - CVE-2007-0515:

A remote code execution vulnerability exists in Microsoft Word. An attacker could exploit this vulnerability when Word parses a file and processes a malformed function. 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.

Mitigating Factors for Word Malformed Function Vulnerability - CVE-2007-0515:

  • 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.
  • Microsoft Word 2002, Microsoft Word 2003, and Microsoft Word Viewer 2003 are not affected by this vulnerability.
  • Microsoft Office Word 2007 is not affected by this vulnerability.

Workarounds for Word Malformed Function Vulnerability - CVE-2007-0515:

  • 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.
  • Use Word Viewer 2003 to open and view files. The Word Viewer 2003 is not affected by this issue. Users can download Microsoft Word Viewer 2003 from the Microsoft Download Center.

FAQ for Word Malformed Function Vulnerability - CVE-2007-0515:

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Microsoft Word. An attacker could exploit this vulnerability when Word parses a file and processes a malformed function. 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 is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

What causes the vulnerability?
Word does not perform sufficient data validation when processing the contents of a file. When Word opens a specially crafted Word file and parses a malformed function, 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 does the update do?
The update removes the vulnerability by modifying the way that Microsoft Word handles certain strings.

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-2007-0515.

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.

Affected Software:

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

Word 2000

Prerequisites and Additional Update Details

Important Before you install this update, make sure that the following requirements have been met:

  • Microsoft Windows Installer 2.0 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

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.

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.

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
SwitchDescription
/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 NameVersionDateTimeSize
Winword.exe9.0.0.895817-Jan-200702:518,835,124

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, language, or programs installed, some of the files that are listed in the file information table may not be installed.
  5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

    Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Administrative Installation Information

If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.

Installation Information

The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from the security update.

Supported Security Update Installation Switches
SwitchDescription
/? 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.

ProductFeature
O9PRM, O9PRO, O9SBE, O9PIPC1, O9PIPC2, O9STD, O9WDI, O9WRDWORDFiles

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 NameVersionDateTimeSize
Winword.exe9.0.0.895817-Jan-200702:518,835,124

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, language, or programs installed, some of the files that are listed in the file information table may not be installed.
  5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

    Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Word 2002

Prerequisites and Additional Update Details

Important: Before you install this update, make sure that the following requirements have been met:

  • Microsoft Windows Installer 2.0 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

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.

Automated Client Installation Information

Office Update Web Site

This update will be available through the Microsoft Update Web site. Microsoft Update consolidates updates provided by Windows Update and Office Update into one location and enables you to choose automatic delivery and installation of high-priority and security updates. We recommend that you install 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.

Manual Client Installation Information

For detailed information about how to manually install this update please review the following section.

Installation Information

The security update supports the following setup switches:

Supported Security Update Installation Switches
SwitchDescription
/q Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u Specifies user-quiet mode, which Displays some dialog boxes to the user.
/q:a Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path Specifies the target folder for extracting files.
/c Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path Override install command defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n Never restarts the computer after installation.
/r:I Prompts the user to restart the computer if a restart is required, except when used with /q:a
/r:a Always restarts the computer after installation.
/r:s Restarts the computer after installation without prompting the user.
/n:v No version checking;install the program over any earlier version.

Note These switches do not necessarily work with all updates. If a switch is not available, that functionality is required for the correct installation of the update. Also, using the /n:v switch is unsupported and may result in an unbootable system. If the installation is unsuccessful, you should contact your support professional to understand why it could not install.

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

Client Deployment Information

  1. Download the 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 receive the following error message: This update has already been applied or is included in an update that has already been applied.

Client Installation File Information

The English version of this update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Word 2002:

File NameVersionDateTimeSize
Winword.exe10.0.6826.017-Jan-200707:5310,741,088

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 frequently asked question, “Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update, earlier in this bulletin.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Administrative Installation Information

If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.

Installation Information

The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from within the security update.

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

ProductFeature
PIPC1, PROPLUS, PRO, SBE, STD, STDEDU, WORDWORDFiles

Note Additional instructions are provided in Microsoft Knowledge Base Article 832332. Information about this update can also be found on the Microsoft Office XP Resource Kit Web site. General information about the Microsoft Office XP Resource Kit can also be found on TechNet. The Windows Installer Documentation also provides additional information about the parameters supported by the Windows Installer.

For more information on how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Administrative Installation File Information

The English version of this update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Word 2002:

File NameVersionDateTimeSize
Winword.exe10.0.6826.017-Jan-200707:5310,741,088

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 frequently asked question, “Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?” in the section, Frequently Asked Questions (FAQ) Related to This Security Update, earlier in this bulletin.

  • File Version Verification

    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

    1. Click Start, and then click Search.
    2. In the Search Results pane, click All files and folders under Search Companion.
    3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
    4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

      Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
    5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

      Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Word 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 2 must be installed. Before you install this update, install Office 2003 SP2.
  • To update Word Viewer 2003, the latest version of Word Viewer 2003 must be installed. Download the lasted Word Viewer 2003.

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.

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.

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
SwitchDescription
/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 the 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 NameVersionDateTimeSize
Winword.exe11.0.8125.023-Jan-200723:0312,263,776

Word Viewer 2003:

File NameVersionDateTimeSize
Wordview.exe11.0.8125.023-Jan-200723:036,963,552

Administrative Installation Information

If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.

Installation Information

The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from within the security update.

Supported Security Update Installation Switches
SwitchDescription
/? Displays the command-line options.
/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 the Word Viewer 2003.
  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.

ProductFeature
STD11, BASIC11, PERS11, PROI11, PRO11, STDP11, WORD11, PRO11SBWORDFiles
Word Viewer 2003WORDVIEWFiles

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 NameVersionDateTimeSize
Winword.exe11.0.8125.023-Jan-200723:0312,263,776

Word Viewer 2003:

File NameVersionDateTimeSize
Wordview.exe11.0.8125.023-Jan-200723:036,963,552

Verifying that the Update Has Been Applied

  • Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for commonly misconfigured security parameters. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

  • File Version Verification

Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

  1. Click Start, and then click Search.
  2. In the Search Results pane, click All files and folders under Search Companion.
  3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
  4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

    Note Depending on the version of the operating system, language, or programs installed, some of the files that are listed in the file information table may not be installed.
  5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

    Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

Word 2004 for Mac

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.4 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.4 Update volume window, double-click the Microsoft Office 2004 for Mac 11.3.4 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.4 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 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.4, the update has been successfully installed.

Other Information

Acknowledgments

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

Obtaining Other Security Updates:

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

Support:

  • Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.
  • International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.

Security Resources:

Software Update Services:

By using Microsoft Software Update Services (SUS), administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.

For more information about how to deploy 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 (February 13, 2007): Bulletin published.

Built at 2014-04-18T13:49:36Z-07:00

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