Article
12/03/2019
90 minutes to read

Security Bulletin

Microsoft Security Bulletin MS09-021 - Critical

Vulnerabilities in Microsoft Office Excel Could Allow Remote Code Execution (969462)

Published: June 09, 2009 | Updated: June 17, 2009

Version: 1.1

General Information

Executive Summary

This security update resolves several privately reported vulnerabilities that could allow remote code execution if a user opens a specially crafted Excel file that includes a malformed record object. An attacker who successfully exploited any of these vulnerabilities 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.

This security update is rated Critical for all supported editions of Microsoft Office Excel 2000. For all supported editions of Microsoft Office Excel 2002, Microsoft Office Excel 2003, Microsoft Office Excel 2007, Microsoft Office 2004 for Mac, and Microsoft Office 2008 for Mac; Open XML File Format Converter for Mac; and all supported versions of Microsoft Office Excel Viewer and Microsoft Office Compatibility Pack, this security update is rated Important.

The update addresses the vulnerabilities by modifying the way that Excel parses Excel files. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

Recommendation. Microsoft recommends that customers apply the update immediately.

Known Issues. Microsoft Knowledge Base Article 969462 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.

Affected and Non-Affected Software

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

Affected Software

Office Suite and Other Software	Component	Maximum Security Impact	Aggregate Severity Rating	Bulletins Replaced by this Update
Microsoft Office Suites and Components
Microsoft Office 2000 Service Pack 3	[Microsoft Office Excel 2000 Service Pack 3](https://www.microsoft.com/download/details.aspx?familyid=dd16e243-b8e2-4afb-86b6-4d60214598eb) (KB969683)	Remote Code Execution	Critical	[MS09-009](http://go.microsoft.com/fwlink/?linkid=143568)
Microsoft Office XP Service Pack 3	[Microsoft Office Excel 2002 Service Pack 3](https://www.microsoft.com/download/details.aspx?familyid=dd80ce95-0aec-4493-b9d1-c3dad95c3415) (KB969680)	Remote Code Execution	Important	[MS09-009](http://go.microsoft.com/fwlink/?linkid=143568)
Microsoft Office 2003 Service Pack 3	[Microsoft Office Excel 2003 Service Pack 3](https://www.microsoft.com/download/details.aspx?familyid=10156044-a5a4-4312-98a7-1b1ced625ddb) (KB969681)	Remote Code Execution	Important	[MS09-009](http://go.microsoft.com/fwlink/?linkid=143568)
2007 Microsoft Office System Service Pack 1	[Microsoft Office Excel 2007 Service Pack 1](https://www.microsoft.com/download/details.aspx?familyid=2bcd565a-6acb-407d-80da-0398526ddf99)\* (KB969682)	Remote Code Execution	Important	[MS09-009](http://go.microsoft.com/fwlink/?linkid=143568)
2007 Microsoft Office System Service Pack 2	[Microsoft Office Excel 2007 Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=2bcd565a-6acb-407d-80da-0398526ddf99)\* (KB969682)	Remote Code Execution	Important	None
Microsoft Office for Mac
[Microsoft Office 2004 for Mac](https://www.microsoft.com/download/details.aspx?familyid=5557bfb7-ebb4-4c42-8042-41e830c4e550) (KB969661)	Not applicable	Remote Code Execution	Important	[MS09-009](http://go.microsoft.com/fwlink/?linkid=143568)
[Microsoft Office 2008 for Mac](https://www.microsoft.com/download/details.aspx?familyid=58326da2-eb75-4b42-b1bc-e70319defb58) (KB971822)	Not applicable	Remote Code Execution	Important	[MS09-009](http://go.microsoft.com/fwlink/?linkid=143568)
[Open XML File Format Converter for Mac](https://www.microsoft.com/download/details.aspx?familyid=9d6d9eaa-8442-4184-8886-faab2803bde6) (KB971824)	Not applicable	Remote Code Execution	Important	[MS08-074](http://go.microsoft.com/fwlink/?linkid=131481)
Other Office Software
[Microsoft Office Excel Viewer 2003 Service Pack 3](https://www.microsoft.com/download/details.aspx?familyid=20e6933d-85f8-4cec-9534-893789cd053e) (KB969685)	Not applicable	Remote Code Execution	Important	[MS09-009](http://go.microsoft.com/fwlink/?linkid=143568)
[Microsoft Office Excel Viewer](https://www.microsoft.com/download/details.aspx?familyid=ac0530dc-7f63-4ad0-85c1-784ad28156cf) (KB969686)	Not applicable	Remote Code Execution	Important	[MS09-009](http://go.microsoft.com/fwlink/?linkid=143568)
[Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1](https://www.microsoft.com/download/details.aspx?familyid=a8be8457-b0b6-455e-907e-d13be883adf2) (KB969679)	Not applicable	Remote Code Execution	Important	[MS09-009](http://go.microsoft.com/fwlink/?linkid=143568)
[Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=a8be8457-b0b6-455e-907e-d13be883adf2) (KB969679)	Not applicable	Remote Code Execution	Important	None
[Microsoft Office SharePoint Server 2007 Service Pack 1 (32-bit editions)](https://www.microsoft.com/download/details.aspx?familyid=862e6ad1-8124-4060-93b1-2b882ef5ce3d)\\ (KB969737)	Not applicable	Remote Code Execution	Important	[MS08-057](http://go.microsoft.com/fwlink/?linkid=124653)
[Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions)](https://www.microsoft.com/download/details.aspx?familyid=862e6ad1-8124-4060-93b1-2b882ef5ce3d)\\ (KB969737)	Not applicable	Remote Code Execution	Important	None
[Microsoft Office SharePoint Server 2007 Service Pack 1 (64-bit editions)](https://www.microsoft.com/download/details.aspx?familyid=b7b6e611-2c5d-4639-add9-972055789ecd)\\ (KB969737)	Not applicable	Remote Code Execution	Important	[MS08-057](http://go.microsoft.com/fwlink/?linkid=124653)
[Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions)](https://www.microsoft.com/download/details.aspx?familyid=b7b6e611-2c5d-4639-add9-972055789ecd)\\ (KB969737)	Not applicable	Remote Code Execution	Important	None

\*For Microsoft Office Excel 2007 Service Pack 1 and Microsoft Office Excel 2007 Service Pack 2, in addition to security update package KB969682, customers also need to install the security update for [Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2](https://www.microsoft.com/download/details.aspx?familyid=a8be8457-b0b6-455e-907e-d13be883adf2) (KB969679) to be protected from the vulnerabilities described in this bulletin.

**This update applies to servers that have Excel Services installed, such as the default configuration of Microsoft Office SharePoint Server 2007 Enterprise and Microsoft Office SharePoint Server 2007 For Internet Sites. Microsoft Office SharePoint Server 2007 Standard does not include Excel Services.

Non-Affected Software

Office and Other Software
Microsoft Office Converter Pack
Works 8.5
Works 9

Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.

MS09-017 and MS09-027 also describe vulnerabilities in Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, and Open XML File Format Converter for Mac. How do MS09-017 and MS09-027 relate to this bulletin (MS09-021)?
The security update packages for Microsoft Office 2004 for Mac (KB969661), Microsoft Office 2008 for Mac (KB971822), and Open XML File Format Converter for Mac (KB971824) in this bulletin, MS09-021, also address the vulnerabilities described in MS09-017 and MS09-027. Users with Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, or Open XML File Format Converter for Mac installed will only need to install the update packages once.

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 need to install this update only.

What components of the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats are updated by this bulletin?
The update included with this security bulletin applies only to the specific component within the Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats that is affected. For example, in an Excel bulletin, only the Excel compatibility pack component files are included in the update packages and not Word or PowerPoint compatibility pack component files. Word compatibility pack component files are updated in a Word bulletin and PowerPoint compatibility pack component files are updated in a PowerPoint bulletin.

What is the Microsoft Office Excel Viewer?
The Microsoft Office Excel Viewer is a replacement for all previous Excel Viewer versions, including Excel Viewer 97 and Excel Viewer 2003. With Excel Viewer, you can open, view, and print Excel workbooks, even if you don't have Excel installed. You can also copy data from Excel Viewer to another program. However, you cannot edit data, save a workbook, or create a new workbook.

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

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

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

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

The following severity ratings assume the potential maximum impact of the vulnerability. For information regarding the likelihood, within 30 days of this security bulletin's release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the June bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software	Record Pointer Corruption Vulnerability - CVE-2009-0549	Object Record Corruption Vulnerability - CVE-2009-0557	Array Indexing Memory Corruption Vulnerability - CVE-2009-0558	String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559	Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560	Record Integer Overflow Vulnerability - CVE-2009-0561	Record Pointer Corruption Vulnerability - CVE-2009-1134	Aggregate Severity Rating
Microsoft Office Suites and Components
Microsoft Office Excel 2000 Service Pack 3	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Not applicable	Critical
Microsoft Office Excel 2002 Service Pack 3	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office Excel 2003 Service Pack 3	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office Excel 2007 Service Pack 1	Not applicable	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important
Microsoft Office Excel 2007 Service Pack 2	Not applicable	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important
Microsoft Office for Mac
Microsoft Office for Mac 2004	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office for Mac 2008	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office Open XML File Converter for MAC	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Other Office Software
Microsoft Office Excel Viewer 2003 Service Pack 3	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office Excel Viewer	Not applicable	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2	Not applicable	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Moderate Remote Code Execution	Important
Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions)	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Important
Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions)	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Important

Record Pointer Corruption Vulnerability - CVE-2009-0549

A remote code execution vulnerability exists in Microsoft Office Excel that could allow remote code execution if a user opens a specially crafted Excel file that includes a malformed record object. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0549.

Mitigating Factors for Record Pointer Corruption Vulnerability - CVE-2009-0549

Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:

The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
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.
Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and later editions of Office.

Workarounds for Record Pointer Corruption Vulnerability - CVE-2009-0549

Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:

Use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or untrusted sources

The Microsoft Office Isolated Conversion Environment (MOICE) will protect Office 2003 installations by more securely opening Word, Excel, and PowerPoint binary format files.

To install MOICE, you must have Office 2003 or 2007 Office system installed.

To install MOICE, you must have the Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats. The compatibility pack is available as a free download from the Microsoft Download Center:

Download the FileFormatConverters.exe package now

MOICE requires all updates that are recommended for all Office programs. Visit Microsoft Update to install all recommended updates:

http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us

To enable MOICE, change the registered handler for the .xls, .xlt, and .xla file formats. The following table describes the command to enable or to disable MOICE for the .xls, .xlt, and .xla file formats:

Command to enable MOICE to be the registered handler	Command to disable MOICE as the registered handler
ASSOC .XLS=oice.excel.sheet	ASSOC .xls=Excel.Sheet.8
ASSOC .XLT=oice.excel.template	ASSOC .xlt=Excel.Template
ASSOC .XLA=oice.excel.addin	ASSOC .xla=Excel.Addin

Note On Windows Vista and Windows Server 2008, the commands above will need to be run from an elevated command prompt.

For more information on MOICE, see Microsoft Knowledge Base Article 935865.

Impact of workaround. Office 2003 and earlier formatted documents that are converted to the 2007 Microsoft Office System Open XML format by MOICE will not retain macro functionality. Additionally, documents with passwords or that are protected with Digital Rights Management cannot be converted.

Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents from unknown or untrusted sources and locations

The following registry scripts can be used to set the File Block policy.

Note Modifying the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from incorrect modification of the Registry can be solved. Modify the Registry at your own risk.
- For Office 2003 Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000001 Note In order to use 'FileOpenBlock' with Office 2003, all of the latest Office 2003 security updates must be applied.
Impact of workaround. Users who have configured the File Block policy and have not configured a special “exempt directory” as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.

How to undo the workaround:
- For Office 2003 Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000000
Do not open or save Excel files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.

FAQ for Record Pointer Corruption Vulnerability - CVE-2009-0549

What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system remotely. An attacker could then install programs or view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
The vulnerability exists in the way that Microsoft Office Excel parses the Excel spreadsheet file format that could allow remote code execution when opening a specially crafted Excel spreadsheet.

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

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Excel spreadsheet with an affected version of Microsoft Office Excel.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Excel file to the user and by convincing the user to open the file.

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. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince them to open the specially crafted Excel file.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office Excel is used, including workstations and terminal servers, are primarily at risk. Servers could be at more risk if administrators allow users to log on to servers and to run programs. However, best practices strongly discourage allowing this.

What does the update do?
This update addresses the vulnerability by changing the way that Microsoft Office Excel parses specially crafted Excel files.

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

Object Record Corruption Vulnerability - CVE-2009-0557

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0557.

Mitigating Factors for Object Record Corruption Vulnerability - CVE-2009-0557

The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
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.
Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and later editions of Office.

Workarounds for Object Record Corruption Vulnerability - CVE-2009-0557

Use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or un-trusted sources

The Microsoft Office Isolated Conversion Environment (MOICE) will protect Office 2003 installations by more securely opening Word, Excel, and PowerPoint binary format files.

To install MOICE, you must have Office 2003 or 2007 Office system installed.

To install MOICE, you must have the Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats. The compatibility pack is available as a free download from the Microsoft Download Center:

Download the FileFormatConverters.exe package now

MOICE requires all updates that are recommended for all Office programs. Visit Microsoft Update to install all recommended updates:

http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us

To enable MOICE, change the registered handler for the .xls, .xlt, and .xla file formats. The following table describes the command to enable or to disable MOICE for the .xls, .xlt, and .xla file formats:

Command to enable MOICE to be the registered handler	Command to disable MOICE as the registered handler
ASSOC .XLS=oice.excel.sheet	ASSOC .xls=Excel.Sheet.8
ASSOC .XLT=oice.excel.template	ASSOC .xlt=Excel.Template
ASSOC .XLA=oice.excel.addin	ASSOC .xla=Excel.Addin

Note On Windows Vista and Windows Server 2008, the commands above will need to be run from an elevated command prompt.

For more information on MOICE, see Microsoft Knowledge Base Article 935865.

Do not open or save Excel files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.

FAQ for Object Record Corruption Vulnerability - CVE-2009-0557

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Excel spreadsheet with an affected version of Microsoft Office Excel.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Excel file to the user and by convincing the user to open the file.

What does the update do?
This update addresses the vulnerability by changing the way that Microsoft Office Excel parses specially crafted Excel files.

Array Indexing Memory Corruption Vulnerability - CVE-2009-0558

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0558.

Mitigating Factors for Array Indexing Memory Corruption Vulnerability - CVE-2009-0558

The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
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.
Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and later editions of Office.

Workarounds for Array Indexing Memory Corruption Vulnerability - CVE-2009-0558

Do not open or save Excel files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.

FAQ for Array Indexing Memory Corruption Vulnerability - CVE-2009-0558

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Excel spreadsheet with an affected version of Microsoft Office Excel.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Excel file to the user and by convincing the user to open the file.

What does the update do?
This update addresses the vulnerability by changing the way that Microsoft Office Excel parses specially crafted Excel files.

String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0559.

Mitigating Factors for String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559

The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
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.
Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and later editions of Office.

Workarounds for String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559

Do not open or save Excel files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.

FAQ for String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Excel spreadsheet with an affected version of Microsoft Office Excel.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Excel file to the user and by convincing the user to open the file.

What does the update do?
This update addresses the vulnerability by changing the way that Microsoft Office Excel parses specially crafted Excel files.

Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0560.

Mitigating Factors for Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560

The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
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.
Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and later editions of Office.

Workarounds for Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560

Use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or untrusted sources

The Microsoft Office Isolated Conversion Environment (MOICE) will protect Office 2003 installations by more securely opening Word, Excel, and PowerPoint binary format files.

To install MOICE, you must have Office 2003 or 2007 Office system installed.

To install MOICE, you must have the Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats. The compatibility pack is available as a free download from the Microsoft Download Center:

Download the FileFormatConverters.exe package now

MOICE requires all updates that are recommended for all Office programs. Visit Microsoft Update to install all recommended updates:

http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us

To enable MOICE, change the registered handler for the .xls, .xlt, and .xla file formats. The following table describes the command to enable or to disable MOICE for the .xls, .xlt, and .xla file formats:

Command to enable MOICE to be the registered handler	Command to disable MOICE as the registered handler
ASSOC .XLS=oice.excel.sheet	ASSOC .xls=Excel.Sheet.8
ASSOC .XLT=oice.excel.template	ASSOC .xlt=Excel.Template
ASSOC .XLA=oice.excel.addin	ASSOC .xla=Excel.Addin

Note On Windows Vista and Windows Server 2008, the commands above will need to be run from an elevated command prompt.

For more information on MOICE, see Microsoft Knowledge Base Article 935865.

Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents from unknown or untrusted sources and locations

The following registry scripts can be used to set the File Block policy.

Note Modifying the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from incorrect modification of the Registry can be solved. Modify the Registry at your own risk.
- For Office 2003 Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000001 Note In order to use 'FileOpenBlock' with Office 2003, all of the latest Office 2003 security updates must be applied.
- For 2007 Office system Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000001 Note In order to use 'FileOpenBlock' with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.
Impact of workaround. Users who have configured the File Block policy and have not configured a special “exempt directory” as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.

How to undo the workaround:
- For Office 2003 Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000000
- For 2007 Office system Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000000

FAQ for Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Excel spreadsheet with an affected version of Microsoft Office Excel.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Excel file to the user and by convincing the user to open the file.

What does the update do?
This update addresses the vulnerability by changing the way that Microsoft Office Excel parses specially crafted Excel files.

Record Integer Overflow Vulnerability - CVE-2009-0561

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-0561.

Mitigating Factors for Record Integer Overflow Vulnerability - CVE-2009-0561

The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
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.
Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and later editions of Office.

Workarounds for Record Integer Overflow Vulnerability - CVE-2009-0561

Use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or untrusted sources

The Microsoft Office Isolated Conversion Environment (MOICE) will protect Office 2003 installations by more securely opening Word, Excel, and PowerPoint binary format files.

To install MOICE, you must have Office 2003 or 2007 Office system installed.

To install MOICE, you must have the Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats. The compatibility pack is available as a free download from the Microsoft Download Center:

Download the FileFormatConverters.exe package now

MOICE requires all updates that are recommended for all Office programs. Visit Microsoft Update to install all recommended updates:

http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us

To enable MOICE, change the registered handler for the .xls, .xlt, and .xla file formats. The following table describes the command to enable or to disable MOICE for the .xls, .xlt, and .xla file formats:

Command to enable MOICE to be the registered handler	Command to disable MOICE as the registered handler
ASSOC .XLS=oice.excel.sheet	ASSOC .xls=Excel.Sheet.8
ASSOC .XLT=oice.excel.template	ASSOC .xlt=Excel.Template
ASSOC .XLA=oice.excel.addin	ASSOC .xla=Excel.Addin

Note On Windows Vista and Windows Server 2008, the commands above will need to be run from an elevated command prompt.

For more information on MOICE, see Microsoft Knowledge Base Article 935865.

Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents from unknown or untrusted sources and locations

The following registry scripts can be used to set the File Block policy.

Note Modifying the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from incorrect modification of the Registry can be solved. Modify the Registry at your own risk.
- For Office 2003 Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000001 Note In order to use 'FileOpenBlock' with Office 2003, all of the latest Office 2003 security updates must be applied.
- For 2007 Office system Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000001 Note In order to use 'FileOpenBlock' with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.
Impact of workaround. Users who have configured the File Block policy and have not configured a special “exempt directory” as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.

How to undo the workaround:
- For Office 2003 Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000000
- For 2007 Office system Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000000
Do not open or save Excel files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.

FAQ for Record Integer Overflow Vulnerability - CVE-2009-0561

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Excel spreadsheet with an affected version of Microsoft Office Excel.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Excel file to the user and by convincing the user to open the file.

What does the update do?
This update addresses the vulnerability by changing the way that Microsoft Office Excel parses specially crafted Excel files.

Record Pointer Corruption Vulnerability - CVE-2009-1134

To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2009-1134.

Mitigating Factors for Record Pointer Corruption Vulnerability - CVE-2009-1134

The vulnerability cannot be exploited automatically through e-mail. For an attack to be successful, a user must open an attachment that is sent in an e-mail message.
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.
Users who have installed and are using the Office Document Open Confirmation Tool for Office 2000 will be prompted with Open, Save, or Cancel before opening a document. The features of the Office Document Open Confirmation Tool are incorporated in Office XP and later editions of Office.

Workarounds for Record Pointer Corruption Vulnerability - CVE-2009-1134

Use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or untrusted sources

The Microsoft Office Isolated Conversion Environment (MOICE) will protect Office 2003 installations by more securely opening Word, Excel, and PowerPoint binary format files.

To install MOICE, you must have Office 2003 or 2007 Office system installed.

To install MOICE, you must have the Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats. The compatibility pack is available as a free download from the Microsoft Download Center:

Download the FileFormatConverters.exe package now

MOICE requires all updates that are recommended for all Office programs. Visit Microsoft Update to install all recommended updates:

http://update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en-us

To enable MOICE, change the registered handler for the .xls, .xlt, and .xla file formats. The following table describes the command to enable or to disable MOICE for the .xls, .xlt, and .xla file formats:

Command to enable MOICE to be the registered handler	Command to disable MOICE as the registered handler
ASSOC .XLS=oice.excel.sheet	ASSOC .xls=Excel.Sheet.8
ASSOC .XLT=oice.excel.template	ASSOC .xlt=Excel.Template
ASSOC .XLA=oice.excel.addin	ASSOC .xla=Excel.Addin

Note On Windows Vista and Windows Server 2008, the commands above will need to be run from an elevated command prompt.

For more information on MOICE, see Microsoft Knowledge Base Article 935865.

Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents from unknown or untrusted sources and locations

The following registry scripts can be used to set the File Block policy.

Note Modifying the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from incorrect modification of the Registry can be solved. Modify the Registry at your own risk.
- For Office 2003 Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000001 Note In order to use 'FileOpenBlock' with Office 2003, all of the latest Office 2003 security updates must be applied.
- For 2007 Office system Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000001 Note In order to use 'FileOpenBlock' with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.
Impact of workaround. Users who have configured the File Block policy and have not configured a special “exempt directory” as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions in Office 2003 or 2007 Microsoft Office System.

How to undo the workaround:
- For Office 2003 Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000000
- For 2007 Office system Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\Security\FileOpenBlock] "BinaryFiles"=dword:00000000
- Do not open or save Excel files that you receive from untrusted sources or that you receive unexpectedly from trusted sources. This vulnerability could be exploited when a user opens a specially crafted file.

FAQ for Record Pointer Corruption Vulnerability - CVE-2009-1134

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open a specially crafted Excel spreadsheet with an affected version of Microsoft Office Excel.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted Excel file to the user and by convincing the user to open the file.

What does the update do?
This update addresses the vulnerability by changing the way that Microsoft Office Excel parses specially crafted Excel files.

Update Information

Detection and Deployment Tools and Guidance

Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.

Security updates are available from Microsoft Update, Windows Update, and Office Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."

Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.

Detection and Deployment Guidance

Microsoft has provided detection and deployment guidance for this month’s security updates. This guidance will also help IT professionals understand how they can use various tools to help deploy the security update, such as Windows Update, Microsoft Update, Office Update, the Microsoft Baseline Security Analyzer (MBSA), the Office Detection Tool, Microsoft Systems Management Server (SMS), and the Extended Security Update Inventory Tool. For more information, see Microsoft Knowledge Base Article 910723.

Microsoft Baseline Security Analyzer

Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.

The following table provides the MBSA detection summary for this security update.

Software	MBSA 2.1
Microsoft Office Excel 2000 Service Pack 3	No
Microsoft Office Excel 2002 Service Pack 3	Yes
Microsoft Office Excel 2003 Service Pack 3	Yes
Microsoft Office Excel 2007 Service Pack 1 and Microsoft Office Excel 2007 Service Pack 2	Yes
Microsoft Office 2004 for Mac	No
Microsoft Office 2008 for Mac	No
Open XML File Format Converter for Mac	No
Microsoft Office Excel Viewer 2003 Service Pack 3	Yes
Microsoft Office Excel Viewer	Yes
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2	Yes
Microsoft Works 8.5	Yes
Microsoft Works 9	Yes
Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions)	Yes
Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions)	Yes

For more information about MBSA 2.1, see MBSA 2.1 Frequently Asked Questions.

Note For customers using legacy software not supported by MBSA 2.1, Microsoft Update, and Windows Server Update Services: please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.

Windows Server Update Services

By using Windows Server Update Services (WSUS), administrators can deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site.

Systems Management Server

The following table provides the SMS detection and deployment summary for this security update.

Software	SMS 2.0	SMS 2003 with SUSFP	SMS 2003 with ITMU	Configuration Manager 2007
Microsoft Office Excel 2000 Service Pack 3	Yes	Yes	No	No
Microsoft Office Excel 2002 Service Pack 3	Yes	Yes	Yes	Yes
Microsoft Office Excel 2003 Service Pack 3	Yes	Yes	Yes	Yes
Microsoft Office Excel 2007 Service Pack 1 and Microsoft Office Excel 2007 Service Pack 2	No	No	Yes	Yes
Microsoft Office 2004 for Mac	No	No	No	No
Microsoft Office 2008 for Mac	No	No	No	No
Open XML File Format Converter for Mac	No	No	No	No
Microsoft Office Excel Viewer 2003 Service Pack 3	Yes	Yes	Yes	Yes
Microsoft Office Excel Viewer	No	No	Yes	Yes
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2	No	No	Yes	Yes
Microsoft Works 8.5	No	No	Yes	Yes
Microsoft Works 9	No	No	Yes	Yes
Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions)	No	No	Yes. See Note for Microsoft Office SharePoint Server 2007 below	Yes. See Note for Microsoft Office SharePoint Server 2007 below
Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions)	No	No	Yes. See Note for Microsoft Office SharePoint Server 2007 below	Yes. See Note for Microsoft Office SharePoint Server 2007 below

For SMS 2.0 and SMS 2003, the SMS SUS Feature Pack (SUSFP), which includes the Security Update Inventory Tool (SUIT), can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.

For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications. For more information about the Office Inventory Tool and other scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.

System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.

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

For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.

Note for Microsoft Office SharePoint Server 2007 The detection table described above is based on single-server Microsoft Office SharePoint Server 2007 deployments. The detection tools do not detect the applicability of the update on systems configured as part of a multiple-system SharePoint server farms. For more information about deploying updates on both stand-alone and multi server configurations, see Deploy software updates for Office SharePoint Server 2007.

Note If you have used an Administrative Installation Point (AIP) for deploying Office 2000, Office XP or Office 2003, you may not be able to deploy the update using SMS if you have updated the AIP from the original baseline. For more information, see the Office Administrative Installation Point heading in this section.

Office Administrative Installation Point

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

For supported versions of Microsoft Office 2000, see How to Create an Administrative Installation Point. For more information about how to change the source for a client system from an updated administrative installation point to an Office 2000 Service Pack 3 (SP3), see Microsoft Knowledge Base Article 932889. Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office 2000 Clients from a Patched Administrative Image.
For supported versions of Microsoft Office XP, see Creating an Administrative Installation Point. For more information on how to change the source for a client system from an updated administrative installation point to an Office XP original baseline source, see Microsoft Knowledge Base Article 922665. Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article Updating Office XP Clients from a Patched Administrative Image.
For supported versions of Microsoft Office 2003, see Creating an Administrative Installation Point. For more information on how to change the source for a client computer from an updated administrative installation point to an Office 2003 original baseline source or Service Pack 3 (SP3), see Microsoft Knowledge Base Article 902349. Note If you plan to manage software updates centrally from an updated administrative image, you can find more information in the article, Distributing Office 2003 Product Upgrades.
For supported versions of the 2007 Microsoft Office system, see Create a network installation point for the 2007 Office system. Note If you plan to manage security updates centrally, use Windows Server Update Services. For more information about how to deploy security updates for the 2007 Microsoft Office system using Windows Server Update Services, visit the Windows Server Update Services Web site.

Update Compatibility Evaluator and Application Compatibility Toolkit

Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit 5.0.

The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.

Security Update Deployment

Affected Software

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

Excel 2000 (all editions)

Reference Table

The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.

Inclusion in Future Service Packs	There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user intervention	office2000-kb969683-fullfile-enu /q:a
Installing without restarting	office2000-kb969683-fullfile-enu /r:n
Update log file	Not applicable
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. 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.
Hotpatching	Not applicable
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 media.
File Information	See Microsoft Knowledge Base Article 969683
Registry Key Verification	Not applicable

#### Office Features for Administrative Installations Server administrators who use a [Windows Installer Administrative Installation](http://go.microsoft.com/fwlink/?linkid=21685) must update the server location. For more information about Administrative Installation Points, refer to the **Office Administrative Installation Point** information in the **Detection and deployment Tools and Guidance** subsection. The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use **REINSTALL=ALL** or you can install the following features: | Product | Feature | |-----------------------------------------------------|------------| | O9EXL, O9PRM, O9PRO, O9SBE, O9PIPC1, O9PIPC2, O9STD | ExcelFiles | **Note** Administrators working in managed environments can find resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the **Update Resources** section for the software version you are updating. The [Windows Installer Documentation](http://go.microsoft.com/fwlink/?linkid=21685) also provides more information about the setup switches supported by Windows Installer. #### Deployment Information **Installing the Update** You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the **Office Administrative Installation Point** information in the **Detection and Deployment Tools and Guidance** subsection. This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version. To install the 2.0 or later version of Windows Installer, visit one of the following Microsoft Web sites: - [Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP](https://www.microsoft.com/download/details.aspx?familyid=5a58b56f-60b6-4412-95b9-54d056d6f9f4&displaylang=en) - [Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000](https://www.microsoft.com/download/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en) - [Windows Installer 2.0 Redistributable for Windows 2000 and Windows NT 4.0](http://go.microsoft.com/fwlink/?linkid=33338) For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684). This security update supports the following setup switches. | Switch | Description | |-------------|---------------------------------------------------------------------------------------------------------------------| | **/q** | Specifies quiet mode, or suppresses prompts, when files are being extracted. | | **/q:u** | Specifies user-quiet mode, which presents some dialog boxes to the user. | | **/q:a** | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. | | **/t:path** | Specifies the target folder for extracting files. | | **/c** | Extracts the files without installing them. If **/t:path** is not specified, you are prompted for a target folder. | | **/c:path** | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. | | **/r:n** | Never restarts the system after installation. | | **/r:I** | Prompts the user to restart the system if a restart is required, except when used with **/q:a**. | | **/r:a** | Always restarts the system after installation. | | **/r:s** | Restarts the system after installation without prompting the user. | | **/n:v** | No version checking - Install the program over any earlier version. | **Note** You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841). **Removing the Update** 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 media. **Verifying That the Update Has Been Applied** - **Microsoft Baseline Security Analyzer** To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, **Detection and Deployment Tools and Guidance**, earlier in this bulletin for more information. - **File Version Verification** Because there are several versions and editions of Microsoft Office, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. Click **Start**, and then click **Search**. 2. In the **Search Results** pane, click **All files and folders** under **Search Companion**. 3. In the **All or part of the file name** box, type a file name from the appropriate file information table, and then click **Search**. 4. In the list of files, right-click a file name from the appropriate file information table, and then click **Properties**. **Note** Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed. 5. On the **Version** tab, determine the version of the file that is installed on your system by comparing it to the version that is documented in the appropriate file information table. **Note** Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation. #### Excel 2002 (all editions) **Reference Table** The following table contains the security update information for this software. You can find additional information in the subsection, **Deployment Information**, in this section.

Inclusion in Future Service Packs	There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user intervention	officeXP-kb969680-fullfile-enu /q:a
Installing without restarting	officeXP-kb969680-fullfile-enu /r:n
Update log file	Not applicable
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. 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.
Hotpatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office XP CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
File Information	See Microsoft Knowledge Base Article 969680
Registry Key Verification	Not applicable

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

Inclusion in Future Service Packs	There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user intervention	For Excel 2003: office2003-kb969681-fullfile-enu /q:a For Excel Viewer 2003: office2003-kb969685-fullfile-enu /q:a
Installing without restarting	For Excel 2003: office2003-kb969681-fullfile-enu /r:n For Excel Viewer 2003: office2003-kb969685-fullfile-enu /r:n
Update log file	Not applicable
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. 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.
Hotpatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
File Information	For Excel 2003: See Microsoft Knowledge Base Article 969681 For Excel Viewer 2003: See Microsoft Knowledge Base Article 969685
Registry Key Verification	Not applicable

#### Office Features The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use **REINSTALL=ALL** or you can install the following features: | Product | Feature | |--------------------------------------------------------|-------------| | STD11, BASIC11, PERS11, STDP11, PROI11, PRO11, PRO11SB | All | | XLVIEW | ExcelViewer | **Note** Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the **Update Resources** section for the software version you are updating. The [Windows Installer Documentation](http://go.microsoft.com/fwlink/?linkid=21685) also provides more information about the parameters supported by Windows Installer. #### Deployment Information **Installing the Update** You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the **Office Administrative Installation Point** information in the **Detection and deployment Tools and Guidance** subsection. This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version. To install the 2.0 or later version of Windows Installer, visit one of the following Microsoft Web sites: - [Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP](https://www.microsoft.com/download/details.aspx?familyid=5a58b56f-60b6-4412-95b9-54d056d6f9f4&displaylang=en) - [Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000](https://www.microsoft.com/download/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en) - [Windows Installer 2.0 Redistributable for Windows 2000 and Windows NT 4.0](http://go.microsoft.com/fwlink/?linkid=33338) For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684). This security update supports the following setup switches. | Switch | Description | |-------------|---------------------------------------------------------------------------------------------------------------------| | **/q** | Specifies quiet mode, or suppresses prompts, when files are being extracted. | | **/q:u** | Specifies user-quiet mode, which presents some dialog boxes to the user. | | **/q:a** | Specifies administrator-quiet mode, which does not present any dialog boxes to the user. | | **/t:path** | Specifies the target folder for extracting files. | | **/c** | Extracts the files without installing them. If **/t:path** is not specified, you are prompted for a target folder. | | **/c:path** | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. | | **/r:n** | Never restarts the system after installation. | | **/r:I** | Prompts the user to restart the system if a restart is required, except when used with **/q:a**. | | **/r:a** | Always restarts the system after installation. | | **/r:s** | Restarts the system after installation without prompting the user. | | **/n:v** | No version checking - Install the program over any earlier version. | **Note** You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841). **Removing the Update** To remove this security update, use the Add or Remove Programs tool in Control Panel. **Note** When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see [Microsoft Knowledge Base Article 903771](http://support.microsoft.com/kb/903771). **Verifying that the Update Has Been Applied** - **Microsoft Baseline Security Analyzer** To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, **Detection and Deployment Tools and Guidance**, earlier in this bulletin for more information. - **File Version Verification** Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. Click **Start** and then enter an update file name in **Start Search**. 2. When the file appears under **Programs**, right-click on the file name and click **Properties**. 3. Under the **General** tab, compare the file size with the file information tables provided in the bulletin KB article. 4. You may also click on the **Details** tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 5. Finally, you may also click on the **Previous Versions** tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. #### Excel 2007 (all editions), Excel Viewer, and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats **Reference Table** The following table contains the security update information for this software. You can find additional information in the subsection, **Deployment Information**, in this section.

Inclusion in Future Service Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	For Excel 2007: excel2007-kb969682-fullfile-x86-glb /passive For Excel Viewer: ExcelViewer2007-kb969686-fullfile-x86-glb /passive For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats: office2007-kb969679-fullfile-x86-glb /passive
Installing without restarting	For Excel 2007: excel2007-kb969682-fullfile-x86-glb /norestart For Excel Viewer: ExcelViewer2007-kb969686-fullfile-x86-glb /norestart For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats: office2007-kb969679-fullfile-x86-glb /norestart
Update log file	Not applicable
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. 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.
Hotpatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel.
File Information	For Excel 2007: See Microsoft Knowledge Base Article 969682 For Excel Viewer: See Microsoft Knowledge Base Article 969686 For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats: See Microsoft Knowledge Base Article 969679
Registry Key Verification	Not applicable

#### Deployment Information **Installing the Update** You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the **Office Administrative Installation Point** information in the **Detection and deployment Tools and Guidance** subsection. This security update requires that Windows Installer 3.1 or later be installed on the system. To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites: - [Windows Installer 4.5 Redistributable for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP](https://www.microsoft.com/download/details.aspx?familyid=5a58b56f-60b6-4412-95b9-54d056d6f9f4&displaylang=en) - [Windows Installer 3.1 Redistributable for Windows Server 2003, Windows XP, and Windows 2000](https://www.microsoft.com/download/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en) For more information about the terminology that appears in this bulletin, such as *hotfix*, see [Microsoft Knowledge Base Article 824684](http://support.microsoft.com/kb/824684). This security update supports the following setup switches. | Switch | Description | |---------------------------|---------------------------------------------------------------------------------------------------------------------| | **/?** or **/help** | Displays usage dialog. | | **/passive** | Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel. | | **/quiet** | Specifies quiet mode, or suppresses prompts, when files are being extracted. | | **/norestart** | Suppresses restarting the system if the update requires a restart. | | **/forcerestart** | Automatically restarts the system after applying the update, regardless of whether the update requires the restart. | | **/extract** | Extracts the files without installing them. You are prompted for a target folder. | | **/extract:<path>** | Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file. | | **/lang:<LCID>** | Forces the use of a specific language, when the update package supports that language. | | **/log:<log file>** | Enables logging, by both Vnox and Installer, during the update installation. | **Note** You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841). **Removing the Update** To remove this security update, use the Add or Remove Programs tool in Control Panel. **Note** When you remove this update, you may be prompted to insert the 2007 Microsoft Office CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see [Microsoft Knowledge Base Article 903771](http://support.microsoft.com/kb/903771). **Verifying that the Update Has Been Applied** - **Microsoft Baseline Security Analyzer** To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, **Detection and Deployment Tools and Guidance**, earlier in this bulletin for more information. - **File Version Verification** Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps. 1. Click **Start** and then enter an update file name in **Start Search**. 2. When the file appears under **Programs**, right-click on the file name and click **Properties**. 3. Under the **General** tab, compare the file size with the file information tables provided in the bulletin KB article. 4. You may also click on the **Details** tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article. 5. Finally, you may also click on the **Previous Versions** tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file. #### Office 2004 for Mac #### Deployment Information **Prerequisites** - Mac OS X version 10.2.8 or later on a G3, Mac OS X-compatible processor or higher - Mac OS X user accounts must have administrator privileges to install this security update **Installing the Update** Download and install the appropriate language version of the Microsoft Office 2004 for Mac 11.5.5 Update from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?familyid=5557bfb7-ebb4-4c42-8042-41e830c4e550). - Quit any applications that are running, including virus-protection applications, all Microsoft Office applications, Microsoft Messenger for Mac, and Office Notifications, because they might interfere with installation. - Open the Microsoft Office 2004 for Mac 11.5.5 Update volume on your desktop. This step might have been performed for you. - To start the update process, in the Microsoft Office 2004 for Mac 11.5.5 Update volume window, double-click the Microsoft Office 2004 for Mac 11.5.5 Update application, and follow the instructions on the screen. - If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following “Verifying Update Installation” heading. To remove the update installer, first drag the Microsoft Office 2004 for Mac 11.5.5 Update volume to the Trash, and then drag the file that you downloaded to the Trash. **Verifying Update Installation** To verify that a security update is installed on an affected system, follow these steps: 1. In the Finder, navigate to the Application Folder (Microsoft Office 2004: Office). 2. Select the file, Microsoft Component Plugin. 3. On the File menu, click **Get Info** or **Show Info**. If the Version number is **11.5.5**, the update has been successfully installed. **Restart Requirement** This update does not require you to restart your computer. **Removing the Update** This security update cannot be uninstalled. **Additional Information** If you have technical questions or problems downloading or using this update, visit [Microsoft for Mac Support](http://www.microsoft.com/mac/support.aspx)to learn about the support options that are available to you. #### Office 2008 for Mac #### Deployment Information **Prerequisites** - Mac OS X version 10.4.9 or later on an Intel, PowerPC G5, or PowerPC G4 (500 MHz or faster) processor - Mac OS X user accounts must have administrator privileges to install this security update **Installing the Update** Download and install the appropriate language version of the Microsoft Office 2008 for Mac 12.1.9 Update from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?familyid=58326da2-eb75-4b42-b1bc-e70319defb58). - Quit any applications that are running, including virus-protection applications, all Microsoft Office applications, Microsoft Messenger for Mac, and Office Notifications, because they might interfere with installation. - Open the Microsoft Office 2008 for Mac 12.1.9 Update volume on your desktop. This step might have been performed for you. - To start the update process, in the Microsoft Office 2008 for Mac 12.1.9 Update volume window, double-click the Microsoft Office 2008 for Mac 12.1.9 Update application, and follow the instructions on the screen. - If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following “Verifying Update Installation” heading. To remove the update installer, first drag the Microsoft Office 2008 for Mac 12.1.9 Update volume to the Trash, and then drag the file that you downloaded to the Trash. **Verifying Update Installation** To verify that a security update is installed on an affected system, follow these steps: 1. In the Finder, navigate to the Application Folder (Microsoft Office 2008: Office). 2. Select the file, Microsoft Component Plugin. 3. On the File menu, click **Get Info** or **Show Info**. If the Version number is **12.1.9**, the update has been successfully installed. **Restart Requirement** This update does not require you to restart your computer. **Removing the Update** This security update cannot be uninstalled. **Additional Information** If you have technical questions or problems downloading or using this update, visit [Microsoft for Mac Support](http://www.microsoft.com/mac/support.aspx)to learn about the support options that are available to you. #### Open XML File Converter For Mac #### Deployment Information **Prerequisites** - Mac OS X version 10.4.9 or later on an Intel, PowerPC G5, or PowerPC G4 (500 MHz or faster) processor - Mac OS X user accounts must have administrator privileges to install this security update **Installing the Update** Download and install the appropriate language version of the Open XML File Converter for Mac 1.0.3 Update from the [Microsoft Download Center](https://www.microsoft.com/download/details.aspx?familyid=9d6d9eaa-8442-4184-8886-faab2803bde6). - Quit any applications that are running, including virus-protection applications, all Microsoft Office applications, Microsoft Messenger for Mac, and Office Notifications, because they might interfere with installation. - Open the Open XML File Converter for Mac 1.0.3 Update volume on your desktop. This step might have been performed for you. - To start the update process, in the Open XML File Converter for Mac 1.0.3 Update volume window, double-click the Open XML File Converter for Mac 1.0.3 Update application, and follow the instructions on the screen. - If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following “Verifying Update Installation” heading. To remove the update installer, first drag the Open XML File Converter for Mac 1.0.3 Update volume to the Trash, and then drag the file that you downloaded to the Trash. **Verifying Update Installation** To verify that a security update is installed on an affected system, follow these steps: 1. In the Finder, navigate to the Application Folder (Open XML File Converter for Mac : Office). 2. Select the file, Microsoft Component Plugin. 3. On the File menu, click **Get Info** or **Show Info**. If the Version number is 1.0.3, the update has been successfully installed. **Restart Requirement** This update does not require you to restart your computer. **Removing the Update** This security update cannot be uninstalled. **Additional Information** If you have technical questions or problems downloading or using this update, visit [Microsoft for Mac Support](http://www.microsoft.com/mac/support.aspx)to learn about the support options that are available to you. #### SharePoint Server 2007 (all editions) **Reference Table** The following table contains the security update information for this software. You can find additional information in the subsection, **Deployment Information**, in this section.

Inclusion in Future Service Packs	There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user intervention	For Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions): office2007-kb969737-fullfile-x86-glb /passive For Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions): office2007-kb969737-fullfile-x64-glb /passive
Installing without restarting	For Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions): office2007-kb969737-fullfile-x86-glb /norestart For Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions): office2007-kb969737-fullfile-x64-glb /norestart
Update log file	Not applicable
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart. 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.
Hotpatching	Not applicable
Removal Information	This security update cannot be removed.
File Information	See Microsoft Knowledge Base Article 969737
Registry Key Verification	Not applicable

Affected Software	Record Pointer Corruption Vulnerability - CVE-2009-0549	Object Record Corruption Vulnerability - CVE-2009-0557	Array Indexing Memory Corruption Vulnerability - CVE-2009-0558	String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559	Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560	Record Integer Overflow Vulnerability - CVE-2009-0561	Record Pointer Corruption Vulnerability - CVE-2009-1134	Aggregate Severity Rating
Microsoft Office Suites and Components
Microsoft Office Excel 2000 Service Pack 3	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Critical Remote Code Execution	Not applicable	Critical
Microsoft Office Excel 2002 Service Pack 3	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office Excel 2003 Service Pack 3	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office Excel 2007 Service Pack 1	Not applicable	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important
Microsoft Office Excel 2007 Service Pack 2	Not applicable	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important
Microsoft Office for Mac
Microsoft Office for Mac 2004	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office for Mac 2008	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office Open XML File Converter for MAC	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Other Office Software
Microsoft Office Excel Viewer 2003 Service Pack 3	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Not applicable	Important
Microsoft Office Excel Viewer	Not applicable	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 1 and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2	Not applicable	Important Remote Code Execution	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Moderate Remote Code Execution	Important
Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (32-bit editions)	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Important
Microsoft Office SharePoint Server 2007 Service Pack 1 and Microsoft Office SharePoint Server 2007 Service Pack 2 (64-bit editions)	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Important

Microsoft Security Bulletin MS09-021 - Critical

Vulnerabilities in Microsoft Office Excel Could Allow Remote Code Execution (969462)

General Information

Executive Summary

Affected and Non-Affected Software

Frequently Asked Questions (FAQ) Related to This Security Update

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

Record Pointer Corruption Vulnerability - CVE-2009-0549

Mitigating Factors for Record Pointer Corruption Vulnerability - CVE-2009-0549

Workarounds for Record Pointer Corruption Vulnerability - CVE-2009-0549

FAQ for Record Pointer Corruption Vulnerability - CVE-2009-0549

Object Record Corruption Vulnerability - CVE-2009-0557

Mitigating Factors for Object Record Corruption Vulnerability - CVE-2009-0557

Workarounds for Object Record Corruption Vulnerability - CVE-2009-0557

FAQ for Object Record Corruption Vulnerability - CVE-2009-0557

Array Indexing Memory Corruption Vulnerability - CVE-2009-0558

Mitigating Factors for Array Indexing Memory Corruption Vulnerability - CVE-2009-0558

Workarounds for Array Indexing Memory Corruption Vulnerability - CVE-2009-0558

FAQ for Array Indexing Memory Corruption Vulnerability - CVE-2009-0558

String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559

Mitigating Factors for String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559

Workarounds for String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559

FAQ for String Copy Stack-Based Overrun Vulnerability - CVE-2009-0559

Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560

Mitigating Factors for Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560

Workarounds for Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560

FAQ for Field Sanitization Memory Corruption Vulnerability - CVE-2009-0560

Record Integer Overflow Vulnerability - CVE-2009-0561

Mitigating Factors for Record Integer Overflow Vulnerability - CVE-2009-0561

Workarounds for Record Integer Overflow Vulnerability - CVE-2009-0561

FAQ for Record Integer Overflow Vulnerability - CVE-2009-0561

Record Pointer Corruption Vulnerability - CVE-2009-1134

Mitigating Factors for Record Pointer Corruption Vulnerability - CVE-2009-1134

Workarounds for Record Pointer Corruption Vulnerability - CVE-2009-1134

FAQ for Record Pointer Corruption Vulnerability - CVE-2009-1134

Update Information

Detection and Deployment Tools and Guidance

Security Update Deployment

Excel 2000 (all editions)