Article
06/08/2023

Security Bulletin

Microsoft Security Bulletin MS10-079 - Important

Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (2293194)

Published: October 12, 2010 | Updated: November 03, 2010

Version: 1.2

General Information

Executive Summary

This security update resolves eleven privately reported vulnerabilities in Microsoft Office. The vulnerabilities could allow remote code execution if a user opens a specially crafted Word 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.

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

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

Recommendation. Microsoft recommends that customers apply the update at the earliest opportunity.

Known Issues. Microsoft Knowledge Base Article 2293194 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 and Other Productivity Software	Component	Maximum Security Impact	Aggregate Severity Rating	Bulletins Replaced by this Update
Microsoft Office Suites and Components
Microsoft Office XP Service Pack 3	Microsoft Word 2002 Service Pack 3 (KB2328360)	Remote Code Execution	Important	MS10-056
Microsoft Office 2003 Service Pack 3	Microsoft Word 2003 Service Pack 3 (KB2344911)	Remote Code Execution	Important	MS10-056
Microsoft Office 2007 Service Pack 2	Microsoft Word 2007 Service Pack 2^[1](KB2344993)	Remote Code Execution	Important	MS10-056
Microsoft Office 2010 (32-bit editions)	Microsoft Word 2010 (32-bit editions) (KB2345000)	Remote Code Execution	Important	None
Microsoft Office 2010 (64-bit editions)	Microsoft Word 2010 (64-bit editions) (KB2345000)	Remote Code Execution	Important	None
Microsoft Office for Mac
Microsoft Office 2004 for Mac (KB2422343)	Not applicable	Remote Code Execution	Important	MS10-056
Microsoft Office 2008 for Mac (KB2422352)	Not applicable	Remote Code Execution	Important	MS10-056
Open XML File Format Converter for Mac (KB2422398)	Not applicable	Remote Code Execution	Important	MS10-056
Other Microsoft Office Software
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2 (KB2345043)	Not applicable	Remote Code Execution	Important	MS10-056
Microsoft Word Viewer (KB2345009)	Not applicable	Remote Code Execution	Important	MS10-056

Microsoft Server Software

Microsoft Office Web Apps	Component	Maximum Security Impact	Aggregate Severity Rating	Bulletins Replaced by this Update
Microsoft Office Web Apps[2]\ (KB2346411)	Not applicable	Remote Code Execution	Important	None
Microsoft Office Web Apps	Microsoft Word Web App[2]\ (KB2345015)	Remote Code Execution	Important	None

^[1]For Microsoft Word 2007 Service Pack 2, in addition to security update package KB2344993, customers also need to install the security update for Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2 (KB2345043) to be protected from the vulnerabilities described in this bulletin.

^[2]For Microsoft Office Web Apps, customers need to install both security update KB2346411 and security update KB2345015 to be protected from the vulnerabilities described in this bulletin.

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.

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.

MS10-072 also describes vulnerabilities in Microsoft Office Web Apps. How does MS10-072 relate to this bulletin (MS10-079)?
The security update package in this bulletin, MS10-079, for Microsoft Office Web Apps (KB2346411) also addresses the vulnerabilities described in MS10-072. Users with Microsoft Office Web Apps installed will only need to install the KB2346411 security update package once.

MS10-080 also describes vulnerabilities in Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, and Open XML File Format Converter for Mac. How does MS10-080 relate to this bulletin (MS10-079)?
The security update packages in this bulletin, MS10-079, for Microsoft Office 2004 for Mac (KB2422343), Microsoft Office 2008 for Mac (KB2422352), and Open XML File Format Converter for Mac (KB2422398) also address the vulnerabilities described in MS10-080. Users with Microsoft Office 2004 for Mac, Microsoft Office 2008 for Mac, or Open XML File Format Converter for Mac installed will only need to install these security update packages once.

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

What is the Microsoft Word Viewer?
The Microsoft Word Viewer is a replacement for Word Viewer 2003 and all previous Word Viewer versions. With Word Viewer, you can view, print, and copy Word documents, even if you do not have Word installed. For more details about currently supported Office viewers, see Supported versions of the Office viewers.

What is Microsoft Office Web Apps?
Microsoft Office Web Apps is the online companion to Office Word, Excel, PowerPoint and OneNote applications that enables users regardless of their location to access documents and edit documents. Users can view, share, and work on documents with others online across personal computers, mobile phones, and the Web. Office Web Apps is available to business customers with Microsoft Office 2010 volume licensing and document management solutions based on Microsoft SharePoint 2010 products.

What is Microsoft Word Web App?
Microsoft Word Web App is part of Microsoft Office Web Apps, available in organizations that have configured Office Web Apps on Microsoft SharePoint Server 2010. Word Web App extends your Microsoft Word experience to the Web browser, where you can work with documents directly on the website where the document is stored. For more information about Word Web App, see Introduction to Word Web App.

Where are updates for Microsoft Office Web Apps applied?
Customers who have deployed Microsoft Office Web Apps in a SharePoint environment will need to apply the updates for Microsoft Office Web Apps on the servers on which those components are installed. For more information about deploying Microsoft Web Apps, see the Microsoft TechNet article, Understanding Office Web Apps.

Note The updates for Microsoft Office Web Apps do not apply to the client workstations that use a Web browser to access Microsoft Office Web Apps.

How are Microsoft Office standalone programs affected by the vulnerabilities?
A Microsoft Office standalone program is affected with the same severity rating as the corresponding component in a Microsoft Office Suite. For example, a standalone installation of Microsoft Word is affected with the same severity rating as an installation of Microsoft Word 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

Severity Ratings and Vulnerability Identifiers

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

Table: Part 1 (continued below in Part 2)

Affected Software	Word Uninitialized Pointer Vulnerability - CVE-2010-2747	Word Boundary Check Vulnerability - CVE-2010-2748	Word Index Vulnerability - CVE-2010-2750	Word Stack Overflow Vulnerability - CVE-2010-3214	Word Return Value Vulnerability - CVE-2010-3215	Word Bookmarks Vulnerability - CVE-2010-3216
Microsoft Office Suites and Components
Microsoft Word 2002 Service Pack 3	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution
Microsoft Word 2003 Service Pack 3	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable
Microsoft Word 2007 Service Pack 2	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable
Microsoft Word 2010 (32-bit editions)	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable
Microsoft Word 2010 (64-bit editions)	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable
Microsoft Office for Mac
Microsoft Office 2004 for Mac	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution
Microsoft Office 2008 for Mac	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable
Open XML File Format Converter for Mac	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable
Other Microsoft Office Software
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable
Microsoft Word Viewer	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable
Other Productivity Software
Microsoft Office Web Apps	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable
Microsoft Word Web App	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Not applicable	Not applicable

Table: Part 2 (continued from Part 1)

Affected Software	Word Pointer Vulnerability - CVE-2010-3217	Word Heap Overflow Vulnerability - CVE-2010-3218	Word Index Parsing Vulnerability - CVE-2010-3219	Word Parsing Vulnerability - CVE-2010-3220	Word Parsing Vulnerability - CVE-2010-3221	Aggregate Severity Rating
Microsoft Office Suites and Components
Microsoft Word 2002 Service Pack 3	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important Remote Code Execution	Important
Microsoft Word 2003 Service Pack 3	Not applicable	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Important
Microsoft Word 2007 Service Pack 2	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important
Microsoft Word 2010 (32-bit editions)	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important
Microsoft Word 2010 (64-bit editions)	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important
Microsoft Office for Mac
Microsoft Office 2004 for Mac	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Important Remote Code Execution	Important
Microsoft Office 2008 for Mac	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important
Open XML File Format Converter for Mac	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important
Other Microsoft Office Software
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important
Microsoft Word Viewer	Not applicable	Not applicable	Not applicable	Not applicable	Important Remote Code Execution	Important
Other Productivity Software
Microsoft Office Web Apps	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important
Microsoft Word Web App	Not applicable	Not applicable	Not applicable	Not applicable	Not applicable	Important

Word Uninitialized Pointer Vulnerability - CVE-2010-2747

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

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

Mitigating Factors for Word Uninitialized Pointer Vulnerability - CVE-2010-2747

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

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

Workarounds for Word Uninitialized Pointer Vulnerability - CVE-2010-2747

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

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Uninitialized Pointer Vulnerability - CVE-2010-2747

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

What causes the vulnerability?
When Microsoft Word parses a specially crafted Word file, system memory may become corrupted in such a way that an attacker could execute arbitrary code

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

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

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

In a Web-based attack scenario, an attacker would have to host a Web site that contains a Word file that is used to attempt to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content could contain specially crafted content that could exploit this vulnerability. An attacker would have no way to force users to visit a specially crafted Web site. Instead, an attacker would have to convince them to visit the Web site, typically by getting them to click a link that takes them to the attacker's site, and then convince them to open the specially crafted Word file.

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word 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.

Word Boundary Check Vulnerability - CVE-2010-2748

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

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

Mitigating Factors for Word Boundary Check Vulnerability - CVE-2010-2748

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

Workarounds for Word Boundary Check Vulnerability - CVE-2010-2748

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Boundary Check Vulnerability - CVE-2010-2748

What causes the vulnerability?
When Microsoft Word parses a specially crafted Word file, an improper boundary check may cause system memory to become corrupted in such a way that an attacker could execute arbitrary code.

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word files.

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

Word Index Vulnerability - CVE-2010-2750

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

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

Mitigating Factors for Word Index Vulnerability - CVE-2010-2750

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

Workarounds for Word Index Vulnerability - CVE-2010-2750

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Index Vulnerability - CVE-2010-2750

What causes the vulnerability?
When Microsoft Word parses a specially crafted Word file that contains a malformed index value, system memory may become corrupted in such a way that an attacker could execute arbitrary code.

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word files.

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

Word Stack Overflow Vulnerability - CVE-2010-3214

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

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

Mitigating Factors for Word Stack Overflow Vulnerability - CVE-2010-3214

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

Workarounds for Word Stack Overflow Vulnerability - CVE-2010-3214

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

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

Note Modifying the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from incorrect modification of the Registry can be solved. Modify the Registry at your own risk.

For Office 2003
```
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Security\FileOpenBlock]

"BinaryFiles"=dword:00000000
```
Note In order to use 'FileOpenBlock' with Microsoft Office 2003, all of the latest security updates for Microsoft Office 2003 must be applied.

For Office 2007
```
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]

"BinaryFiles"=dword:00000000
```
Note In order to use 'FileOpenBlock' with the 2007 Microsoft Office system, all of the latest security updates for the 2007 Microsoft Office system must be applied.

For Office 2010 Open Word 2010 and follow the steps below:
1. Click the File tab.
2. Under Help, click Options.
3. Click TrustCenter, and then click Trust Center Settings.
4. In the Trust Center, click File Block Settings.
5. Ensure the Open check box is selected for the following file types:
  - Word 2003 Binary Documents and Templates
  - Word XP Binary Documents and Templates
  - Word 2000 Binary Documents and Templates
  - Word 97 Binary Documents and Templates
  - Word 95 Binary Documents and Templates
  - Word 6.0 Binary Documents and Templates
  - Word 2 and earlier Binary Documents and Templates
6. Under Open behavior for selected file types, select "Do not open selected file types" or select "Open selected file types in Protected View" (either choice will block the attack vector to the vulnerable code).
7. Click OK to apply the File Block Settings.
Alternatively, file block can be applied using Group Policy. For more information, see the TechNet article, Plan file block settings for Office 2010.

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

How to undo the workaround.

For Office 2003
```
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Security\FileOpenBlock]

"BinaryFiles"=dword:00000001
```
For Office 2007
```
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Word\Security\FileOpenBlock]

"BinaryFiles"=dword:00000001
```
For Office 2010 Open Word 2010 and follow these steps:
1. Click the File tab.
2. Under Help, click Options.
3. Click TrustCenter, and then click Trust Center Settings.
4. In the Trust Center, click File Block Settings.
5. Clear the Open check box for the file types that you previously selected.
6. Click OK to apply the File Block settings.

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

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

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

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

Download the FileFormatConverters.exe package now

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

https:

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

Do not open or save Word 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 Word Stack Overflow Vulnerability - CVE-2010-3214

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

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word files.

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

Word Return Value Vulnerability - CVE-2010-3215

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

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

Mitigating Factors for Word Return Value Vulnerability - CVE-2010-3215

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

Workarounds for Word Return Value Vulnerability - CVE-2010-3215

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Return Value Vulnerability - CVE-2010-3215

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

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word files.

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

Word Bookmarks Vulnerability - CVE-2010-3216

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

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

Mitigating Factors for Word Bookmarks Vulnerability - CVE-2010-3216

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

Workarounds for Word Bookmarks Vulnerability - CVE-2010-3216

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Bookmarks Vulnerability - CVE-2010-3216

What causes the vulnerability?
When Microsoft Word parses a specially crafted Word file that contains bookmarks, system memory may become corrupted in such a way that an attacker could execute arbitrary code.

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

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word files.

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

Word Pointer Vulnerability - CVE-2010-3217

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

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

Mitigating Factors for Word Pointer Vulnerability - CVE-2010-3217

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

Workarounds for Word Pointer Vulnerability - CVE-2010-3217

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Pointer Vulnerability - CVE-2010-3217

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

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word 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.

Word Heap Overflow Vulnerability - CVE-2010-3218

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

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

Mitigating Factors for Word Heap Overflow Vulnerability - CVE-2010-3218

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

Workarounds for Word Heap Overflow Vulnerability - CVE-2010-3218

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Heap Overflow Vulnerability - CVE-2010-3218

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

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word files.

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

Word Index Parsing Vulnerability - CVE-2010-3219

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

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

Mitigating Factors for Word Index Parsing Vulnerability - CVE-2010-3219

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

Workarounds for Word Index Parsing Vulnerability - CVE-2010-3219

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Index Parsing Vulnerability - CVE-2010-3219

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

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word 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.

Word Parsing Vulnerability - CVE-2010-3220

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

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

Mitigating Factors for Word Parsing Vulnerability - CVE-2010-3220

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

Workarounds for Word Parsing Vulnerability - CVE-2010-3220

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Parsing Vulnerability - CVE-2010-3220

What causes the vulnerability?
When Microsoft Word parses a specially crafted Word file, system memory may be corrupted in such a way that an attacker could execute arbitrary code.

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word files.

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

Word Parsing Vulnerability - CVE-2010-3221

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

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

Mitigating Factors for Word Parsing Vulnerability - CVE-2010-3221

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

Workarounds for Word Parsing Vulnerability - CVE-2010-3221

Do not open Word documents from untrusted sources

Do not open or save Word 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 Word Parsing Vulnerability - CVE-2010-3221

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

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

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

What does the update do?
This update addresses the vulnerability by modifying the way that Microsoft Word parses specially crafted Word files.

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

Update Information

Detection and Deployment Tools and Guidance

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

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

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

Detection and Deployment Guidance

Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.

Microsoft Baseline Security Analyzer

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

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

Software	MBSA
Microsoft Office XP Service Pack 3	Yes
Microsoft Office 2003 Service Pack 3	Yes
Microsoft Office 2007 Service Pack 2	Yes
Microsoft Office 2010 (32-bit editions)	Yes
Microsoft Office 2010 (64-bit editions)	Yes
Microsoft Office 2004 for Mac	No
Microsoft Office 2008 for Mac	No
Open XML File Format Converter for Mac	No
Microsoft Word Viewer	Yes
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2	Yes
Microsoft Word Web Apps	Yes

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

Windows Server Update Services

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

Systems Management Server

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

Software	SMS 2.0	SMS 2003 with SUIT	SMS 2003 with ITMU	Configuration Manager 2007
Microsoft Office XP Service Pack 3	No	No	Yes	Yes
Microsoft Office 2003 Service Pack 3	No	No	Yes	Yes
Microsoft Office 2007 Service Pack 2	No	No	Yes	Yes
Microsoft Office 2010 (32-bit editions)	No	No	Yes	Yes
Microsoft Office 2010 (64-bit editions)	No	No	Yes	Yes
Microsoft Office 2004 for Mac	No	No	No	No
Microsoft Office 2008 for Mac	No	No	No	No
Open XML File Format Converter for Mac	No	No	No	No
Microsoft Word Viewer	No	No	Yes	Yes
Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats Service Pack 2	No	No	Yes	Yes
Microsoft Word Web Apps	No	No	Yes	Yes

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.

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

Update Compatibility Evaluator and Application Compatibility Toolkit

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

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

Security Update Deployment

Affected Software

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

Word 2002 (all editions)

Reference Table

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

Inclusion in Future Service Packs	There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user intervention	officexp-KB2328360-FullFile-ENU.exe /q:a
Installing without restarting	officexp-KB2328360-FullFile-ENU.exe /r:n
Update log file	Not applicable
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. \ \ For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel.\ \ Note When you remove this update, you may be prompted to insert the Microsoft Office XP CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
File Information	See Microsoft Knowledge Base Article 2328360
Registry Key Verification	Not applicable

Office Features

The following table contains the list of feature names (case sensitive) that must be reinstalled for the update. To install all features, you can use REINSTALL=ALL or you can install the following features:

Product	Feature
PIPC1, PROPLUS, PRO, SBE, STD, STDEDU, WORD	WORDFiles

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

Deployment Information

Installing the Update

You can install the update from the appropriate download link in the Affected and Non-Affected Software section. If you installed your application from a server location, the server administrator must instead update the server location with the administrative update and deploy that update to your system. For more information about Administrative Installation Points, refer to the Office Administrative Installation Point information in the Detection and deployment Tools and Guidance subsection.

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the 2.0 or later version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Switch	Description
/q	Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u	Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a	Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path	Specifies the target folder for extracting files.
/c	Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path	Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n	Never restarts the system after installation.
/r:I	Prompts the user to restart the system if a restart is required, except when used with /q:a.
/r:a	Always restarts the system after installation.
/r:s	Restarts the system after installation without prompting the user.
/n:v	No version checking - Install the program over any earlier version.

Note You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

To remove this security update, use the Add or Remove Programs tool in Control Panel. Note When you remove this update, you may be prompted to insert the Microsoft Office XP CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

Verifying That the Update Has Been Applied

Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification

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

Word 2003 (all editions) and Word Viewer (all versions)

Reference Table

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

Inclusion in Future Service Packs	There are no more service packs planned for this software. The update for this issue may be included in a future update rollup.
Deployment
Installing without user intervention	For Word 2003:\ Office2003-kb2344911-fullfile-enu.exe /q:a
For Word Viewer:\ Office-kb2345009-fullfile-enu.exe /q:a
Installing without restarting	For Word 2003:\ Office2003-kb2344911-fullfile-enu.exe /r:n
For Word Viewer:\ Office-kb2345009-fullfile-enu.exe /r:n
Update log file	Not applicable
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance. \ \ For features you can selectively install, see the Office Features for Administrative Installations subsection in this section.
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel.\ \ Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
File Information	See Microsoft Knowledge Base Article 2344911
Registry Key Verification	Not applicable

Office Features

Product	Feature
BASIC11, PERS11, PRO11SB, PROI11, PRO11, STDP11, STD11, WORD11	WORDFiles
Word Viewer 2003	WORDVIEWFiles

Deployment Information

Installing the Update

This security update requires that Windows Installer 2.0 or later be installed on the system. All supported versions of Windows include Windows Installer 2.0 or a later version.

To install the 2.0 or later version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Switch	Description
/q	Specifies quiet mode, or suppresses prompts, when files are being extracted.
/q:u	Specifies user-quiet mode, which presents some dialog boxes to the user.
/q:a	Specifies administrator-quiet mode, which does not present any dialog boxes to the user.
/t:path	Specifies the target folder for extracting files.
/c	Extracts the files without installing them. If /t:path is not specified, you are prompted for a target folder.
/c:path	Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/r:n	Never restarts the system after installation.
/r:I	Prompts the user to restart the system if a restart is required, except when used with /q:a.
/r:a	Always restarts the system after installation.
/r:s	Restarts the system after installation without prompting the user.
/n:v	No version checking - Install the program over any earlier version.

Note You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841.

Removing the Update

To remove this security update, use the Add or Remove Programs tool in Control Panel.

Note When you remove this update, you may be prompted to insert the Microsoft Office 2003 CD in the CD drive. Additionally, you may not have the option to uninstall the update from the Add or Remove Programs tool in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.

Verifying that the Update Has Been Applied

Microsoft Baseline Security Analyzer

To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
File Version Verification

Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1. Click Start and then enter an update file name in the Start Search box.
2. When the file appears under Programs, right-click the file name and click Properties.
3. On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
4. You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
5. Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.

Word 2007 (all editions) and Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats (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 Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	For Word 2007:\ Word2007-kb2344993-fullfile-x86-glb.exe /passive
For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats:\ office2007-kb2345043-v2-fullfile-x86-glb.exe /passive
Installing without restarting	For Word 2007:\ Word2007-kb2344993-fullfile-x86-glb.exe /norestart
For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats:\ office2007-kb2345043-v2-fullfile-x86-glb.exe /norestart
Update log file	Not applicable
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatching	Not applicable
Removal Information	Use Add or Remove Programs tool in Control Panel.
File Information	For Word 2007, see Microsoft Knowledge Base Article 2344993\ \ For Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats, see Microsoft Knowledge Base Article 2345043
Registry Key Verification	Not applicable

Deployment Information

Installing the Update

This security update requires that Windows Installer 3.1 or later be installed on the system.

To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Switch	Description
/? or /help	Displays usage dialog.
/passive	Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quiet	Specifies quiet mode, or suppresses prompts, when files are being extracted.
/norestart	Suppresses restarting the system if the update requires a restart.
/forcerestart	Automatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extract	Extracts the files without installing them. You are prompted for a target folder.
/extract:<path>	Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/lang:<LCID>	Forces the use of a specific language, when the update package supports that language.
/log:<log file>	Enables logging, by both Vnox and Installer, during the update installation.

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

Word 2010 (all editions), Office Web Apps, and Word 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 Packs	The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention	For Microsoft Word 2010 (32-bit editions):\ Word2010-kb2345000-fullfile-x86-glb.exe /passive
For Microsoft Word 2010 (64-bit editions):\ Word2010-kb2345000-fullfile-x64-glb.exe /passive
For Microsoft Word Web App:\ wordwebapp2010-kb2345015-fullfile-x64-glb.exe /passive
For Microsoft Office Web Apps:\ webapplications2010-kb2346411-fullfile-x64-glb.exe /passive
Installing without restarting	For Microsoft Word 2010 (32-bit editions):\ Word2010-kb2345000-fullfile-x86-glb.exe /norestart
For Microsoft Word 2010 (64-bit editions):\ Word2010-kb2345000-fullfile-x64-glb.exe /norestart
For Microsoft Word Web App:\ wordwebapp2010-kb2345015-fullfile-x64-glb.exe /norestart
For Microsoft Office Web Apps:\ webapplications2010-kb2346411-fullfile-x64-glb.exe /norestart
Update log file	Not applicable
Further information	For detection and deployment, see the earlier section, Detection and Deployment Tools and Guidance.
Restart Requirement
Restart required?	In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.\ \ To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatching	Not applicable
Removal Information	For Microsoft Word 2010, use Add or Remove Programs tool in Control Panel.
For Microsoft Office Web Apps and Microsoft Word Web App, this security update cannot be removed.
File Information	For Microsoft Office 2010, see Microsoft Knowledge Base Article 2345000
For Microsoft Word Web App, see Microsoft Knowledge Base Article 2345015
For Microsoft Office Web Apps, see Microsoft Knowledge Base Article 2346411
Registry Key Verification	Not applicable

Deployment Information

Installing the Update

This security update requires that Windows Installer 3.1 or later be installed on the system.

To install the 3.1 or later version of Windows Installer, visit one of the following Microsoft Web sites:

For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.

This security update supports the following setup switches.

Switch	Description
/? or /help	Displays usage dialog.
/passive	Specifies passive mode. Requires no user interaction; users see basic progress dialogs but cannot cancel.
/quiet	Specifies quiet mode, or suppresses prompts, when files are being extracted.
/norestart	Suppresses restarting the system if the update requires a restart.
/forcerestart	Automatically restarts the system after applying the update, regardless of whether the update requires the restart.
/extract	Extracts the files without installing them. You are prompted for a target folder.
/extract:<path>	Overrides the install command that is defined by author. Specifies the path and name of the Setup.inf or .exe file.
/lang:<LCID>	Forces the use of a specific language, when the update package supports that language.
/log:<log file>	Enables logging, by both Vnox and Installer, during the update installation.

Removing the Update

To remove this security update, use the Add or Remove Programs tool in Control Panel.

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.1 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.1 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.1 Update volume window, double-click the Microsoft Office 2004 for Mac 11.6.1 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.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:

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

If the Version number is 11.6.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.

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.7 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.7 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.7 Update volume window, double-click the Microsoft Office 2008 for Mac 12.2.7 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.7 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:

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

If the Version number is 12.2.7, 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.7 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.7 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.7 Update volume window, double-click the Open XML File Format Converter for Mac 1.1.7 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.7 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:

In the Finder, navigate to the Application Folder.
Select the file, Open XML File Format Converter.
On the File menu, click Get Info or Show Info.

If the Version number is 1.1.7, 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:

Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Uninitialized Pointer Vulnerability (CVE-2010-2747)
Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Boundary Check Vulnerability (CVE-2010-2748)
Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Index Vulnerability (CVE-2010-2750)
Nicolas Joly of VUPEN Vulnerability Research Team for reporting the Word Stack Overflow Vulnerability (CVE-2010-3214)
Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Return Value Vulnerability (CVE-2010-3215)
Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Bookmarks Vulnerability (CVE-2010-3216)
Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Pointer Vulnerability (CVE-2010-3217)
Alin Rad Pop of Secunia Research for reporting the Word Pointer Vulnerability (CVE-2010-3217)
Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Heap Overflow Vulnerability (CVE-2010-3218)
Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Index Parsing Vulnerability (CVE-2010-3219)
Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Parsing Vulnerability (CVE-2010-3220)
Chaouki Bekrar of VUPEN Vulnerability Research Team for reporting the Word Parsing Vulnerability (CVE-2010-3221)

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 (October 12, 2010): Bulletin published.
V1.1 (October 13, 2010): Corrected the package name for the Microsoft Office Compatibility Pack (KB2345043) update. This is an informational change only. Customers who have already successfully updated their systems do not need to take any action.
V1.2 (November 3, 2010): Corrected the bulletin replacement information for the Microsoft Word Viewer update (KB2345009). This is an informational change only. There were no changes to the detection logic or the update files.

Built at 2014-04-18T13:49:36Z-07:00 </https:>

Share via

Microsoft Security Bulletin MS10-079 - Important

Vulnerabilities in Microsoft Word Could Allow Remote Code Execution (2293194)

General Information

Executive Summary

Affected and Non-Affected Software

Frequently Asked Questions (FAQ) Related to This Security Update

Vulnerability Information

Severity Ratings and Vulnerability Identifiers

Word Uninitialized Pointer Vulnerability - CVE-2010-2747

Mitigating Factors for Word Uninitialized Pointer Vulnerability - CVE-2010-2747

Workarounds for Word Uninitialized Pointer Vulnerability - CVE-2010-2747

FAQ for Word Uninitialized Pointer Vulnerability - CVE-2010-2747

Word Boundary Check Vulnerability - CVE-2010-2748

Mitigating Factors for Word Boundary Check Vulnerability - CVE-2010-2748

Workarounds for Word Boundary Check Vulnerability - CVE-2010-2748

FAQ for Word Boundary Check Vulnerability - CVE-2010-2748

Word Index Vulnerability - CVE-2010-2750

Mitigating Factors for Word Index Vulnerability - CVE-2010-2750

Workarounds for Word Index Vulnerability - CVE-2010-2750

FAQ for Word Index Vulnerability - CVE-2010-2750

Word Stack Overflow Vulnerability - CVE-2010-3214

Mitigating Factors for Word Stack Overflow Vulnerability - CVE-2010-3214

Workarounds for Word Stack Overflow Vulnerability - CVE-2010-3214

FAQ for Word Stack Overflow Vulnerability - CVE-2010-3214

Word Return Value Vulnerability - CVE-2010-3215

Mitigating Factors for Word Return Value Vulnerability - CVE-2010-3215

Workarounds for Word Return Value Vulnerability - CVE-2010-3215

FAQ for Word Return Value Vulnerability - CVE-2010-3215

Word Bookmarks Vulnerability - CVE-2010-3216

Mitigating Factors for Word Bookmarks Vulnerability - CVE-2010-3216

Workarounds for Word Bookmarks Vulnerability - CVE-2010-3216

FAQ for Word Bookmarks Vulnerability - CVE-2010-3216

Word Pointer Vulnerability - CVE-2010-3217

Mitigating Factors for Word Pointer Vulnerability - CVE-2010-3217

Workarounds for Word Pointer Vulnerability - CVE-2010-3217

FAQ for Word Pointer Vulnerability - CVE-2010-3217

Word Heap Overflow Vulnerability - CVE-2010-3218

Mitigating Factors for Word Heap Overflow Vulnerability - CVE-2010-3218

Workarounds for Word Heap Overflow Vulnerability - CVE-2010-3218

FAQ for Word Heap Overflow Vulnerability - CVE-2010-3218

Word Index Parsing Vulnerability - CVE-2010-3219

Mitigating Factors for Word Index Parsing Vulnerability - CVE-2010-3219

Workarounds for Word Index Parsing Vulnerability - CVE-2010-3219

FAQ for Word Index Parsing Vulnerability - CVE-2010-3219

Word Parsing Vulnerability - CVE-2010-3220

Mitigating Factors for Word Parsing Vulnerability - CVE-2010-3220

Workarounds for Word Parsing Vulnerability - CVE-2010-3220

FAQ for Word Parsing Vulnerability - CVE-2010-3220

Word Parsing Vulnerability - CVE-2010-3221

Mitigating Factors for Word Parsing Vulnerability - CVE-2010-3221

Workarounds for Word Parsing Vulnerability - CVE-2010-3221

FAQ for Word Parsing Vulnerability - CVE-2010-3221

Update Information

Detection and Deployment Tools and Guidance

Security Update Deployment

Word 2002 (all editions)

Office Features

Deployment Information

Word 2003 (all editions) and Word Viewer (all versions)

Office Features

Deployment Information

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

Deployment Information

Word 2010 (all editions), Office Web Apps, and Word Web App

Deployment Information

Office 2004 for Mac

Deployment Information

Office 2008 for Mac

Deployment Information

Open XML File Format Converter for Mac

Deployment Information

Other Information

Acknowledgments

Microsoft Active Protections Program (MAPP)

Support

Disclaimer

Revisions

Additional resources