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

Microsoft Security Bulletin MS11-022 - Important

Vulnerabilities in Microsoft PowerPoint Could Allow Remote Code Execution (2489283)

Published: April 12, 2011 | Updated: April 20, 2011

Version: 1.1

General Information

Executive Summary

This security update resolves three privately reported vulnerabilities in Microsoft PowerPoint. The vulnerabilities could allow remote code execution if a user opens a specially crafted PowerPoint file. 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. The automated Microsoft Fix it solution for PowerPoint 2010, "Disable Edit in Protected View for PowerPoint 2010," available in Microsoft Knowledge Base Article 2501584, blocks the attack vectors for exploiting the vulnerabilities described in CVE-2011-0655 and CVE-2011-0656.

This security update is rated Important for all supported releases of Microsoft PowerPoint; Microsoft Office for Mac; Open XML File Format Converter for Mac; Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats; Microsoft PowerPoint Viewer, and Microsoft PowerPoint Web App. For more information, see the subsection, Affected and Non-Affected Software, in this section.

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

Recommendation. Customers can configure automatic updating to check online for updates from Microsoft Update by using the Microsoft Update service. Customers who have automatic updating enabled and configured to check online for updates from Microsoft Update typically will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates from Microsoft Update and install this update manually. For information about specific configuration options in automatic updating in supported editions of Windows XP and Windows Server 2003, see Microsoft Knowledge Base Article 294871. For information about automatic updating in supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, see Understanding Windows automatic updating.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.

See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.

Known Issues. Microsoft Knowledge Base Article 2489283 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 Suites and Software

Microsoft Office Suite and Other SoftwareComponentMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft Office Suites and Components
Microsoft Office XP Service Pack 3Microsoft PowerPoint 2002 Service Pack 3
(KB2464617)
Remote Code ExecutionImportantMS10-088
Microsoft Office 2003 Service Pack 3Microsoft PowerPoint 2003 Service Pack 3
(KB2464588)
Remote Code ExecutionImportantMS10-088
Microsoft Office 2007 Service Pack 2Microsoft PowerPoint 2007 Service Pack 2
(KB2464594)
Remote Code ExecutionImportantMS10-036
Microsoft Office 2010 (32-bit editions)Microsoft PowerPoint 2010 (32-bit editions)[1]
(KB2519975)
Remote Code ExecutionImportantNone
Microsoft Office 2010 (64-bit editions)Microsoft PowerPoint 2010 (64-bit editions)[1]
(KB2519975)
Remote Code ExecutionImportantNone
Microsoft Office for Mac
Microsoft Office 2004 for Mac
(KB2505924)
Not applicableRemote Code ExecutionImportantNone
Microsoft Office 2008 for Mac
(KB2505927)
Not applicableRemote Code ExecutionImportantMS10-087
Microsoft Office for Mac 2011
(KB2525412)
Not applicableRemote Code ExecutionImportantMS10-087
Open XML File Format Converter for Mac
(KB2505935)
Not applicableRemote Code ExecutionImportantMS10-087
Other Office software
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2
(KB2464635)
Not applicableRemote Code ExecutionImportantMS09-017
Microsoft PowerPoint Viewer 2007 Service Pack 2
(KB2464623)
Not applicableRemote Code ExecutionImportantMS10-088
Microsoft PowerPoint Viewer
(KB2519984)
Not applicableRemote Code ExecutionImportantNone

[1]The automated Microsoft Fix it solution for PowerPoint 2010, "Disable Edit in Protected View for PowerPoint 2010," available in Microsoft Knowledge Base Article 2501584, blocks the attack vectors for exploiting the vulnerabilities described in CVE-2011-0655 and CVE-2011-0656. For more information, see the FAQ entry, "What is the benefit if I apply the Microsoft Fix it solution to disable edit in protected view?", in the next section.

Microsoft Server Software

Microsoft Office Web AppsComponentMaximum Security ImpactAggregate Severity RatingBulletins Replaced by this Update
Microsoft Office Web AppsMicrosoft PowerPoint Web App
(KB2520047)
Remote Code ExecutionImportantMS10-079

Non-Affected Software

Office and Other Software
Microsoft Works 9

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

Does this update contain any security-related changes to functionality? 
Yes. The updates for Microsoft PowerPoint 2003 Service Pack 3 (KB2464588) and Microsoft PowerPoint 2007 Service Pack 2 (KB2464594), in conjunction with the update offered in MS11-023, provide support for the Office File Validation feature. For more information about the Office File Validation feature, see Microsoft Security Advisory 2501584.

How is this security update related to MS10-087 and MS10-088? 
The update for Microsoft Office 2004 for Mac (KB2505924) offered in this bulletin also addresses the vulnerabilities described in the MS10-087 and MS10-088 security bulletins.

What is the benefit if I apply the Microsoft Fix it solution to disable edit in protected view? 
By setting Office File Validation to not allow editing of suspicious files in PowerPoint 2010, the Microsoft Fix it solution, "Disable Edit in Protected View for PowerPoint 2010," blocks the attack vectors for exploiting the vulnerabilities described in CVE-2011-0655 and CVE-2011-0656. Customers may choose to apply the Fix it solution as a workaround if choosing not to install the security update for PowerPoint 2010 until a later time.

Refer to Microsoft Knowledge Base Article 2501584 for instructions on applying the automated Fix it solution, "Disable Edit in Protected View for PowerPoint 2010," or refer to the Workaround sections for CVE-2011-0655 and CVE-2011-0656 in the Vulnerability Information section of this bulletin for instructions on applying the solution manually.

MS11-021 and MS11-023 also describe vulnerabilities in Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, and Open XML File Format Converter for Mac. MS11-021 also describes vulnerabilities in Microsoft Office for Mac 2011. How do MS11-021 and MS11-023 relate to this bulletin (MS11-022)?
The security update packages for Microsoft Office 2004 for Mac (KB2505924), Microsoft Office 2008 for Mac (KB2505927), and Open XML File Format Converter for Mac (KB2505935) offered in this bulletin also address the vulnerabilities described in the MS11-021 and MS11-023 security bulletins. The security update package for Microsoft Office for Mac 2011 (KB2525412) offered in this bulletin also addresses the vulnerabilities described in MS11-021. Users with Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, Open XML File Format Converter for Mac, or Microsoft Office for Mac 2011 installed will only need to install these security update packages once.

Why does this update address several reported security vulnerabilities? 
This update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers need to install this update only.

What is Microsoft PowerPoint Viewer? 
Microsoft PowerPoint Viewer, which is based on Microsoft Office 2010 technology, is a replacement for Microsoft PowerPoint Viewer 2007 Service Pack 2. Microsoft PowerPoint Viewer lets you view full-featured presentations created in Microsoft PowerPoint 97 and later versions.

I use the "Package a Presentation for CD" feature. How can I help ensure my presentations are protected from the vulnerabilities described in this bulletin? 
After applying this security update to affected software, customers running supported editions of Microsoft PowerPoint 2003 and Microsoft PowerPoint 2007 can issue updated versions of their presentations created using the Package a Presentation for CD feature in PowerPoint to help ensure that the PowerPoint Viewer included in their presentations is protected from the vulnerabilities described in this bulletin.

Microsoft PowerPoint 2010 presentations created using the Package a Presentation for CD feature do not include the PowerPoint Viewer.

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

How are Microsoft Office standalone programs affected by these vulnerabilities? 
A Microsoft Office standalone program is affected with the same severity rating as the corresponding component in a Microsoft Office Suite. For example, a standalone installation of Microsoft PowerPoint is affected with the same severity rating as an installation of Microsoft PowerPoint that was delivered with a Microsoft Office Suite.

The Microsoft Office component discussed in this article is part of the Microsoft Office Suite that I have installed on my system; however, I did not choose to install this specific component. Will I be offered this update? 
Yes, if the component discussed in this bulletin was delivered with the version of the Microsoft Office Suite installed on your system, the system will be offered updates for it whether the component is installed or not. The detection logic used to scan for affected systems is designed to check for updates for all components that were delivered with the particular Microsoft Office Suite and to offer the updates to a system. Users who choose not to apply an update for a component that is not installed, but is delivered with their version of the Microsoft Office Suite, will not increase the security risk of that system. On the other hand, users who do choose to install the update will not have a negative impact on the security or performance of a system.

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

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 April bulletin summary. For more information, see Microsoft Exploitability Index.

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareFloating Point Techno-color Time Bandit RCE Vulnerability - CVE-2011-0655Persist Directory RCE Vulnerability - CVE-2011-0656OfficeArt Atom RCE Vulnerability - CVE-2011-0976Aggregate Severity Rating
Microsoft Office Suites and Components
Microsoft PowerPoint 2002 Service Pack 3Not applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft PowerPoint 2003 Service Pack 3Not applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft PowerPoint 2007 Service Pack 2Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft PowerPoint 2010 (32-bit editions)Important 
Remote Code Execution
Important 
Remote Code Execution
Not applicableImportant
Microsoft PowerPoint 2010 (64-bit editions)Important 
Remote Code Execution
Important 
Remote Code Execution
Not applicableImportant
Microsoft Office for Mac
Microsoft Office 2004 for MacImportant 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft Office 2008 for MacImportant 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft Office for Mac 2011Important 
Remote Code Execution
Important 
Remote Code Execution
Not applicableImportant
Open XML File Format Converter for MacImportant 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Other Software
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft PowerPoint Viewer 2007 Service Pack 2Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft PowerPoint ViewerImportant 
Remote Code Execution
Important 
Remote Code Execution
Not applicableImportant
Microsoft Server Software
Microsoft PowerPoint Web AppImportant 
Remote Code Execution
Important 
Remote Code Execution
Not applicableImportant

A remote code execution vulnerability exists in the way that Microsoft PowerPoint handles specially crafted PowerPoint files. An attacker could exploit the vulnerability by creating a specially crafted PowerPoint file that could be included as an e-mail attachment, or hosted on a specially crafted or compromised Web site.

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

Mitigating Factors for Floating Point Techno-color Time Bandit RCE Vulnerability - CVE-2011-0655

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:

  • 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.
  • 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 Microsoft PowerPoint 2010, the possibility of an attacker's success in exploiting this vulnerability is reduced due to the protections afforded by the Office File Validation feature enabled in Microsoft Office 2010 by default. Specially crafted files used to exploit the vulnerability open in Protected View and the user is warned that the file is unsafe and potentially harmful because the file failed validation. A user would have to click through multiple warnings and then open the file for editing or saving before the vulnerability could be exploited. For more information about Protected View and Office File Validation, see the TechNet article, Security Overview for Office 2010.

    Note  Turning off Office File Validation in Microsoft PowerPoint 2010 would remove the protections provided by Office File Validation as a mitigating factor. For this reason, Microsoft recommends not turning off the Office File Validation feature in Microsoft PowerPoint 2010.

Workarounds for Floating Point Techno-color Time Bandit RCE Vulnerability - CVE-2011-0655

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:

  • Set Office File Validation to disable editing in protected view in PowerPoint 2010

    Note  See Microsoft Knowledge Base Article 2501584 to use the automated Microsoft Fix it solution, "Disable Edit in Protected View for PowerPoint 2010," to enable or disable this workaround.

    Warning  Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    To manually apply this workaround:

    1. Open Registry Editor and navigate to the following registry key:

      HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\PowerPoint\Security\FileValidation
    2. Set the value for DisableEditFromPV to "00000001"
    3. Exit Registry Editor

    Impact of workaround.  Office File Validation will no longer allow the editing of suspicious files in PowerPoint 2010.

    How to undo the workaround.

    1. Open Registry Editor and navigate to the following registry key:

      HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\PowerPoint\Security\FileValidation
    2. Set the value for DisableEditFromPV to "00000000"
    3. Exit Registry Editor
  • 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 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 Microsoft Office 2007, all of the latest security updates for Office 2007 must be applied.

    Impact of workaround. For 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.

    How to undo the workaround.

    For Office 2007

    Windows Registry Editor Version 5.00

    [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.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 documents from untrusted sources

    Do not open 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 Floating Point Techno-color Time Bandit RCE Vulnerability - CVE-2011-0655

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? 
The vulnerability is caused when PowerPoint reads an invalid record in a specially crafted PowerPoint file, causing an error that could corrupt memory in such a way as to allow an attacker to execute arbitrary code.

What is the component affected by this vulnerability? 
Microsoft PowerPoint is the component affected by this vulnerability.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of an affected system in the context of the current logged-on user. 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? 
Exploitation of this vulnerability requires that a user open a specially crafted PowerPoint file with an affected version of Microsoft PowerPoint.

In a Web-based attack scenario, a Web site could contain a specially crafted PowerPoint file that is used to exploit this vulnerability. An attacker would have no way to force users to visit the Web site. Instead, an attacker would have to convince users to visit the Web site and open the specially crafted PowerPoint file, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's Web site, and then convince them to open the 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 convincing the user to open the file.

What systems are primarily at risk from the vulnerability? 
Systems where an affected version of Microsoft PowerPoint is used, such as 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 modifies the way that PowerPoint validates TimeColorBehaviorContainer Floating Point records when opening 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.

A remote code execution vulnerability exists in the way that Microsoft PowerPoint handles specially crafted PowerPoint files. An attacker could exploit the vulnerability by creating a specially crafted PowerPoint file that could be included as an e-mail attachment, or hosted on a specially crafted or compromised Web site.

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

Mitigating Factors for Persist Directory RCE Vulnerability - CVE-2011-0656

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:

  • 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.
  • 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 Microsoft PowerPoint 2010, the possibility of an attacker's success in exploiting this vulnerability is reduced due to the protections afforded by the Office File Validation feature enabled in Microsoft Office 2010 by default. Specially crafted files used to exploit the vulnerability open in Protected View and the user is warned that the file is unsafe and potentially harmful because the file failed validation. A user would have to click through multiple warnings and then open the file for editing or saving before the vulnerability could be exploited. For more information about Protected View and Office File Validation, see the TechNet article, Security Overview for Office 2010.

    Note  Turning off Office File Validation in Microsoft PowerPoint 2010 would remove the protections provided by Office File Validation as a mitigating factor. For this reason, Microsoft recommends not turning off the Office File Validation feature in Microsoft PowerPoint 2010.

Workarounds for Persist Directory RCE Vulnerability - CVE-2011-0656

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:

  • Set Office File Validation to disable editing in protected view in PowerPoint 2010

    Note  See Microsoft Knowledge Base Article 2501584 to use the automated Microsoft Fix it solution, "Disable Edit in Protected View for PowerPoint 2010," to enable or disable this workaround.

    Warning  Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe.

    To manually apply this workaround:

    1. Open Registry Editor and navigate to the following registry key:

      HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\PowerPoint\Security\FileValidation
    2. Set the value for DisableEditFromPV to "00000001"
    3. Exit Registry Editor

    Impact of workaround.  Office File Validation will no longer allow the editing of suspicious files in PowerPoint 2010.

    How to undo the workaround.

    1. Open Registry Editor and navigate to the following registry key:

      HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\PowerPoint\Security\FileValidation
    2. Set the value for DisableEditFromPV to "00000000"
    3. Exit Registry Editor
  • 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 Microsoft Office 2007, all of the latest security updates for Office 2007 must be applied.

    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.

    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

  • 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 documents from untrusted sources

    Do not open 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 Persist Directory RCE Vulnerability - CVE-2011-0656

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? 
The vulnerability is caused when PowerPoint reads an invalid record in a specially crafted PowerPoint file, causing an error that could corrupt memory in such a way as to allow an attacker to execute arbitrary code.

What is the component affected by this vulnerability? 
Microsoft PowerPoint is the component affected by this vulnerability.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of an affected system in the context of the current logged-on user. 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? 
Exploitation of this vulnerability requires that a user open a specially crafted PowerPoint file with an affected version of Microsoft PowerPoint.

In a Web-based attack scenario, a Web site could contain a specially crafted PowerPoint file that is used to exploit this vulnerability. An attacker would have no way to force users to visit the Web site. Instead, an attacker would have to convince users to visit the Web site and open the specially crafted PowerPoint file, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's Web site, and then convince them to open the 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 convincing the user to open the file.

What systems are primarily at risk from the vulnerability? 
Systems where an affected version of Microsoft PowerPoint is used, such as 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 modifies the way that PowerPoint validates PersistDirectoryEntry records when opening 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.

A remote code execution vulnerability exists in the way that Microsoft PowerPoint handles specially crafted PowerPoint files. An attacker could exploit the vulnerability by creating a specially crafted PowerPoint file that could be included as an e-mail attachment, or hosted on a specially crafted or compromised Web site.

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

Mitigating Factors for OfficeArt Atom RCE Vulnerability - CVE-2011-0976

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:

  • 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.
  • 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 Microsoft PowerPoint 2010, the possibility of an attacker's success in exploiting this vulnerability is reduced due to the protections afforded by the Office File Validation feature enabled in Microsoft Office 2010 by default. Specially crafted files used to exploit the vulnerability open in Protected View and the user is warned that the file is unsafe and potentially harmful because the file failed validation. A user would have to click through multiple warnings and then open the file for editing or saving before the vulnerability could be exploited. For more information about Protected View and Office File Validation, see the TechNet article, Security Overview for Office 2010.

    Note  Turning off Office File Validation in Microsoft PowerPoint 2010 would remove the protections provided by Office File Validation as a mitigating factor. For this reason, Microsoft recommends not turning off the Office File Validation feature in Microsoft PowerPoint 2010.

Workarounds for OfficeArt Atom RCE Vulnerability - CVE-2011-0976

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 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 Microsoft Office 2007, all of the latest security updates for Office 2007 must be applied.

    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.

    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

  • 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 documents from untrusted sources

    Do not open 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 OfficeArt Atom RCE Vulnerability - CVE-2011-0976

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? 
The vulnerability is caused when PowerPoint reads an invalid record in a specially crafted PowerPoint file, causing an error that could corrupt memory in such a way as to allow an attacker to execute arbitrary code.

What is the component affected by this vulnerability? 
Microsoft PowerPoint is the component affected by this vulnerability.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability could take complete control of an affected system in the context of the current logged-on user. 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? 
Exploitation of this vulnerability requires that a user open a specially crafted PowerPoint file with an affected version of Microsoft PowerPoint.

In a Web-based attack scenario, a Web site could contain a specially crafted PowerPoint file that is used to exploit this vulnerability. An attacker would have no way to force users to visit the Web site. Instead, an attacker would have to convince users to visit the Web site and open the specially crafted PowerPoint file, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes them to the attacker's Web site, and then convince them to open the 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 convincing the user to open the file.

What systems are primarily at risk from the vulnerability? 
Systems where an affected version of Microsoft PowerPoint is used, such as 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 modifies the way that PowerPoint validates OfficeArt records when opening 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.

Update Information

Security Central

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

For customers of Microsoft Office for Mac, Microsoft AutoUpdate for Mac can help keep your Microsoft software up to date. For more information about using Microsoft AutoUpdate for Mac, see Check for software updates automatically.

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 3Yes
Microsoft Office 2003 Service Pack 3Yes
Microsoft Office 2007 Service Pack 2Yes
Microsoft Office 2010 (32-bit editions)Yes
Microsoft Office 2010 (64-bit editions)Yes
Microsoft Office 2004 for MacNo
Microsoft Office 2008 for MacNo
Microsoft Office for Mac 2011No
Open XML File Format Converter for MacNo
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2Yes
Microsoft PowerPoint Viewer 2007 Service Pack 2Yes
Microsoft PowerPoint ViewerYes
Microsoft PowerPoint Web AppYes

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.

SoftwareSMS 2.0SMS 2003 with SUITSMS 2003 with ITMUConfiguration Manager 2007
Microsoft Office XP Service Pack 3NoNoYesYes
Microsoft Office 2003 Service Pack 3NoNoYesYes
Microsoft Office 2007 Service Pack 2NoNoYesYes
Microsoft Office 2010 (32-bit editions)NoNoYesYes
Microsoft Office 2010 (64-bit editions)NoNoYesYes
Microsoft Office 2004 for MacNoNoNoNo
Microsoft Office 2008 for MacNoNoNoNo
Microsoft Office for Mac 2011NoNoNoNo
Open XML File Format Converter for MacNoNoNoNo
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2NoNoYesYes
Microsoft PowerPoint Viewer 2007 Service Pack 2NoNoYesYes
Microsoft PowerPoint ViewerNoNoYesYes
Microsoft PowerPoint Web AppNoNoYesYes

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.

Affected Software

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

PowerPoint 2002 (all editions)

Reference Table

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

Inclusion in Future Service PacksThere 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 interventionFor PowerPoint 2002:
OfficeXP-kb2464617-fullfile-enu.exe /q:a
Installing without restartingFor PowerPoint 2002:
OfficeXP-kb2464617-fullfile-enu.exe /r:n
Update log fileNot applicable
Further informationFor 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.
HotPatchingNot applicable
Removal InformationUse 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 InformationSee Microsoft Knowledge Base Article 2464617
Registry Key VerificationNot 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:

ProductFeature
PPT, PROPLUS, PRO, STD, STDEDUPPTFiles

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.

Supported Security Update Installation Switches
SwitchDescription
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/q:uSpecifies user-quiet mode, which presents some dialog boxes to the user.
/q:aSpecifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:pathSpecifies the target folder for extracting files.
/cExtracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:pathOverrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:nNever restarts the system after installation.
/r:IPrompts the user to restart the system if a restart is required, except when used with /q:a.
/r:aAlways restarts the system after installation.
/r:sRestarts the system after installation without prompting the user.
/n:vNo 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.

PowerPoint 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 PacksThere 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 interventionFor PowerPoint 2003 Service Pack 3:
Office2003-KB2464588-fullfile-enu.exe /q:a
Installing without restartingFor PowerPoint 2003 Service Pack 3:
Office2003-KB2464588-fullfile-enu.exe /r:n
Update log fileNot applicable
Further informationFor 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.
HotPatchingNot applicable
Removal InformationUse 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 InformationSee Microsoft Knowledge Base Article 2464588
Registry Key VerificationNot 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:

ProductFeature
STD11, PPT11, PROI11, PRO11, STDP11, PRO11SBPPTFiles

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.

Supported Security Update Installation Switches
SwitchDescription
/qSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/q:uSpecifies user-quiet mode, which presents some dialog boxes to the user.
/q:aSpecifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:pathSpecifies the target folder for extracting files.
/cExtracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:pathOverrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:nNever restarts the system after installation.
/r:IPrompts the user to restart the system if a restart is required, except when used with /q:a.
/r:aAlways restarts the system after installation.
/r:sRestarts the system after installation without prompting the user.
/n:vNo 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.

PowerPoint 2007 (all editions), Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (all versions), and PowerPoint Viewer 2007 (all versions)

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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor PowerPoint 2007:
PowerPoint2007-KB2464594-fullfile-x86-glb.exe /passive
For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2:
Office2007-kb2464635-fullfile-x86-glb.exe /passive
For PowerPoint Viewer 2007 Service Pack 2:
Office2007-KB2464623-fullfile-x86-glb.exe /passive
Installing without restartingFor PowerPoint 2007:
PowerPoint2007-KB2464594-fullfile-x86-glb.exe /norestart
For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2:
Office2007-kb2464635-fullfile-x86-glb.exe /norestart
For PowerPoint Viewer 2007 Service Pack 2:
Office2007-KB2464623-fullfile-x86-glb.exe /norestart
Update log fileNot applicable
Further informationFor 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.
HotPatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel.
File InformationFor PowerPoint 2007, see Microsoft Knowledge Base Article 2464594
For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2, see Microsoft Knowledge Base Article 2464635
For PowerPoint Viewer 2007 Service Pack 2, see Microsoft Knowledge Base Article 2464623
Registry Key VerificationNot 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.

Supported Security Update Installation Switches
SwitchDescription
/? or /helpDisplays usage dialog.
/passiveSpecifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quietSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/norestartSuppresses restarting the system if the update requires a restart.
/forcerestartAutomatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extractExtracts 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.

PowerPoint 2010 (all editions), PowerPoint Viewer (all versions), and PowerPoint Web App

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 PacksThe update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user interventionFor PowerPoint 2010 (32-bit editions):
PowerPoint2010-kb2519975-fullfile-x86-glb.exe /passive
For PowerPoint 2010 (64-bit editions):
PowerPoint2010-kb2519975-fullfile-x64-glb.exe /passive
For PowerPoint Viewer:
office2010-kb2519984-fullfile-x86-glb.exe /passive
For PowerPoint Web App:
webapplications2010-kb2520047-fullfile-x64-glb.exe /passive
Installing without restartingFor PowerPoint 2010 (32-bit editions):
PowerPoint2010-kb2519975-fullfile-x86-glb.exe /norestart
For PowerPoint 2010 (64-bit editions):
PowerPoint2010-kb2519975-fullfile-x64-glb.exe /norestart
For PowerPoint Viewer:
office2010-kb2519984-fullfile-x86-glb.exe /norestart
For PowerPoint Web App:
webapplications2010-kb2520047-fullfile-x64-glb.exe /norestart
Update log fileNot applicable
Further informationFor 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.
HotPatchingNot applicable
Removal InformationUse Add or Remove Programs tool in Control Panel.
File InformationFor PowerPoint 2010, see Microsoft Knowledge Base Article 2519975
For PowerPoint Viewer, see Microsoft Knowledge Base Article 2519984
For PowerPoint Web App, see Microsoft Knowledge Base Article 2520047
Registry Key VerificationNot 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.

Supported Security Update Installation Switches
SwitchDescription
/? or /helpDisplays usage dialog.
/passiveSpecifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quietSpecifies quiet mode, or suppresses prompts, when files are being extracted.
/norestartSuppresses restarting the system if the update requires a restart.
/forcerestartAutomatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extractExtracts 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 2004 for Mac

Deployment Information

Prerequisites

  • Mac OS X version 10.2.8 or later on a G3, Mac OS X-compatible processor or higher
  • Mac OS X user accounts must have administrator privileges to install this security update

Installing the Update

Download and install the appropriate language version of the Microsoft Office 2004 for Mac 11.6.3 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 2004 for Mac 11.6.3 Update volume on your desktop. This step might have been performed for you.
  • To start the update process, in the Microsoft Office 2004 for Mac 11.6.3 Update volume window, double-click the Microsoft Office 2004 for Mac 11.6.3 Update application, and follow the instructions on the screen.
  • If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following "Verifying Update Installation" heading. To remove the update installer, first drag the Microsoft Office 2004 for Mac 11.6.3 Update volume to the Trash, and then drag the file that you downloaded to the Trash.

Verifying Update Installation

To verify that a security update is installed on an affected system, follow these steps:

  1. In the Finder, navigate to the Application Folder (Microsoft Office 2004: Office).
  2. Select the file, Microsoft Component Plugin.
  3. On the File menu, click Get Info or Show Info.

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

Restart Requirement

This update does not require you to restart your computer.

Removing the Update

This security update cannot be uninstalled.

Additional Information

If you have technical questions or problems downloading or using this update, visit Microsoft for Mac Support to learn about the support options that are available to you.

Office 2008 for Mac

Deployment Information

Prerequisites

  • Mac OS X version 10.4.9 or later on an Intel, PowerPC G5, or PowerPC G4 (500 MHz or faster) processor
  • Mac OS X user accounts must have administrator privileges to install this security update

Installing the Update

Download and install the appropriate language version of the Microsoft Office 2008 for Mac 12.2.9 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.9 Update volume on your desktop. This step might have been performed for you.
  • To start the update process, in the Microsoft Office 2008 for Mac 12.2.9 Update volume window, double-click the Microsoft Office 2008 for Mac 12.2.9 Update application, and follow the instructions on the screen.
  • If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following "Verifying Update Installation" heading. To remove the update installer, first drag the Microsoft Office 2008 for Mac 12.2.9 Update volume to the Trash, and then drag the file that you downloaded to the Trash.

Verifying Update Installation

To verify that a security update is installed on an affected system, follow these steps:

  1. In the Finder, navigate to the Application Folder (Microsoft Office 2008: Office).
  2. Select the file, Microsoft Component Plugin.
  3. On the File menu, click Get Info or Show Info.

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

Restart Requirement

This update does not require you to restart your computer.

Removing the Update

This security update cannot be uninstalled.

Additional Information

If you have technical questions or problems downloading or using this update, visit Microsoft for Mac Support 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.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.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.1 Update volume window, double-click the Microsoft Office for Mac 2011 14.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.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.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.9 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.9 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.9 Update volume window, double-click the Open XML File Format Converter for Mac 1.1.9 Update application, and follow the instructions on the screen.
  • If the installation finishes successfully, you can remove the update installer from your hard disk. To verify that the installation finished successfully, see the following "Verifying Update Installation" heading. To remove the update installer, first drag the Open XML File Format Converter for Mac 1.1.9 Update volume to the Trash, and then drag the file that you downloaded to the Trash.

Verifying Update Installation

To verify that a security update is installed on an affected system, follow these steps:

  1. In the Finder, navigate to the Application Folder.
  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.9, the update has been successfully installed.

Restart Requirement

This update does not require you to restart your computer.

Removing the Update

This security update cannot be uninstalled.

Additional Information

If you have technical questions or problems downloading or using this update, visit Microsoft for Mac Support 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 (April 12, 2011): Bulletin published.

    V1.1 (April 20, 2011): Corrected the bulletin replacement information for the Microsoft PowerPoint Web App update (KB2520047). This is an informational change only. There were no changes to the detection logic or the update files.

Built at 2014-04-16T02:39:51Z-07:00

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