Microsoft Security Bulletin MS06-038
Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (917284)
Version: 1.5
Summary
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 a prior security update. See the frequently asked questions (FAQ) section of this bulletin for the complete list.
Caveats: None
Tested Software and Security Update Download Locations:
Affected Software:
| • | Microsoft Office 2003 Service Pack 1 or Service Pack 2 - Download the update (KB917151)
| ||||||||||||||||||||||||||
| • | Microsoft Office XP Service Pack 3 - Download the update (KB917150)
| ||||||||||||||||||||||||||
| • | Microsoft Office 2000 Service Pack 3 - Download the update (KB917152)
| ||||||||||||||||||||||||||
| • | Microsoft Project 2002 Service Pack 1 - Download the update (KB917150) | ||||||||||||||||||||||||||
| • | Microsoft Visio 2002 Service Pack 2 - Download the update (KB917150) | ||||||||||||||||||||||||||
| • | Microsoft Project 2000 Service Release 1 Download the update (KB917152) | ||||||||||||||||||||||||||
| • | Microsoft Office 2004 for Mac | ||||||||||||||||||||||||||
| • | Microsoft Office v. X for Mac |
Non-Affected Software:
| • | Microsoft Works Suites:
|
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 reported and public vulnerabilities. Each vulnerability is documented in this bulletin in its own "Vulnerability Details" section.
When using vulnerable versions of Office, if a user were logged on with administrative user rights, an attacker who successfully exploited 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:
| Vulnerability Identifiers | Impact of Vulnerability | Microsoft Office 2003 | Microsoft Office XP | Microsoft Office 2000 | Microsoft Office 2004 for Mac or Microsoft Office v. X for Mac |
Microsoft Office Parsing Vulnerability - CVE-2006-1316 | Remote Code Execution | Important | Important | Critical | Important |
Microsoft Office Control Vulnerability - CVE-2006-1318 | Remote Code Execution | Important | Important | Critical | Important |
Microsoft Office Malformed String Parsing Vulnerability - CVE-2006-1540 | Remote Code Execution | Important | Important | Critical | Important |
Microsoft Office Property Vulnerability - CVE-2006-2389 | Remote Code Execution | Important | Important | Critical | Important |
Aggregate Severity of All Vulnerabilities |
| Important | Important | Critical | 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.
Frequently Asked Questions (FAQ) Related to This Security Update |
I am updating the administrative installation points and I noticed that there are two .msp’s. Why?
Limitations in our security update detection logic necessitate us having two separate updates. This is because the file being updated, mso.dll, ships in so many products that if we used a single .MSP to target them all, the detection logic in the MSP would be too large for our detection tools to consume. We are actively working on resolving this limitation.
The administrative installation points lists mso.msp and pvmso.msp. Do I need to install both packages?
Yes, the mso.msp targets most of the Office products, such as Word and Excel. The pvmso.msp targets additional Office products, such as Visio, Project and OneNote. In order to be secure you will need to install both packages.
What updates does this release replace?
This security update replaces a prior security update. The security bulletin IDs and affected software are listed in the following table.
| Bulletin ID | Microsoft Office 2003 | Microsoft Office XP, Project 2002 Service Pack 1, and Visio 2002 Service Pack 2 | Microsoft Office 2000 |
Not Applicable | Replaced | Not Applicable |
Can I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?
The following table provides the MBSA detection summary for this security update.
| Software | MBSA 1.2.1 | MBSA 2.0 |
Microsoft Office 2003 | Yes | Yes |
Microsoft Office XP | Yes | Yes |
Microsoft Office 2000 | Yes | No |
Microsoft Office 2004 for Mac | No | No |
Microsoft Office v. X for Mac | No | No |
Note MBSA 1.2.1 uses an integrated version of the Office Detection Tool (ODT) which does not support remote scans of this security update. For more information about MBSA, visit the MBSA Web site.
For more information about MBSA, visit the MBSA Web site. For more information about the programs that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660.
Can I use Systems Management Server (SMS) to determine whether this update is required?
The following table provides the SMS summary for this security update.
| Software | SMS 2.0 | SMS 2003 |
Microsoft Office 2003 | Yes | Yes |
Microsoft Office XP | Yes | Yes |
Microsoft Office 2000 | Yes | Yes |
Microsoft Office 2004 for Mac | No | No |
Microsoft Office v. X for Mac | No | No |
SMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to programs that MBSA does not detect.
For SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.
For more information about SMS, visit the SMS Web site.
Vulnerability Details |
Microsoft Office Parsing Vulnerability - CVE-2006-1316 |
A remote code execution vulnerability exists in Office, and could be exploited when a malformed string included in an Office file was parsed by any of the affected Office applications. Such a string might be included in an email attachment processed by one of the affected applications or hosted on a malicious web site. Viewing or previewing a malformed email 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 Office file that could allow remote code execution.
If a user were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
Mitigating Factors for Microsoft Office Parsing Vulnerability - CVE-2006-1316 |
| • | 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 Outlook 2002 and Outlook 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must accept a prompt confirming that they Open, Save or Cancel the attachment that is sent in an e-mail message before the exploit could occur. |
| • | In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site. |
Note Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.
Workarounds for Microsoft Parsing Vulnerability - CVE-2006-1316: |
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 or that you received unexpectedly from trusted sources.
This vulnerability could be exploited when a user opens a file.
FAQ for Microsoft Office Parsing Vulnerability - CVE-2006-1316: |
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Office, and could be exploited when a malformed string included in an Office file was parsed by any of the affected Office applications. Such a string might be included in an email attachment processed by one of the affected applications or hosted on a malicious web site. Viewing or previewing a malformed email 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 Office file that could allow remote code execution.
If a user were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
What causes the vulnerability?
When Office opens a specially crafted Office 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 cause arbitrary code to run with the privileges of the user who opened the file.
How could an attacker exploit the vulnerability?
In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site.
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 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 parses the length of a record before it passes the message to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Microsoft Office Control Vulnerability - CVE-2006-1318 |
A remote code execution vulnerability exists in Office, and could be exploited when a malformed control included in an Office file was parsed by any of the affected Office applications. Such a control might be included in an email attachment processed by one of the affected applications or hosted on a malicious web site. Viewing or previewing a malformed email 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 Office file that could allow remote code execution.
If a user were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
Mitigating Factors for Microsoft Office Control Vulnerability - CVE-2006-1318 |
| • | 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 Outlook 2002 and Outlook 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must accept a prompt confirming that they Open, Save or Cancel the attachment that is sent in an e-mail message before the exploit could occur. |
| • | In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site. |
Note Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.
Workarounds for Microsoft Control Vulnerability - CVE-2006-1318: |
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 or that you received unexpectedly from trusted sources.
This vulnerability could be exploited when a user opens a file.
FAQ for Microsoft Office Control Vulnerability - CVE-2006-1318: |
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Office, and could be exploited when a malformed control included in an Office file was parsed by any of the affected Office applications. Such a control might be included in an email attachment processed by one of the affected applications or hosted on a malicious web site. Viewing or previewing a malformed email 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 Office file that could allow remote code execution.
If a user were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
What causes the vulnerability?
When Office opens a specially crafted Office file and parses a malformed control, it may corrupt system memory in such a way that an attacker could execute arbitrary code.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause arbitrary code to run with the privileges of the user who opened the file.
How could an attacker exploit the vulnerability?
In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site.
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 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 parses the length of a record before it passes the message to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Microsoft Office Malformed String Parsing Vulnerability - CVE-2006-1540 |
A remote code execution vulnerability exists in Office, and could be exploited when a malformed string included in an Office file was parsed by any of the affected Office applications. Such a string might be included in an email attachment processed by one of the affected applications or hosted on a malicious web site. Viewing or previewing a malformed email 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 Office file that could allow remote code execution.
If a user were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
Mitigating Factors for Microsoft Office Malformed String Parsing Vulnerability - CVE-2006-1540 |
| • | 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 Outlook 2002 and Outlook 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must accept a prompt confirming that they Open, Save or Cancel the attachment that is sent in an e-mail message before the exploit could occur. |
| • | In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site. |
Note Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.
Workarounds for Microsoft Office Malformed String Parsing Vulnerability - CVE-2006-1540: |
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 or that you received unexpectedly from trusted sources.
This vulnerability could be exploited when a user opens a file.
FAQ for Microsoft Office Malformed String Parsing Vulnerability - CVE-2006-1540: |
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 were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
What causes the vulnerability?
When Office opens a specially crafted Office 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 cause arbitrary code to run with the privileges of the user who opened the file.
How could an attacker exploit the vulnerability?
In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site.
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 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 parses the length of a record before it passes the message to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. While the initial report was provided through responsible disclosure, the vulnerability was later disclosed publicly. This security bulletin addresses the publicly disclosed vulnerability as well as additional issues discovered through internal investigations.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
Yes. When the security bulletin was released, Microsoft had received information that this vulnerability was being exploited.
Microsoft Office Property Vulnerability - CVE-2006-2389 |
A remote code execution vulnerability exists in Office, and could be exploited when a malformed property included in an Office file was parsed by any of the affected Office applications. Such a property might be included in an email attachment processed by one of the affected applications or hosted on a malicious web site. Viewing or previewing a malformed email 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 Office file that could allow remote code execution.
If a user were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
Mitigating Factors for Microsoft Office Property Vulnerability - CVE-2006-2389 |
| • | 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 Outlook 2002 and Outlook 2003, the vulnerability could not be exploited automatically through e-mail. For an attack to be successful a user must accept a prompt confirming that they Open, Save or Cancel the attachment that is sent in an e-mail message before the exploit could occur. |
| • | In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site. |
Note Office 2000 does not prompt the user to Open, Save, or Cancel before opening a document.
Workarounds for Microsoft Property Vulnerability - CVE-2006-2389: |
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 or that you received unexpectedly from trusted sources.
This vulnerability could be exploited when a user opens a file.
FAQ for Microsoft Office Property Vulnerability - CVE-2006-2389: |
What is the scope of the vulnerability?
A remote code execution vulnerability exists in Office, and could be exploited when a malformed property included in an Office file was parsed by any of the affected Office applications. Such a property might be included in an email attachment processed by one of the affected applications or hosted on a malicious web site. Viewing or previewing a malformed email 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 Office file that could allow remote code execution.
If a user were logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.
What causes the vulnerability?
When Office opens a specially crafted Office file and parses a malformed property, it may corrupt system memory in such a way that an attacker could execute arbitrary code.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could cause arbitrary code to run with the privileges of the user who opened the file.
How could an attacker exploit the vulnerability?
In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to persuade users to visit the Web site, typically by getting them to click a link in an e-mail message or instant messenger message that takes users to the attacker's Web site.
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 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 parses the length of a record before it passes the message to the allocated buffer.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued. This security bulletin addresses the privately disclosed vulnerability as well as additional issues discovered through internal investigations.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
Security Update Information |
Office 2003 |
Prerequisites and Additional Update Details |
Important: Before you install this update, make sure that the following requirements have been met:
| • | To update Office 2003, Office 2003 Service Pack 1 must be installed. Before you install this update, install Office 2003 SP1 or Office 2003 SP2. |
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 | |
| Switch | Description |
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
/q:u | Specifies user-quiet mode, which presents some dialog boxes to the user. |
/q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. |
/t:path | Specifies the target folder for extracting files. |
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
/c:path | 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 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. | |
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.
Office 2003:
| File Name | Version | Date | Time | Size |
Ietag.dll | 11.0.6550.0 | 17-Mar-2005 | 21:36 | 161,984 |
Mso.dll | 11.0.8028.0 | 26-May-2006 | 15:24 | 12,254,984 |
Administrative Installation Information |
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.
Installation Information
The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from within the security update.
| Supported Security Update Installation Switches | |
| Switch | Description |
/? | Displays the command-line options. |
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
/t:path | Specifies the target folder for extracting files. |
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
/c:path | Override install 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. | |
2. | 2.Click Save this program to disk, and then click OK. |
3. | Click Save. |
4. | Using Windows Explorer, locate the folder that contains the saved file. Click Start, click Run, type the following command, and then click OK to extract the .msp file: |
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: |
8. | Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box. |
9. | Click I accept the terms in the License Agreement, and then click Install. |
At this point, your administrative installation point is updated. Next, you must update the workstations configurations that were originally installed from this administrative installation. To do this, please review the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update.
Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions such as repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section.
Workstation Deployment Information
To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK:
Msiexec /I Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu
Note Admin Path is the path of your administrative installation point for your application (for example, C:\Office2003), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update.
To install all features, you can use REINSTALL=ALL or you can install the following features
| Product | Feature |
RMS | RMSFiles, ProductFiles |
ACCESSRT, ACC11 | ACCESSNonBootFiles, ProductFiles |
STD11, BASIC11, PERS11, STDP11 | WORDNonBootFiles, EXCELNonBootFiles, ProductFiles |
FP11, OUTLS11, OUTL11, PPT11, INF11, OUTLSM11 | ProductFiles |
PROI11, PRO11, PRO11SB | WORDNonBootFiles, ACCESSNonBootFiles, EXCELNonBootFiles, ProductFiles |
WORD11 | WORDNonBootFiles, ProductFiles |
EXCEL11 | EXCELNonBootFiles, ProductFiles |
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.
Office 2003:
| File Name | Version | Date | Time | Size |
Ietag.dll | 11.0.6550.0 | 17-Mar-2005 | 21:36 | 161,984 |
Mso.dll | 11.0.8028.0 | 26-May-2006 | 15:24 | 12,254,984 |
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. |
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. |
Office XP |
Prerequisites and Additional Update Details |
Important: Before you install this update, make sure that the following requirements have been met:
| • | Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP, and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of the Windows Installer, visit one of the following Microsoft Web sites: |
Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition
Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
| • | Office XP Service Pack 3 (SP3) must be installed. Before you install this update, install Office XP SP3. For more information about how to install Office XP SP3, see Microsoft Knowledge Base Article 832671 and/or Project 2002 Service Pack 1 (SP1) and/or Visio 2002 Service Pack 2 (SP2) must be installed. |
For more information about how to determine the version of Office XP that is installed on your computer, see Microsoft Knowledge Base Article 291331. For more information about the version information displayed in the About dialog box, see Microsoft Knowledge Base Article 328294.
Inclusion in Future Service Packs
None. Service Pack 3 is the last service pack for Office XP.
Restart Requirement
To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
Removal Information
To remove this security update, use the Add or Remove Programs tool in Control Panel.
Note When you remove this update, you may be prompted to insert the Microsoft Office XP CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
Note For Project 2002 Service Pack 1 and Visio 2002 Service Pack 2, after you install the update, you cannot remove it. To revert to an installation before the update was installed; you must remove the application, and then install it again from the original CD-ROM.
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 | |
| Switch | Description |
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
/q:u | Specifies user-quiet mode, which presents some dialog boxes to the user. |
/q:a | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. |
/t:path | Specifies the target folder for extracting files. |
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
/c:path | 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 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 Office XP and/or download the security update for Project 2002 Service Pack 1 and/or download the security update for Visio 2002 Service Pack 2. |
2. | Click Save this program to disk, and then click OK. |
3. | Click Save. |
4. | Using Windows Explorer, find the folder that contains the saved file, and then double-click the saved file. |
5. | If you are prompted to install the update, click Yes. |
6. | Click Yes to accept the License Agreement. |
7. | Insert your original source CD-ROM when you are prompted to do so, and then click OK. |
8. | When you receive a message that states the installation was successful, click OK. |
Note If the security update is already installed on your computer, you see the following error message: This update has already been applied or is included in an update that has already been applied.
Client Installation File Information
The English version of this update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Office XP:
| File Name | Version | Date | Time | Size |
Ietag.dll | 10.0.6731.0 | 10-Sep-2004 | 21:11 | 105,152 |
Ietag.dll_1033 | 10.0.6731.0 | 10-Sep-2004 | 21:11 | 105,152 |
Mso.dll | 10.0.6804.0 | 31-May-2006 | 21:25 | 9,816,840 |
Project 2002 Service Pack1:
| File Name | Version | Date | Time | Size |
Mso.dll | 10.0.6804.0 | 31-May-2006 | 21:25 | 9,816,840 |
Visio 2002 Service Pack 2:
| File Name | Version | Date | Time | Size |
Mso.dll | 10.0.6804.0 | 31-May-2006 | 21:25 | 9,816,840 |
Administrative Installation Information |
If you installed your application from a server location, the server administrator must update the server location with the administrative update and deploy that update to your computer.
Installation Information
The following setup switches are relevant to administrative installations as they allow an administrator to customize how the files are extracted from within the security update.
| Supported Security Update Installation Switches | |
| Switch | Description |
/? | Displays the command-line options. |
/q | Specifies quiet mode, or suppresses prompts, when files are being extracted. |
/t:path | Specifies the target folder for extracting files. |
/c | Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder. |
/c:path | Override install 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 this security update for Office XP and/or download the security update for Project 2002 Service Pack 1 and/or download the security update for Visio 2002 Service Pack 2. |
2. | Click Save this program to disk, and then click OK. |
3. | Click Save. |
4. | Using Windows Explorer, locate the folder that contains the saved file. Click Start, click Run, type the following command, and then click OK to extract the .msp file: |
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: |
8. | Click Next in the provided dialog box. Do not change your CD key, installation location, or company name in the provided dialog box. |
9. | Click I accept the terms in the License Agreement, and then click Install. |
At this point, your administrative installation point is updated. Next, you must update the workstation configurations that were originally installed from this administrative installation. To do this, see the “Workstation Deployment Information” section. Any new installations that you run from this administrative installation point will include the update.
Warning Any workstation configuration that was originally installed from this administrative installation before you installed the update cannot use this administrative installation for actions like repairing Office or adding new features until you complete the steps in the “Workstation Deployment Information” section for this workstation.
Workstation Deployment Information
To deploy the update to the client workstations, click Start, click Run, type the following command, and then click OK:
msiexec /I Admin Path\MSI File /qb REINSTALL=Feature List REINSTALLMODE=vomu
Note Admin Path is the path of your administrative installation point for your application (for example, C:\OfficeXP), MSI File is the .msi database package for the application (for example, Data1.msi), and Feature List is the list of feature names (case sensitive) that must be reinstalled for the update.
To install all features, you can use REINSTALL=ALL or you can install the following features.
| Product | Feature |
ACCESS, FP, OUTLOOK, PPT, ACCESSRT, PUB | ProductFiles |
PIPC1, PROPLUS, PRO, SBE, STD, STDEDU | ProductFiles |
WORD | WORDNonBootFiles, ProductFiles |
EXCEL | EXCELNonBootFiles, ProductFiles |
Visio 2002 | Program_Files |
Project 2002 | ProductFiles |
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.
Office XP:
| File Name | Version | Date | Time | Size |
Ietag.dll | 10.0.6731.0 | 10-Sep-2004 | 21:11 | 105,152 |
Ietag.dll_1033 | 10.0.6731.0 | 10-Sep-2004 | 21:11 | 105,152 |
Mso.dll | 10.0.6804.0 | 31-May-2006 | 21:25 | 9,816,840 |
Project 2002 Service Pack 1:
| File Name | Version | Date | Time | Size |
Mso.dll | 10.0.6804.0 | 31-May-2006 | 21:25 | 9,816,840 |
Visio 2002 Service Pack 2:
| File Name | Version | Date | Time | Size |
Mso.dll | 10.0.6804.0 | 31-May-2006 | 21:25 | 9,816,840 |
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. |
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. |
Office 2000 |
Prerequisites and Additional Update Details |
Important Before you install this update, make sure that the following requirements have been met:
| • | Microsoft Windows Installer 2.0 must be installed. Microsoft Windows Server 2003, Windows XP and Microsoft Windows 2000 Service Pack 3 (SP3) include Windows Installer 2.0 or a later version. To install the latest version of Windows Installer, visit one of the following Microsoft Web sites: |
Windows Installer 2.0 for Windows 95, Windows 98, Windows 98 SE, and Windows Millennium Edition
Windows Installer 2.0 for Windows 2000 and Windows NT 4.0
| • | Office 2000 Service Pack 3 (SP3) must be installed. Before you install this update, install Office 2000 SP3. For more information about how to install Office 2000 SP3, see Microsoft Knowledge Base Article 326585 and/or Project 2000 Service Pack 1 (SP1) must be installed. |
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