Security Bulletin

Microsoft Security Bulletin MS06-012 - Critical

Published: March 14, 2006 | Updated: December 27, 2006

Version: 1.5

Who should read this document: Customers who use Microsoft Office

Impact of Vulnerability: Remote Code Execution

Maximum Severity Rating: Critical

Recommendation: Customers should apply the update immediately.

Security Update Replacement: This bulletin replaces several prior security updates. 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
  • Microsoft Word 2000 - Download the update (KB905553)
  • Microsoft Excel 2000 - Download the update (KB905757)
  • Microsoft Outlook 2000 - Download the update (KB905646)
  • Microsoft PowerPoint 2000 - Download the update (KB905555)
  • Microsoft Office 2000 MultiLanguage Packs - Download the update (KB905646)
• Microsoft Office XP Service Pack 3
  • Microsoft Word 2002 - Download the update (KB905754)
  • Microsoft Excel 2002 - Download the update (KB905755)
  • Microsoft Outlook 2002 - Download the update (KB905649)
  • Microsoft PowerPoint 2002 - Download the update (KB905758)
  • Microsoft Office XP Multilingual User Interface Packs - Download the update (KB905649)
• Microsoft Office 2003 Service Pack 1 or Service Pack 2
  • Microsoft Excel 2003 - Download the update (KB905756)
  • Microsoft Excel 2003 Viewer - Download the update (KB914451)
• Microsoft Works Suites:
  • Microsoft Works Suite 2000 - Download the update (KB905553) (same as Microsoft Word 2000 update)
  • Microsoft Works Suite 2001 - Download the update (KB905553) (same as Microsoft Word 2000 update)
  • Microsoft Works Suite 2002 - Download the update (KB905754) (same as the Microsoft Word 2002 update)
  • Microsoft Works Suite 2003 - Download the update (KB905754) (same as the Microsoft Word 2002 update)
  • Microsoft Works Suite 2004 -Download the update (KB905754) (same as the Microsoft Word 2002 update)
  • Microsoft Works Suite 2005 -Download the update (KB905754) (same as the Microsoft Word 2002 update)
  • Microsoft Works Suite 2006 -Download the update (KB905754) (same as the Microsoft Word 2002 update)
• Microsoft Office X for Mac - Download the update
  • Microsoft Excel X for Mac
• Microsoft Office 2004 for Mac - Download the update
  • Microsoft Excel 2004 for Mac

Non-Affected Software:

• Microsoft Office Excel 2000 Viewer
• Microsoft Office Excel 2002 Viewer
• Microsoft Word 2003
• Microsoft Outlook 2003
• Microsoft PowerPoint 2003

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.

Executive Summary:

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

On vulnerable versions of Office, if a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability 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:

Note [1] The Remote Code Execution with Microsoft Office Excel Vulnerability - CVE-2005-4131, CVE-2006-0028, CVE-2006-0029, CVE-2006-0030, and CVE-2006-0031 only affects Excel.

Note Word 2003, Outlook 2003, and PowerPoint 2003 are not listed in the table because they are not affected by either vulnerability.

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

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

This assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.

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

Note All supported versions of Microsoft Works are replaced by MS05-035.

Why does Microsoft Works Suite appear in the Affected Software list?
Microsoft Works Suite appears in the Affected Software list because it includes Microsoft Word. Microsoft Works users should use Office Update to detect and to install the appropriate update.

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

Note MBSA 1.2.1 does not support Microsoft Office for Mac 2004 or Microsoft Office X for Mac.

Can I use the Microsoft Baseline Security Analyzer (MBSA) 2.0 to determine whether this update is required?
Yes. MBSA 2.0 will determine whether this update is required for Office XP and Office 2003. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site. MBSA 2.0 does not support the detection of Office 2000. You should use MBSA 1.2.1 to determine if this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.

Note MBSA 2.0 does not support Microsoft Office for Mac 2004 or Microsoft Office X for Mac.

Can I use Systems Management Server (SMS) to determine whether this update is required?
Yes. SMS can help detect and deploy this security update. SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to programs that MBSA does not detect. 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. Therefore, SMS SUIT has the same limitation listed earlier in this bulletin related to programs that MBSA does not detect. 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.

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

A remote code execution vulnerability exists in Excel using a malformed range. An attacker could exploit the vulnerability by constructing a specially crafted Excel 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 affected than users who operate with administrative user rights.

• 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.
• When running Office XP or Office 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
• On Office XP and Office 2003, this vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to 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.

Note This vulnerability could be exploited automatically when using Office 2000. Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.

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 Excel files that you receive from un-trusted sources.
This vulnerability could be exploited when a user opens a file.

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system.

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 affected than users who operate with administrative user rights.

What causes the vulnerability?
When Excel opens a specially crafted Excel using a malformed range, 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 a Web-based attack scenario, an attacker would have to host a Web site that contains an Office file that is used to attempt to 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. 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.

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 do not 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 Excel validates the length of a message 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-2005-4131. It also has been named Excel eBay Vulnerability by the larger security community.

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.

A remote code execution vulnerability exists in Excel using a malformed parsing format file. An attacker could exploit the vulnerability by constructing a specially crafted Excel 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 affected than users who operate with administrative user rights.

• 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.
• When running Office XP or Office 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
• On Office XP and Office 2003, this vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to 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.

Note This vulnerability could be exploited automatically when using Office 2000. Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.

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 Excel files that you receive from un-trusted sources.
This vulnerability could be exploited when a user opens a file.

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system.

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 affected than users who operate with administrative user rights.

What causes the vulnerability?
When Excel opens a specially crafted Excel file using malformed parsing format 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 a Web-based attack scenario, an attacker would have to host a Web site that contains an Office file that is used to attempt to 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. 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.

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 do not 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 Excel validates the length of a message 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.

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.

A remote code execution vulnerability exists in Excel using a malformed description. An attacker could exploit the vulnerability by constructing a specially crafted Excel 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 affected than users who operate with administrative user rights.

• 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.
• When running Office XP or Office 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
• On Office XP and Office 2003, this vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to 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.

Note This vulnerability could be exploited automatically when using Office 2000. Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.

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 Excel files that you receive from un-trusted sources.
This vulnerability could be exploited when a user opens a file.

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system.

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 affected than users who operate with administrative user rights.

What causes the vulnerability?
When Excel opens a specially crafted Excel file using a malformed description, 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 a Web-based attack scenario, an attacker would have to host a Web site that contains an Office file that is used to attempt to 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. 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.

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 do not 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 Excel validates the length of a message 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.

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.

A remote code execution vulnerability exists in Excel using malformed graphic. An attacker could exploit the vulnerability by constructing a specially crafted Excel 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 affected than users who operate with administrative user rights.

• 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.
• When running Office XP or Office 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
• On Office XP and Office 2003, this vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to 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.

Note This vulnerability could be exploited automatically when using Office 2000. Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.

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 Excel files that you receive from un-trusted sources.
This vulnerability could be exploited when a user opens a file.

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system.

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 affected than users who operate with administrative user rights.

What causes the vulnerability?
When Excel opens a specially crafted Excel file using a malformed graphic, 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 a Web-based attack scenario, an attacker would have to host a Web site that contains an Office file that is used to attempt to 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. 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.

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 do not 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 Excel validates the length of a message 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 numberCVE-2006-0030

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

A remote code execution vulnerability exists in Excel using a malformed record. An attacker could exploit the vulnerability by constructing a specially crafted Excel 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 affected than users who operate with administrative user rights.

• 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.
• When running Office XP or Office 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message.
• On Office XP and Office 2003, this vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to 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.

Note This vulnerability could be exploited automatically when using Office 2000. Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.

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 Excel files that you receive from un-trusted sources.
This vulnerability could be exploited when a user opens a file.

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system.

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 affected than users who operate with administrative user rights.

What causes the vulnerability?
When Excel opens a specially crafted Excel file using a malformed record, 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 a Web-based attack scenario, an attacker would have to host a Web site that contains an Office file that is used to attempt to 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. 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.

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 do not 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 Excel validates the length of a message 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.

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

A remote code execution vulnerability exists in Office. An attacker could exploit the vulnerability by constructing a specially crafted routing slip within an Office document that could allow remote code execution. An attacker who successfully exploited this vulnerability could take complete control of the affected system.

• 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.
• On Office XP and Office 2003, this vulnerability could not be exploited automatically through a Web-based attack scenario. An attacker would have to host a Web site that contains an Office file that is used to attempt to 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.
• When running Office XP or Office 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must open an attachment that is sent in an e-mail message

Note This vulnerability could be exploited automatically when using Office 2000. Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.

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 Office files that you receive from un-trusted sources. This vulnerability could be exploited when a user opens a file.

What is the scope of the vulnerability?
A remote code execution vulnerability exists in Office. An attacker could exploit the vulnerability by constructing a specially crafted routing slip within an Office document that could allow remote code execution. An attacker who successfully exploited this vulnerability could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
When Office opens a crafted routing slip within an Office document, it may corrupt system memory in such a way that an attacker could execute arbitrary code.

What is a routing slip?
Microsoft Office applications have the ability to add a "routing slip" to an Office document. Document Routing facilitates the flow of information among a group of users. With Document Routing features as part of a client application, a user can route any type of file to co-workers by attaching it to an e-mail message. It can be sent either to one person at a time or to the group simultaneously. This feature works the same as the File Send option in Office applications, using the same dialogs

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 a Web-based attack scenario, an attacker would have to host a Web site that contains an Office file that is used to attempt to 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. 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.

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 do not 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 Office validates the length of data in the file before it passes the file 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.

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.

Affected Software:

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

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) or Microsoft Office 2000 Service Pack 3 for Office 2000 SR1 Multilanguage Pack must be installed. Before you install this update, install Office 2000 SP3. Additionally, if you are installing Office 2000 SP3 for Office SR1 Multilanguage Pack, you must install Multilanguage Pack Service Pack. 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.

Office Update Web Site

We recommend that you install the Microsoft Office 2000 client updates by using the Office Update Web site. The Office Update Web site detects your particular installation and prompts you to install exactly what you must have to make sure that your installation is completely up to date.

To have the Office Update Web site detect the 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.

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

Installation Information

The security update supports the following setup switches.

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 appropriate client version of this security update: Excel 2000, Outlook 2000, Office 2000 English Multilanguage Pack, PowerPoint 2000, or 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.

Excel 2000:

Word 2000:

Outlook 2000 (These files installed on all operating systems):

Outlook 2000 (These files are installed in only on (Windows 98, Windows 98 Second Edition (SE), and Windows Millennium Edition (ME) operating systems):

Outlook 2000 (These files are installed in only on Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, and Windows NT Server 4.0 Terminal Server Edition Service Pack 6 and later operating systems):

PowerPoint 2000:

Office 2000 Multilingual User Interface Packs:

Office 2000 Multilingual User Interface Packs (These files are installed on only Windows (Windows 98, Windows 98 Second Edition (SE), and Windows Millennium Edition (ME) operating systems):

Office 2000 Multilingual User Interface Packs (These files are installed on only on Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, and Windows NT Server 4.0 Terminal Server Edition Service Pack 6 and later operating systems):

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 can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

• File Version Verification

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

1. Click Start, and then click Search.

2. In the Search Results pane, click All files and folders under Search Companion.

3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

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

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.

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 appropriate client version of this security update: Excel 2000, Outlook 2000, Office 2000 English Multilanguage Pack, PowerPoint 2000, or 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.

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.

Excel 2000:

Word 2000:

Outlook 2000 (These files are installed on all operating systems):

Outlook 2000 (These files are installed on only (Windows 98, Windows 98 Second Edition (SE), and Windows Millennium Edition (ME) operating systems):

Outlook 2000 (These files are installed on only on Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, and Windows NT Server 4.0 Terminal Server Edition Service Pack 6 and later operating systems):

PowerPoint 2000:

Office 2000 Multilingual User Interface Packs:

Office 2000 Multilingual User Interface Packs (These files are installed on only Windows (Windows 98, Windows 98 Second Edition (SE), and Windows Millennium Edition (ME) operating systems):

Office 2000 Multilingual User Interface Packs (These files are installed on only on Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, and Windows NT Server 4.0 Terminal Server Edition Service Pack 6 and later operating systems):

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 can use the Microsoft Baseline Security Analyzer (MBSA) tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.

• File Version Verification

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

1. Click Start, and then click Search.
2. In the Search Results pane, click All files and folders under Search Companion.
3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

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. Additionally, if you are installing Office XP Multilingual User Interface Packs, you must install Multilingual User Interface Packs Service Pack 3 (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.

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.

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.

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

Installation Information

The security update supports the following setup switches.

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 appropriate client version of this security update: Excel 2002, Outlook 2002, Office 2002 English Multilanguage Pack, PowerPoint 2002, or 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.

Excel 2002:

Word 2002:

Outlook 2002 (These files are installed on all operating systems):

Outlook 2002 (These files are installed on only Windows (Windows 98, Windows 98 Second Edition (SE), and Windows Millennium Edition (ME) operating systems):

Outlook 2002 (These files are installed on only on Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, and Windows NT Server 4.0 Terminal Server Edition Service Pack 6 and later operating systems):

PowerPoint 2002:

Office XP Multilingual User Interface Packs:

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.

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 appropriate client version of this security update: Excel 2002, Outlook 2002, Office 2002 English Multilanguage Pack, PowerPoint 2002, or 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 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:\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.

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.

Excel 2002:

Word 2002:

Outlook 2002:

Outlook 2002 (Files installed in only Windows (Windows 98, Windows 98 Second Edition (SE), and Windows Millennium Edition (ME) operating systems):

Outlook 2002 (Files installed in only on Windows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, and Windows NT Server 4.0 Terminal Server Edition Service Pack 6 and later operating systems):

PowerPoint 2002:

Office XP Multilingual User Interface Packs:

Verifying that the Update Has Been Applied

• Microsoft Baseline Security Analyzer

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

• File Version Verification

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

1. Click Start, and then click Search.
2. In the Search Results pane, click All files and folders under Search Companion.
3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.
4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties. Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.
5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table. Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.

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 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.
• The latest version of the Excel 2003 Viewer must be installed. Before you install this update, install Excel 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 the Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

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.

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

Installation Information

The security update supports the following setup switches.

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 appropriate client version of this security update: Excel 2003 or Excel 2003 Viewer
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.

Excel 2003:

Excel 2003 Viewer:

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.

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 appropriate client version of this security update: Excel 2003 or Excel 2003 Viewer.

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 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:\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

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.

Excel 2003:

Excel Viewer 2003:

Verifying that the Update Has Been Applied

• Microsoft Baseline Security Analyzer

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

• File Version Verification

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

1. Click Start, and then click Search.

2. In the Search Results pane, click All files and folders under Search Companion.

3. In the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.

4. In the list of files, right-click a file name from the appropriate file information table, and then click Properties.

   Note Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.

5. On the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.

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

Prerequisites

This security update requires Excel v. X for Mac Versions 10.0 through 10.1.6 to be installed.

Installation Information

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. Navigate to the Application Binary (Applications/Microsoft Office X/Microsoft Excel).
2. Click the application.
3. Click File, and then click Get Info.

If the Version number is 10.1.7, the update has been successfully installed.

Prerequisites

This security update requires Excel 2004 for Mac Versions 11.0.0 through 11.2.2 to be installed.

Installation Information

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. Navigate to the Application Binary (Microsoft Office 2004:Microsoft Excel).
2. Click the application.
3. Click File, and then click Get Info.

If the Version number is 11.2.3, the update has been successfully installed.

Acknowledgments

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

• Ollie Whitehouse of Symantec for reporting the Microsoft Office Remote Code Execution Using a Malformed Routing Slip Vulnerability - CVE-2006-0009
• FelicioX for working with Microsoft on the Microsoft Office Excel Remote Code Execution Using a Malformed Range Vulnerability - CVE-2005-4131
• Peter Winter-Smith of NGS Software for reporting similar behavior to the Remote Code Execution with Microsoft Office Excel Vulnerability - CVE-2005-4131
• Arnaud Dovi working with TippingPoint and the Zero Day Initiative for reporting the Microsoft Office Excel Remote Code Execution Using a Malformed File Format Parsing Vulnerability - CVE-2006-0028
• Dejun of the Fortinet Security Response Team for reporting the Microsoft Office Excel Remote Code Execution Using a Malformed Description Vulnerability - CVE-2006-0029
• Eyas of the XFOCUS Security Team for reporting the Microsoft Office Excel Remote Code Execution Using a Malformed Record Vulnerability - CVE-2006-0031

Obtaining Other Security Updates:

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

• Security updates are available in 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 more information about security in Microsoft products.
• 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 Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool (available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack) to install these updates.

Disclaimer:

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions:

• V1.0 (March 14, 2006): Bulletin published.
• V1.2 (March 17, 2006): Bulletin revised: Removed MS05-012 and MS06-010 from “What updates does this release replace?” in the “Frequently asked questions (FAQ) related to this security update” section. Updated the “Mitigations and Work Around” section for all vulnerabilities to provide additional clarity around Office 2000 in addition updated the” Acknowledgments” section for CVE-2006-0028.
• V1.3 (November 29, 2006): Bulletin Updated: “What updates does this release replace?” for Microsoft Outlook in the “Frequently asked questions (FAQ) related to this security update” section.
• V1.4 (December 6, 2006): Bulletin Updated: “What updates does this release replace?” for Microsoft Outlook in the “Frequently asked questions (FAQ) related to this security update” section.
• V1.5 (December 27, 2006): Bulletin Updated to provide additional clarity for “What updates does this release replace?” for Microsoft Outlook in the “Frequently asked questions (FAQ) related to this security update” section.

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