Security Bulletin

Microsoft Security Bulletin MS10-087 - Critical

Vulnerabilities in Microsoft Office Could Allow Remote Code Execution (2423930)

Published: November 09, 2010 | Updated: April 12, 2011

Version: 2.1

General Information

Executive Summary

This security update resolves one publicly disclosed vulnerability and five privately reported vulnerabilities in Microsoft Office. The most severe vulnerability could allow remote code execution if a user opens or previews a specially crafted RTF e-mail message. An attacker who successfully exploited any of these vulnerabilities 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.

This security update is rated Critical for all supported editions of Microsoft Office 2007 and Microsoft Office 2010. This security update is also rated Important for all supported editions of Microsoft Office XP, Microsoft Office 2003, Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, and Microsoft Office for Mac 2011; and Open XML File Format Converter for Mac. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The update addresses the vulnerabilities by modifying the way that Microsoft Office software parses files and by helping to ensure a vulnerable component of Microsoft Office uses a more appropriate and secure search order when loading libraries. 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 2423930 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues. When currently known issues and recommended solutions pertain only to specific releases of this software, this article provides links to further articles.

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

Microsoft Office Suite and Other Software Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Microsoft Office Suites
Microsoft Office XP Service Pack 3 (KB2289169) Remote Code Execution Important MS10-003
Microsoft Office 2003 Service Pack 3 (KB2289187) Remote Code Execution Important MS10-036
Microsoft Office 2007 Service Pack 2 (KB2289158) Remote Code Execution Critical MS10-036
Microsoft Office 2010 (32-bit editions) (KB2289161) Remote Code Execution Critical None
Microsoft Office 2010 (64-bit editions) (KB2289161) Remote Code Execution Critical None
Microsoft Office for Mac
Microsoft Office 2004 for Mac[1] Remote Code Execution Important None
Microsoft Office 2008 for Mac (KB2476512) Remote Code Execution Important MS10-079
Microsoft Office for Mac 2011 (KB2454823) Remote Code Execution Important None
Open XML File Format Converter for Mac (KB2476511) Remote Code Execution Important MS10-079

[1]The security update for Microsoft Office 2004 for Mac (KB2505924) is available as of April 12, 2011. See the entry to the section, Frequently Asked Questions (FAQ) Related to This Security Update, that explains how to obtain this update.

Non-Affected Software

Office and Other Software
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2
Microsoft Word Viewer
Microsoft Excel Viewer Service Pack 2
Microsoft PowerPoint Viewer Service Pack 2
Microsoft Visio 2007 Viewer Service Pack 2
Microsoft Visio 2010 Viewer
Microsoft Works 9

Why was this bulletin revised on April 12, 2011?
Microsoft revised this bulletin to announce that the security update for Microsoft Office 2004 for Mac (KB2505924) offered in the MS11-021, MS11-022, and MS11-023 security bulletins also addresses the vulnerabilities described in this security bulletin in addition to the vulnerabilities described in the respective bulletins. Although the KB2505924 update package is offered in three separate security bulletins, users with Microsoft Office 2004 for Mac installed will only need to install the security update package once. See MS11-021, MS11-022, or MS11-023 for more information and download links.

Why was this bulletin revised on December 15, 2010?
Microsoft revised this bulletin to announce the availability of the security updates for Microsoft Office 2008 for Mac (KB2476512) and Open XML File Format Converter for Mac (KB2476511). Microsoft recommends that users of Microsoft Office 2008 for Mac and Open XML File Format Converter for Mac apply these updates at the earliest opportunity to address the vulnerabilities described in this bulletin. The update for Microsoft Office 2004 for Mac remains unavailable at this time.

Why was this bulletin revised on November 17, 2010?
Microsoft revised this bulletin to add CVE-2010-2573 to the vulnerabilities addressed by this update. For Microsoft PowerPoint 2002 and Microsoft PowerPoint 2003, CVE-2010-2573 is also addressed by the Microsoft Office update provided in this bulletin (MS10-087). This is an informational change only. Customers who have already successfully applied the MS10-087 and the MS10-088 updates do not need to take any action.

Where is the update for Microsoft Office 2004 for Mac?
The Microsoft Office 2004 for Mac (KB2505924) update offered in the MS11-021, MS11-022, and MS11-023 security bulletins also addresses the vulnerabilities described in this security bulletin in addition to the vulnerabilities described in the respective bulletins. Although the KB2505924 update package is offered in three separate security bulletins, users with Microsoft Office 2004 for Mac installed will only need to install the security update package once. See MS11-021, MS11-022, or MS11-023 for more information and download links.

How does MS10-088 relate to this bulletin (MS10-087)?
CVE-2010-2573 is addressed in both this bulletin (MS10-087) and in MS10-088, Vulnerabilities in Microsoft PowerPoint Could Allow Remote Code Execution (2293386). For Microsoft PowerPoint 2002 and Microsoft PowerPoint 2003, this update (MS10-087) addresses the vulnerability. MS10-088 addresses all other software, including PowerPoint viewers, affected by CVE-2010-2573.

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.

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.

How is Microsoft Office Outlook affected by these vulnerabilities?
Outlook is not directly affected because the vulnerabilities can only be exploited through Microsoft Word. If Word is the selected e-mail reader, which is the default setting in Microsoft Outlook 2007 and Microsoft Outlook 2010, then an attacker could leverage Outlook for the e-mail attack vector by sending a specially crafted RTF e-mail message to the target user. In this scenario this attack vector requires minimal user action (as in viewing a specially crafted e-mail through the preview pane in Outlook) to be exploited.

How are Microsoft Office standalone programs affected by the vulnerabilities?
A Microsoft Office standalone program is affected with the same severity rating as the corresponding Microsoft Office Suite. For example, a standalone installation of Microsoft Word is affected with the same severity rating as an installation of the affected Microsoft Office Suite.

I have a non-vulnerable version of software installed, why am I being offered this update?
Some non-affected software, including Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats, Microsoft Word Viewer, Microsoft Excel Viewer, and Microsoft PowerPoint Viewer, contain the vulnerable shared component of Microsoft Office, but because they do not access the vulnerable code, they are not affected by this vulnerability. However, since the vulnerable code is present, this update will be offered.

Does the offer to update a non-vulnerable version of Microsoft Office constitute an issue in the Microsoft update mechanism?
No, the update mechanism is functioning correctly in that it detects a lower version of the files on the system than in the update package and thus, offers the update.

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. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.

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. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.

Customers who require custom support for older software 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 the Microsoft Worldwide Information Web site, select the country in the Contact Information list, 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 Microsoft Support Lifecycle Policy 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 November bulletin summary. For more information, see Microsoft Exploitability Index.

Affected Software PowerPoint Integer Underflow Causes Heap Corruption Vulnerability - CVE-2010-2573 RTF Stack Buffer Overflow Vulnerability - CVE-2010-3333 Office Art Drawing Records Vulnerability - CVE-2010-3334 Drawing Exception Handling Vulnerability - CVE-2010-3335 MSO Large SPID Read AV Vulnerability - CVE-2010-3336 Insecure Library Loading Vulnerability - CVE-2010-3337 Aggregate Severity Rating
Microsoft Office Suites
Microsoft Office XP Service Pack 3 Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Not applicable Important
Microsoft Office 2003 Service Pack 3 Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Not applicable Not applicable Important
Microsoft Office 2007 Service Pack 2 Not applicable Critical  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Not applicable Important  Remote Code Execution Critical
Microsoft Office 2010 (32-bit editions) Not applicable Critical Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Not applicable Important  Remote Code Execution Critical
Microsoft Office 2010 (64-bit editions) Not applicable Critical  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Not applicable Important  Remote Code Execution Critical
Microsoft Office for Mac
Microsoft Office 2004 for Mac Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Not applicable Important
Microsoft Office 2008 for Mac Not applicable Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Not applicable Important
Microsoft Office for Mac 2011 Not applicable Important  Remote Code Execution Not applicable Important  Remote Code Execution Important  Remote Code Execution Not applicable Important
Open XML File Format Converter for Mac Not applicable Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Important  Remote Code Execution Not applicable Important

PowerPoint Integer Underflow Causes Heap Corruption Vulnerability - CVE-2010-2573

A remote code execution vulnerability exists in the way that Microsoft PowerPoint handles specially crafted PowerPoint files. 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-2010-2573.

Mitigating Factors for PowerPoint Integer Underflow Causes Heap Corruption Vulnerability - CVE-2010-2573

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.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site, and then convince them to open the specially crafted PowerPoint file.

Workarounds for PowerPoint Integer Underflow Causes Heap Corruption Vulnerability - CVE-2010-2573

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 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\PowerPoint\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.

    Alternatively, file block can be applied using Group Policy. For more information, see the TechNet article, Plan file block settings for Office 2010.

    Impact of workaround. For Microsoft Office 2003 and Microsoft Office 2007, 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. For Microsoft Office 2007, Office 2003 or earlier versions will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected.

    How to undo the workaround.

    For Office 2003

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\PowerPoint\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    
  • Use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or untrusted sources

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

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

    To install MOICE, you must also 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.

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

    Enable MOICE

    Note See Microsoft Knowledge Base Article 935865 to use the automated Microsoft Fix it solution to enable or disable this workaround.

    To manually enable MOICE, run the commands as specified in the following table. Running the commands will associate the Office application extensions with MOICE.

Command to enable MOICE to be the registered handler
For Word, run the following command from a command prompt:\ ASSOC .doc=oice.word.document
For Excel, run the following commands from a command prompt:\ ASSOC .XLS=oice.excel.sheet\ ASSOC .XLT=oice.excel.template\ ASSOC .XLA=oice.excel.addin
For PowerPoint, run the following commands from a command prompt:\ ASSOC .PPT=oice.powerpoint.show\ ASSOC .POT=oice.powerpoint.template\ ASSOC .PPS=oice.powerpoint.slideshow

Note On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands 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 Microsoft Office 2007 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.

How to undo the workaround. Run the commands to disable MOICE as specified in the table below.

Command to disable MOICE as the registered handler
For Word, run the following command from a command prompt:\ ASSOC .doc=Word.Document.8
For Excel, run the following commands from a command prompt:\ ASSOC .xls=Excel.Sheet.8\ ASSOC .xlt=Excel.Template\ ASSOC .xla=Excel.Addin
For PowerPoint, run the following commands from a command prompt:\ ASSOC .ppt=PowerPoint.Show.8\ ASSOC .PPS=oice.powerpoint.slideshow\ ASSOC .pps=PowerPoint.SlideShow.8

Note On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands from an elevated command prompt.

  • Do not open PowerPoint files from untrusted sources

    Do not open or save PowerPoint 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 PowerPoint Integer Underflow Causes Heap Corruption Vulnerability - CVE-2010-2573

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 because of the way that Microsoft PowerPoint parses the PowerPoint file format when opening a specially crafted PowerPoint file.

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?
The vulnerability exists because of the way that Microsoft PowerPoint parses the PowerPoint file format when opening a specially crafted PowerPoint file.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending a specially crafted PowerPoint 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 a PowerPoint 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 PowerPoint file.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft PowerPoint 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 PowerPoint parses specially crafted PowerPoint files.

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

RTF Stack Buffer Overflow Vulnerability - CVE-2010-3333

A remote code execution vulnerability exists in the way that affected Microsoft Office software parses specially crafted Rich Text Format (RTF) data. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

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

Mitigating Factors for RTF Stack Buffer Overflow Vulnerability - CVE-2010-3333

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:

  • An attacker who successfully exploited this vulnerability could gain the same user rights as the logged-on user. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site, and then convince them to open the specially crafted Office file.

Workarounds for RTF Stack Buffer Overflow Vulnerability - CVE-2010-3333

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:

  • Read e-mails in plain text

    To help protect yourself from the e-mail attack vector, read e-mail messages in plain text format.

    Microsoft Office Outlook 2002 users who have applied Office XP Service Pack 1 or a later version can enable this setting and view in plain text only those e-mail messages that are not digitally signed or e-mail messages that are not encrypted.

    Digitally signed e-mail messages or encrypted e-mail messages are not affected by the setting and may be read in their original formats. For more information about how to enable this setting in Outlook 2002, see Microsoft Knowledge Base Article 307594.

    Impact of workaround. E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:

    • The changes are applied to the preview pane and to open messages.
    • Pictures become attachments so that they are not lost.
    • Because the message is still in Rich Text or HTML format in the store, the object model (custom code solutions) may behave unexpectedly.
  • Use Microsoft Office File Block policy to block the opening of RTF 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\Word\Security\FileOpenBlock]
    
    "RtfFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.

    For Office 2007 

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
    
    "RtfFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Microsoft Office 2007, all of the latest security updates for Microsoft Office 2007 must be applied.

    For Office 2010  Open Word 2010 and follow the steps below:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Ensure the Open check box is selected for the following file types:
      • RTF Files
    6. Under Open behavior for selected file types, select "Do not open selected file types" or select "Open selected file types in Protected View". Either choice will block the attack vector to the vulnerable code.
    7. Click OK to apply the File Block Settings.

    Alternatively, file block can be applied using Group Policy. For more information, see the TechNet article, Plan file block settings for Office 2010.

    Impact of workaround. Users who have configured the File Block policy and have not configured a special exempt directory or have not moved files to a trusted location as discussed in Microsoft Knowledge Base Article 922848 will be unable to open RTF files in Office 2003 or 2007 Microsoft Office System. For Microsoft Office 2010, RTF files will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected.

    How to undo the workaround.

    For Office 2003

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Security\FileOpenBlock]
    
    "RtfFiles"=dword:00000000
    

    For 2007 Office system

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
    
    "RtfFiles"=dword:00000000
    

    For Office 2010  Open Word 2010 and follow these steps:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Clear the Open check box for the file types that you previously selected.
    6. Click OK to apply the File Block settings.

FAQ for RTF Stack Buffer Overflow Vulnerability - CVE-2010-3333

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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
When Microsoft Office software parses specially crafted RTF-formatted data, system memory may be corrupted in such a way that an attacker could execute arbitrary code.

What is RTF?
Rich Text Format (RTF) is a method of encoding formatted text and graphics for use within applications and for transfer between applications. Users often depend on special translation software to move word-processing documents between various applications developed by different companies. RTF serves as both a standard of data transfer between word processing software, document formatting, and a means of migrating content from one operating system to another.

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

How could an attacker exploit the vulnerability?
This vulnerability requires that a user open or preview specially crafted RTF-formatted data with an affected version of Microsoft Office software.

In an e-mail attack scenario, an attacker could exploit the vulnerability by sending specially-crafted RTF-formatted data in the contents of an e-mail message. The vulnerability could be exploited when the specially crafted RTF e-mail message is previewed or opened in Outlook while using Word as the e-mail viewer. An attacker could also exploit the vulnerability by sending a specially-crafted RTF file as an attachment and convincing the user to open the specially crafted RTF file.

In a Web-based attack scenario, an attacker could 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 Office file.

How is Microsoft Office affected by this vulnerability?
Although the known attack vectors can only leverage Microsoft Word, the vulnerable code exists in a shared component of Microsoft Office.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office software 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?
The update addresses the vulnerability by modifying the way that Microsoft Office parses RTF-formatted data.

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Office Art Drawing Records Vulnerability - CVE-2010-3334

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

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

Mitigating Factors for Office Art Drawing Records Vulnerability - CVE-2010-3334

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.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site, and then convince them to open the specially crafted Office file.

Workarounds for Office Art Drawing Records Vulnerability - CVE-2010-3334

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 Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents in Microsoft Word 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\Word\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.

    For Office 2007 

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Office 2007, all of the latest security updates for Microsoft Office 2007 must be applied.

    For Office 2010  Open Word 2010 and follow the steps below:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Ensure the Open check box is selected for the following file types:
      • Word 2003 Binary Documents and Templates
      • Word XP Binary Documents and Templates
      • Word 2000 Binary Documents and Templates
      • Word 97 Binary Documents and Templates
      • Word 95 Binary Documents and Templates
      • Word 6.0 Binary Documents and Templates
      • Word 2 and earlier Binary Documents and Templates
    6. Under Open behavior for selected file types, select "Do not open selected file types" or select "Open selected file types in Protected View". Either choice will block the attack vector to the vulnerable code.
    7. Click OK to apply the File Block Settings.

    Alternatively, file block can be applied using Group Policy. For more information, see the TechNet article, Plan file block settings for Office 2010.

    Impact of workaround. For Microsoft Office 2003 and Microsoft Office 2007, users who have configured the File Block policy and have not configured a special exempt directory or have not moved files to a trusted location as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions. For Microsoft Office 2010, Office 2003 files or earlier versions will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected.

    How to undo the workaround.

    For Office 2003

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2007

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2010  Open Word 2010 and follow these steps:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Clear the Open check box for the file types that you previously selected.
    6. Click OK to apply the File Block settings.
  • Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents in Microsoft Excel 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 Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.

    For Office 2007 

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Excel\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Microsoft Office 2007, all of the latest security updates for Office 2007 must be applied.

    For Office 2010  Open Excel 2010 and follow the steps below:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Ensure the Open check box is selected for the following file types:
      • Excel 2007 and later Binary Workbooks
      • Excel 97-2003 Add-in Files
      • Excel 97-2003 Workbooks and Templates
      • Excel 95-97 Workbooks and Templates
      • Excel 95 Workbooks
      • Excel 4 Workbooks
      • Excel 4 Worksheets
      • Excel 3 Worksheets
      • Excel 2 Worksheets
    6. Under Open behavior for selected file types, select "Do not open selected file types" or select "Open selected file types in Protected View". Either choice will block the attack vector to the vulnerable code.
    7. Click OK to apply the File Block Settings.

    Alternatively, file block can be applied using Group Policy. For more information, see the TechNet article, Plan file block settings for Office 2010.

    Impact of workaround. For Microsoft Office 2003 and Microsoft Office 2007, users who have configured the File Block policy and have not configured a special exempt directory or have not moved files to a trusted location as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions. For Microsoft Office 2010, Office 2003 files or earlier versions will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected.

    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 Office 2007

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Excel\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2010  Open Excel 2010 and follow these steps:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Clear the Open check box for the file types that you previously selected.
    6. Click OK to apply the File Block settings.
  • Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents in Microsoft PowerPoint 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\PowerPoint\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.

    For Office 2007 

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\PowerPoint\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.

    For Office 2010  Open PowerPoint 2010 and follow the steps below:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Ensure the Open check box is selected for the following file types:
      • PowerPoint 97-2003 Presentations, Shows, Templates and Add-in Files
    6. Under Open behavior for selected file types, select "Do not open selected file types" or select "Open selected file types in Protected View". Either choice will block the attack vector to the vulnerable code.
    7. Click OK to apply the File Block Settings.

    Alternatively, file block can be applied using Group Policy. For more information, see the TechNet article, Plan file block settings for Office 2010.

    Impact of workaround. For Microsoft Office 2003 and Microsoft Office 2007, users who have configured the File Block policy and have not configured a special exempt directory or have not moved files to a trusted location as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions. For Microsoft Office 2010, Office 2003 files or earlier versions will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected.

    How to undo the workaround.

    For Office 2003

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\PowerPoint\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2007

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\PowerPoint\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2010  Open PowerPoint 2010 and follow these steps:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Clear the Open check box for the file types that you previously selected.
    6. Click OK to apply the File Block settings.
  • Use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or untrusted sources

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

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

    To install MOICE, you must also 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.

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

    Enable MOICE

    Note See Microsoft Knowledge Base Article 935865 to use the automated Microsoft Fix it solution to enable or disable this workaround.

    To manually enable MOICE, run the commands as specified in the following table. Running the commands will associate the Office application extensions with MOICE.

Command to enable MOICE to be the registered handler
For Word, run the following command from a command prompt:\ ASSOC .doc=oice.word.document
For Excel, run the following commands from a command prompt:\ ASSOC .XLS=oice.excel.sheet\ ASSOC .XLT=oice.excel.template\ ASSOC .XLA=oice.excel.addin
For PowerPoint, run the following commands from a command prompt:\ ASSOC .PPT=oice.powerpoint.show\ ASSOC .POT=oice.powerpoint.template\ ASSOC .PPS=oice.powerpoint.slideshow

Note On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands 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 Microsoft Office 2007 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.

How to undo the workaround. Run the commands to disable MOICE as specified in the table below.

Command to disable MOICE as the registered handler
For Word, run the following command from a command prompt:\ ASSOC .doc=Word.Document.8
For Excel, run the following commands from a command prompt:\ ASSOC .xls=Excel.Sheet.8\ ASSOC .xlt=Excel.Template\ ASSOC .xla=Excel.Addin
For PowerPoint, run the following commands from a command prompt:\ ASSOC .ppt=PowerPoint.Show.8\ ASSOC .PPS=oice.powerpoint.slideshow\ ASSOC .pps=PowerPoint.SlideShow.8

Note On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands from an elevated command prompt.

  • Do not open Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources

    Do not open Office 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 Office Art Drawing Records Vulnerability - CVE-2010-3334

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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
When a user opens a specially crafted Office file, system memory may become corrupted in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged-on with administrative user rights, an attacker could take complete control of the affected system. 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 Office file with an affected version of Microsoft Office software.

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

In a Web-based attack scenario, an attacker could 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 Office file.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office software 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?
The update addresses the vulnerability by modifying the way that Microsoft Office software parses files.

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Drawing Exception Handling Vulnerability - CVE-2010-3335

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

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

Mitigating Factors for Drawing Exception Handling Vulnerability - CVE-2010-3335

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.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site, and then convince them to open the specially crafted Office file.

Workarounds for Drawing Exception Handling Vulnerability - CVE-2010-3335

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 Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents in Microsoft Word 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\Word\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.

    For Office 2007 

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Office 2007, all of the latest security updates for Microsoft Office 2007 must be applied.

    For Office 2010  Open Word 2010 and follow the steps below:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Ensure the Open check box is selected for the following file types:
      • Word 2003 Binary Documents and Templates
      • Word XP Binary Documents and Templates
      • Word 2000 Binary Documents and Templates
      • Word 97 Binary Documents and Templates
      • Word 95 Binary Documents and Templates
      • Word 6.0 Binary Documents and Templates
      • Word 2 and earlier Binary Documents and Templates
    6. Under Open behavior for selected file types, select "Do not open selected file types" or select "Open selected file types in Protected View". Either choice will block the attack vector to the vulnerable code.
    7. Click OK to apply the File Block Settings.

    Alternatively, file block can be applied using Group Policy. For more information, see the TechNet article, Plan file block settings for Office 2010.

    Impact of workaround. For Microsoft Office 2003 and Microsoft Office 2007, users who have configured the File Block policy and have not configured a special exempt directory or have not moved files to a trusted location as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions. For Microsoft Office 2010, Office 2003 files or earlier versions will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected.

    How to undo the workaround.

    For Office 2003

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2007

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2010  Open Word 2010 and follow these steps:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Clear the Open check box for the file types that you previously selected.
    6. Click OK to apply the File Block settings.
  • Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents in Microsoft Excel 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 Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.

    For Office 2007 

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Excel\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Microsoft Office 2007, all of the latest security updates for Office 2007 must be applied.

    For Office 2010  Open Excel 2010 and follow the steps below:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Ensure the Open check box is selected for the following file types:
      • Excel 2007 and later Binary Workbooks
      • Excel 97-2003 Add-in Files
      • Excel 97-2003 Workbooks and Templates
      • Excel 95-97 Workbooks and Templates
      • Excel 95 Workbooks
      • Excel 4 Workbooks
      • Excel 4 Worksheets
      • Excel 3 Worksheets
      • Excel 2 Worksheets
    6. Under Open behavior for selected file types, select "Do not open selected file types" or select "Open selected file types in Protected View". Either choice will block the attack vector to the vulnerable code.
    7. Click OK to apply the File Block Settings.

    Alternatively, file block can be applied using Group Policy. For more information, see the TechNet article, Plan file block settings for Office 2010.

    Impact of workaround. For Microsoft Office 2003 and Microsoft Office 2007, users who have configured the File Block policy and have not configured a special exempt directory or have not moved files to a trusted location as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions. For Microsoft Office 2010, Office 2003 files or earlier versions will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected.

    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 Office 2007

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Excel\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2010  Open Excel 2010 and follow these steps:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Clear the Open check box for the file types that you previously selected.
    6. Click OK to apply the File Block settings.
  • Use Microsoft Office File Block policy to block the opening of Office 2003 and earlier documents in Microsoft PowerPoint 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\PowerPoint\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000001
    

    Note In order to use 'FileOpenBlock' with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.

    For Office 2007 

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\PowerPoint\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.

    For Office 2010  Open PowerPoint 2010 and follow the steps below:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Ensure the Open check box is selected for the following file types:
      • PowerPoint 97-2003 Presentations, Shows, Templates and Add-in Files
    6. Under Open behavior for selected file types, select "Do not open selected file types" or select "Open selected file types in Protected View". Either choice will block the attack vector to the vulnerable code.
    7. Click OK to apply the File Block Settings.

    Alternatively, file block can be applied using Group Policy. For more information, see the TechNet article, Plan file block settings for Office 2010.

    Impact of workaround. For Microsoft Office 2003 and Microsoft Office 2007, users who have configured the File Block policy and have not configured a special exempt directory or have not moved files to a trusted location as discussed in Microsoft Knowledge Base Article 922848 will be unable to open Office 2003 files or earlier versions. For Microsoft Office 2010, Office 2003 files or earlier versions will either be blocked from opening or will be opened in protected mode depending on the open behavior that was selected.

    How to undo the workaround.

    For Office 2003

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\PowerPoint\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2007

    Windows Registry Editor Version 5.00
    
    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\PowerPoint\Security\FileOpenBlock]
    
    "BinaryFiles"=dword:00000000
    

    For Office 2010  Open PowerPoint 2010 and follow these steps:

    1. Click the File tab.
    2. Under Help, click Options.
    3. Click Trust Center, and then click Trust Center Settings.
    4. In the Trust Center, click File Block Settings.
    5. Clear the Open check box for the file types that you previously selected.
    6. Click OK to apply the File Block settings.
  • Use the Microsoft Office Isolated Conversion Environment (MOICE) when opening files from unknown or untrusted sources

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

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

    To install MOICE, you must also 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.

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

    Enable MOICE

    Note See Microsoft Knowledge Base Article 935865 to use the automated Microsoft Fix it solution to enable or disable this workaround.

    To manually enable MOICE, run the commands as specified in the following table. Running the commands will associate the Office application extensions with MOICE.

Command to enable MOICE to be the registered handler
For Word, run the following command from a command prompt:\ ASSOC .doc=oice.word.document
For Excel, run the following commands from a command prompt:\ ASSOC .XLS=oice.excel.sheet\ ASSOC .XLT=oice.excel.template\ ASSOC .XLA=oice.excel.addin
For PowerPoint, run the following commands from a command prompt:\ ASSOC .PPT=oice.powerpoint.show\ ASSOC .POT=oice.powerpoint.template\ ASSOC .PPS=oice.powerpoint.slideshow

Note On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands 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 Microsoft Office 2007 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.

How to undo the workaround. Run the commands to disable MOICE as specified in the table below.

Command to disable MOICE as the registered handler
For Word, run the following command from a command prompt:\ ASSOC .doc=Word.Document.8
For Excel, run the following commands from a command prompt:\ ASSOC .xls=Excel.Sheet.8\ ASSOC .xlt=Excel.Template\ ASSOC .xla=Excel.Addin
For PowerPoint, run the following commands from a command prompt:\ ASSOC .ppt=PowerPoint.Show.8\ ASSOC .PPS=oice.powerpoint.slideshow\ ASSOC .pps=PowerPoint.SlideShow.8

Note On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, run the above commands from an elevated command prompt.

  • Do not open Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources

    Do not open Office 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 Drawing Exception Handling Vulnerability - CVE-2010-3335

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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
When a user opens a specially crafted Office file, system memory may become corrupted in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged-on with administrative user rights, an attacker could take complete control of the affected system. 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 Office file with an affected version of Microsoft Office software.

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

In a Web-based attack scenario, an attacker could 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 Office file.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office software 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?
The update addresses the vulnerability by modifying the way that Microsoft Office parses Office files.

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

MSO Large SPID Read AV Vulnerability - CVE-2010-3336

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

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

Mitigating Factors for MSO Large SPID Read AV Vulnerability - CVE-2010-3336

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.
  • In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site, and then convince them to open the specially crafted Office file.

Workarounds for MSO Large SPID Read AV Vulnerability - CVE-2010-3336

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:

  • Do not open Office files that you receive from untrusted sources or that you receive unexpectedly from trusted sources

    Do not open Office 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 MSO Large SPID Read AV Vulnerability - CVE-2010-3336

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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
When a user opens a specially crafted Office file, system memory may become corrupted in such a way that an attacker could execute arbitrary code.

What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could run arbitrary code as the logged-on user. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged-on with administrative user rights, an attacker could take complete control of the affected system. 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 Office file with an affected version of Microsoft Office software.

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

In a Web-based attack scenario, an attacker could 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 Office file.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office software 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?
The update addresses the vulnerability by modifying the way that Microsoft Office parses files.

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

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

Insecure Library Loading Vulnerability - CVE-2010-3337

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

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

Mitigating Factors for Insecure Library Loading Vulnerability - CVE-2010-3337

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:

  • For an attack to be successful using an untrusted remote file system location or WebDAV share, a user must be convinced to open a PowerPoint presentation located on the remote file system location or WebDAV share. An attacker would have no way to force users to visit an untrusted remote file system location or WebDAV share. Instead, an attacker would have to convince them to visit the untrusted remote file system location or WebDAV share, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the untrusted remote file system location or WebDAV share.
  • The file sharing protocol SMB is often disabled on the perimeter firewall. This limits the potential attack vectors.

Workarounds for Insecure Library Loading Vulnerability - CVE-2010-3337

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:

  • Disable loading of libraries from WebDAV and remote network shares

    Note See Microsoft Knowledge Base Article 2264107 to deploy a workaround tool that allows customers to disable the loading of libraries from remote network or WebDAV shares. This tool can be configured to disallow insecure loading on a per-application or a global system basis.

    Customers who are informed by their vendor of an application being vulnerable can use this tool to help protect against attempts to exploit this issue.

    Note See Microsoft Knowledge Base Article 2264107 to use the automated Microsoft Fix it solution to deploy the registry key to block loading of libraries for SMB and WebDAV shares. Note that this Fix it solution does require you to install the workaround tool also described in Microsoft Knowledge Base Article 2264107 first. This Fix it solution only deploys the registry key and requires the workaround tool in order to be effective. We recommend that administrators review the KB article closely prior to deploying this Fix it solution.

  • Disable the WebClient service

    Disabling the WebClient service helps protect affected systems from attempts to exploit this vulnerability by blocking the most likely remote attack vector through the Web Distributed Authoring and Versioning (WebDAV) client service. After applying this workaround it is still possible for remote attackers who successfully exploit this vulnerability to cause Microsoft Office Outlook to run programs located on the targeted user's computer or the Local Area Network (LAN), but users will be prompted for confirmation before opening arbitrary programs from the Internet.

    To disable the WebClient Service, follow these steps:

    1. Click Start, click Run, type Services.msc and then click OK.
    2. Right-click WebClient service and select Properties.
    3. Change the Startup type to Disabled. If the service is running, click Stop.
    4. Click OK and exit the management application.

    Impact of workaround. When the WebClient service is disabled, Web Distributed Authoring and Versioning (WebDAV) requests are not transmitted. In addition, any services that explicitly depend on the Web Client service will not start, and an error message will be logged in the System log. For example, WebDAV shares will be inaccessible from the client computer.

    How to undo the workaround.

    To re-enable the WebClient Service, follow these steps:

    1. Click Start, click Run, type Services.msc and then click OK.
    2. Right-click WebClient service and select Properties.
    3. Change the Startup type to Automatic. If the service is not running, click Start.
    4. Click OK and exit the management application.
  • Block TCP ports 139 and 445 at the firewall

    These ports are used to initiate a connection with the affected component. Blocking TCP ports 139 and 445 at the firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. Microsoft recommends that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, see the TechNet article, TCP and UDP Port Assignments.

    Impact of workaround. Several Windows services use the affected ports. Blocking connectivity to the ports may cause various applications or services to not function. Some of the applications or services that could be impacted are listed below:

    • Applications that use SMB (CIFS)
    • Applications that use mailslots or named pipes (RPC over SMB)
    • Server (File and Print Sharing)
    • Group Policy
    • Net Logon
    • Distributed File System (DFS)
    • Terminal Server Licensing
    • Print Spooler
    • Computer Browser
    • Remote Procedure Call Locator
    • Fax Service
    • Indexing Service
    • Performance Logs and Alerts
    • Systems Management Server
    • License Logging Service

    How to undo the workaround. Unblock TCP ports 139 and 445 at the firewall. For more information about ports, see TCP and UDP Port Assignments.

FAQ for Insecure Library Loading Vulnerability - CVE-2010-3337

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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

What causes the vulnerability?
This vulnerability requires a user to open a document contained within the same working directory as a specially crafted DLL file. The specially crafted DLL will be loaded into memory giving the attacker control of the affected system in the security context of the logged-on user.

Is this vulnerability related to the issue described in Microsoft Security Advisory 2269637?
Yes, this vulnerability is related to the class of vulnerabilities that affect how applications load external libraries described in Microsoft Security Advisory 2269637. This security bulletin addresses a particular instance of this type of vulnerability.

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. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged-on with administrative user rights, an attacker could take complete control of the affected system. 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 an office document in the same working directory as a specially crafted DLL file.

In an e-mail attack scenario, an attacker could exploit the vulnerability by convincing a user to place an Office file in the same folder as a specially crafted DLL file, and then convincing the user to open the Office file. When the user opens the Office file the specially crafted DLL file, which is contained in the same directory as the Office file, will be loaded.

What systems are primarily at risk from the vulnerability?
Systems where Microsoft Office 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.

How is Microsoft Office affected by this vulnerability?
Although the known attack vectors can only leverage Microsoft PowerPoint, the vulnerable code exists in a shared component of Microsoft Office.

What does the update do?
This update addresses the vulnerability by helping to ensure the vulnerable component of Microsoft Office uses a more appropriate and secure search order when loading libraries.

When this security bulletin was issued, had this vulnerability been publicly disclosed?
Yes. This vulnerability had been publicly disclosed when this security bulletin was originally issued.

When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.

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 and Windows 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 provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.

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
Microsoft Office XP Service Pack 3 Yes
Microsoft Office 2003 Service Pack 3 Yes
Microsoft Office 2007 Service Pack 2 Yes
Microsoft Office 2010 (32-bit editions) Yes
Microsoft Office 2010 (64-bit editions) Yes
Microsoft Office 2008 for Mac No
Microsoft Office for Mac 2011 No
Open XML File Format Converter for Mac No

Note For customers using legacy software not supported by the latest release of MBSA, 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

Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.

Systems Management Server

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

Software SMS 2.0 SMS 2003 with SUIT SMS 2003 with ITMU Configuration Manager 2007
Microsoft Office XP Service Pack 3 No No Yes Yes
Microsoft Office 2003 Service Pack 3 No No Yes Yes
Microsoft Office 2007 Service Pack 2 No No Yes Yes
Microsoft Office 2010 (32-bit editions) No No Yes Yes
Microsoft Office 2010 (64-bit editions) No No Yes Yes
Microsoft Office 2008 for Mac No No No No
Microsoft Office for Mac 2011 No No No No
Open XML File Format Converter for Mac No No No No

For SMS 2.0 and SMS 2003, 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. For more information about SMS 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 If you have used an Administrative Installation Point (AIP) for deploying 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.

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.

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:

Office XP (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-kb2289169-fullfile-enu.exe /q:a
Installing without restarting OfficeXP-kb2289169-fullfile-enu.exe /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 2289169
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
ACCESS, FP, OUTLOOK, PPT, ACCESSRT, PUB ProductFiles
PIPC1, PROPLUS, PRO, SBE, STD, STDEDU ProductFiles
EXCEL EXCELNonBootFiles, ProductFiles

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer.

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:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 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.

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.

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.

Office 2003 (all editions)

Reference Table

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

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 Office2003-kb2289187-fullfile-enu.exe /q:a
Installing without restarting Office2003-kb2289187-fullfile-enu.exe /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 See Microsoft Knowledge Base Article 2289187
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
VISVEA, PPT11, RMS, STD11, ACCESSRT, ACC11, BASIC11, FP11, ONOTE11, OUTLS11, OUTL11, OUTLSM11, PERS11, PRO11SB, PROI11, PRO11, PUB11, STDP11, WORD11, INF11, EXCEL11, PRJPROE, PRJPRO, PRJSTDE, PRJSTD, VISPRO, VISPROR, VISSTD, VISSTDR ProductNonBootFiles

Note Administrators working in managed environments can find complete resources for deploying Office updates in an organization at the Office Admin Update Center. At that site, scroll down and look under the Update Resources section for the software version you are updating. The Windows Installer Documentation also provides more information about the parameters supported by Windows Installer.

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:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 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.

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.

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 the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You can also click 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 can also click 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 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 The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention Office2007-kb2289158-fullfile-x86-glb.exe /passive
Installing without restarting Office2007-kb2289158-fullfile-x86-glb.exe /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 See Microsoft Knowledge Base Article 2289158
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:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 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.

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.

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 the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You can also click 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 can also click 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 2010 (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 The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention For Microsoft Office 2010 (32-bit editions):\ Office2010-kb2289161-fullfile-x86-glb.exe /passive
For Microsoft Office 2010 (64-bit editions):\ Office2010-kb2289161-fullfile-x64-glb.exe /passive
Installing without restarting For Microsoft Office 2010 (32-bit editions):\ Office2010-kb2289161-fullfile-x86-glb.exe /norestart
For Microsoft Office 2010 (64-bit editions):\ Office2010-kb2289161-fullfile-x64-glb.exe /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 For Microsoft Word 2010, use Add or Remove Programs tool in Control Panel.
For Microsoft Office Web Apps and Microsoft Word Web App, this security update cannot be removed.
File Information For Microsoft Office 2010, see Microsoft Knowledge Base Article 2289161
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:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 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.

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.

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 the Start Search box.
    2. When the file appears under Programs, right-click the file name and click Properties.
    3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
    4. You can also click 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 can also click 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 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.2.8 Update from the Microsoft Download Center.

  • 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.2.8 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.2.8 Update volume window, double-click the Microsoft Office 2008 for Mac 12.2.8 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.2.8 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.2.8, 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 to learn about the support options that are available to you.

Office for Mac 2011

Deployment Information

Prerequisites

  • Mac OS X version 10.5.8 or later on an Intel 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 for Mac 2011 14.0.1 Update from the Microsoft Download Center.

  • Quit any applications that are running, including virus-protection applications and all Microsoft Office applications, because they might interfere with installation.
  • Open the Microsoft Office for Mac 2011 14.0.1 Update volume on your desktop. This step might have been performed for you.
  • To start the update process, in the Microsoft Office for Mac 2011 14.0.1 Update volume window, double-click the Microsoft Office for Mac 2011 14.0.1 Update application, and follow the instructions on the screen.
  • When 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 for Mac 2011 14.0.1 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 2011).
  2. Select Word, Excel, PowerPoint or Outlook and launch the application.
  3. On the Application menu, click About Application_Name (where Application_Name is Word, Excel, PowerPoint or Outlook).

If the Latest Installed Update Version number is 14.0.1, 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 to learn about the support options that are available to you.

Open XML File Format 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 Format Converter for Mac 1.1.8 Update from the Microsoft Download Center.

  • 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 Format Converter for Mac 1.1.8 Update volume on your desktop. This step might have been performed for you.
  • To start the update process, in the Open XML File Format Converter for Mac 1.1.8 Update volume window, double-click the Open XML File Format Converter for Mac 1.1.8 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 Format Converter for Mac 1.1.8 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.
  2. Select the file, Open XML File Format Converter.
  3. On the File menu, click Get Info or Show Info.

If the Version number is 1.1.8, 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 to learn about the support options that are available to you.

Other Information

Acknowledgments

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

Microsoft Active Protections Program (MAPP)

To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

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

Disclaimer

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

Revisions

  • V1.0 (November 9, 2010): Bulletin published.
  • V1.1 (November 17, 2010): Corrected the severity table and vulnerability section to add CVE-2010-2573 as a vulnerability addressed by this update. This is an informational change only.
  • V2.0 (December 15, 2010): Announced the availability of the security updates for Microsoft Office 2008 for Mac (KB2476512) and Open XML File Format Converter for Mac (KB2476511). Microsoft recommends that users of these software apply these updates at the earliest opportunity.
  • V2.1 (April 12, 2011): Announced that the security update for Microsoft Office 2004 for Mac (KB2505924) offered in MS11-021, MS11-022, and MS11-023 also addresses the vulnerabilities described in this security bulletin.

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