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

Microsoft Security Bulletin MS13-072 - Important

Vulnerabilities in Microsoft Office Could Allow Remote Code Execution

Published: September 10, 2013 | Updated: September 13, 2013

Version: 1.1

General Information

Executive Summary

This security update resolves 13 privately reported vulnerabilities in Microsoft Office. The most severe vulnerabilities could allow remote code execution if a specially crafted file is opened in an affected version of Microsoft Office software. An attacker who successfully exploited the most severe vulnerabilities could gain the same user rights as the current 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 supported editions of Microsoft Office 2003 including (Microsoft Word 2003 and Microsoft Word Viewer), Microsoft Office 2007 (including Microsoft Word 2007 and Microsoft Office Compatibility Pack), and Microsoft Word 2010. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses the vulnerabilities by correcting the way that Microsoft Office parses specially crafted files and by correcting the manner in which the XML parser used by Word resolves external entities within a specially crafted file. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

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

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

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

Knowledge Base Article

Knowledge Base Article2845537
File informationYes
SHA1/SHA2 hashesYes
Known issuesNone

Affected and Non-Affected Software

The following software has 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, see Microsoft Support Lifecycle.

Affected Software

Microsoft Office Suite and Other Office SoftwareComponentMaximum Security ImpactAggregate Severity RatingUpdates Replaced
Microsoft Office 2003
Microsoft Office 2003 Service Pack 3
(mso)
(2817474)
Not applicableRemote Code ExecutionImportant2817421 in MS13-051
Microsoft Office 2003 Service Pack 3 Microsoft Word 2003 Service Pack 3
(2817682)
Remote Code ExecutionImportant2810046 in MS13-043
Microsoft Office 2007
Microsoft Office 2007 Service Pack 3
(mso)
(2760411)
Not applicableRemote Code ExecutionImportant2596615 in MS12-057
Microsoft Office 2007 Service Pack 3
(msptls)
(2597973)
Not applicableRemote Code ExecutionImportant2596785 in MS11-089
Microsoft Office 2007 Service Pack 3 Microsoft Word 2007 Service Pack 3
(2767773)
Remote Code ExecutionImportant2760421 in MS12-079
Microsoft Office 2010
Microsoft Office 2010 Service Pack 1 (32-bit editions) Microsoft Word 2010 Service Pack 1 (32-bit editions)
(2760769)
Remote Code ExecutionImportant2760410 in MS12-079
Microsoft Office 2010 Service Pack 1 (32-bit editions) Microsoft Word 2010 Service Pack 1 (32-bit editions)
(2767913)
Remote Code ExecutionImportantNone
Microsoft Office 2010 Service Pack 2 (32-bit editions) Microsoft Word 2010 Service Pack 2 (32-bit editions)
(2760769)
Remote Code ExecutionImportantNone
Microsoft Office 2010 Service Pack 2 (32-bit editions) Microsoft Word 2010 Service Pack 2 (32-bit editions)
(2767913)
Remote Code ExecutionImportantNone
Microsoft Office 2010 Service Pack 1 (64-bit editions) Microsoft Word 2010 Service Pack 1 (64-bit editions)
(2760769)
Remote Code ExecutionImportant2760410 in MS12-079
Microsoft Office 2010 Service Pack 1 (64-bit editions) Microsoft Word 2010 Service Pack 1 (64-bit editions)
(2767913)
Remote Code ExecutionImportantNone
Microsoft Office 2010 Service Pack 2 (64-bit editions) Microsoft Word 2010 Service Pack 2 (64-bit editions)
(2760769)
Remote Code ExecutionImportantNone
Microsoft Office 2010 Service Pack 2 (64-bit editions) Microsoft Word 2010 Service Pack 2 (64-bit editions)
(2767913)
Remote Code ExecutionImportantNone
Other Office Software
Microsoft Office Compatibility Pack Service Pack 3
(2760823)
Not applicableRemote Code ExecutionImportant2760416 in MS12-079
Microsoft Word Viewer
(2817683)
Not applicableRemote Code ExecutionImportant2817361 in MS13-043

 

Non-Affected Software 

Office and Other Software
Microsoft Office for Mac 2011
Microsoft Office 2013 (32-bit editions)
Microsoft Office 2013 (64-bit editions)
Microsoft Office 2013 RT

CVE-2013-3847, CVE-2013-3848, CVE-2013-3849, CVE-2013-3857, and CVE-2013-3858 are described in multiple security bulletins. How are these bulletins related? 
The Word Memory Corruption Vulnerabilities (CVE-2013-3847, CVE-2013-3848, CVE-2013-3849, CVE-2013-3857, CVE-2013-3858) affect the following products:

  • Microsoft Word (MS13-072)
  • Microsoft Office Services and Web Apps (MS13-067)

You need to install only the updates that correspond to the software you have installed on your system. If you need to install more than one of these updates, they can be installed in any sequence.

There are multiple update packages available for some affected software. Do I need to install all the updates listed in the Affected Software table for the software? 
Yes. Customers should apply all updates offered for the software installed on their systems.

Do I need to install these security updates in a particular sequence? 
No. Multiple updates for one version of Microsoft Office software can be applied in any sequence.

I have Microsoft Word 2010 installed. Why am I not being offered the 2767913 update? 
The 2767913 update only applies to systems running specific configurations of Microsoft Office 2010. Other systems will not be offered the update.

I am being offered this update for software I do not have installed on my system. Why am I being offered this update? 
Due to the servicing model for Microsoft Office updates, you may be offered updates for software that you do not have installed on your system. For example, you may be offered an update for a Microsoft Office product even though you do not have the specific Office product installed. For more information on this behavior and recommended actions, see Microsoft Knowledge Base Article 830335.

I am being offered this update for software that is not specifically listed in the Affected Software table. Why am I being offered this update? 
When updates address vulnerable code that exists in a component that is shared between multiple Microsoft Office products or shared between multiple versions of the same Microsoft Office product, the update is considered to be applicable to all supported products and versions that contain the vulnerable component.

For example, when an update applies to Microsoft Office 2007 products, only Microsoft Office 2007 may be specifically listed in the Affected Software table. However, the update could apply to Microsoft Word 2007, Microsoft Excel 2007, Microsoft Visio 2007, Microsoft Compatibility Pack, Microsoft Excel Viewer, or any other Microsoft Office 2007 product that is not specifically listed in the Affected Software table.

For example, when an update applies to Microsoft Office 2010 products, only Microsoft Office 2010 may be specifically listed in the Affected Software table. However, the update could apply to Microsoft Word 2010, Microsoft Excel 2010, Microsoft Visio 2010, Microsoft Visio Viewer, or any other Microsoft Office 2010 product that is not specifically listed in the Affected Software table.

For a list of Microsoft Office products an update may apply to, refer to the Microsoft Knowledge Base Article associated with the specific update.

In some cases, an update may apply to Office products that are specifically listed in the Non-Affected Software table. For example, you may be offered a Microsoft Office security update even though this security bulletin indicates that the Office products or the version of the Office products that you do have installed are not affected. For more information on this behavior and recommended actions, see Microsoft Knowledge Base Article 830335.

Does the offer to update a non-vulnerable version of Microsoft Office software constitute an issue in the servicing model for Microsoft Office updates? 
No. The servicing model is based on how the update applies to shared components of Microsoft Office software. Some of the products offered an update may not access the vulnerable code, and thus the software is not affected by the vulnerability. However, the update mechanism is functioning correctly in that it detects a product version for applicable software on the system that is within the range of product versions that the update applies to, and thus offers the update. This helps to maintain consistency for shared files across Office products.

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

How are Microsoft Office standalone programs affected by 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.

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 has been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, see the Microsoft Support Lifecycle website.

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 Service Pack Lifecycle Support Policy.

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, see the Microsoft Worldwide Information website, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.

Vulnerability Information

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

Table: Part 1 (continued below in Part 2)

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareXML External Entities Resolution Vulnerability - CVE-2013-3160Word Memory Corruption Vulnerability - CVE-2013-3847Word Memory Corruption Vulnerability - CVE-2013-3848Word Memory Corruption Vulnerability - CVE-2013-3849Word Memory Corruption Vulnerability - CVE-2013-3850Word Memory Corruption Vulnerability - CVE-2013-3851
Microsoft Office 2003 Service Pack 3
(mso)
Important 
Information Disclosure
Not applicableNot applicableNot applicableNot applicableImportant 
Remote Code Execution
Microsoft Word 2003 Service Pack 3 Important 
Information Disclosure
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Microsoft Office 2007 Service Pack 3
(mso)
Important 
Information Disclosure
Not applicableNot applicableNot applicableNot applicableImportant 
Remote Code Execution
Microsoft Office 2007 Service Pack 3
(msptls)
Not applicableNot applicableNot applicableNot applicableNot applicableNot applicable
Microsoft Word 2007 Service Pack 3 Important 
Information Disclosure
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Microsoft Word 2010 Service Pack 1 (32-bit editions) Not applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Not applicable
Microsoft Word 2010 Service Pack 2 (32-bit editions) Not applicableNot applicableNot applicableNot applicableImportant 
Remote Code Execution
Not applicable
Microsoft Word 2010 Service Pack 1 (64-bit editions) Not applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Not applicable
Microsoft Word 2010 Service Pack 2 (64-bit editions) Not applicableNot applicableNot applicableNot applicableImportant 
Remote Code Execution
Not applicable
Microsoft Office Compatibility Pack Service Pack 3 Not applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Microsoft Word Viewer Important 
Information Disclosure
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution

 

Table: Part 2 (continued from Part 1)

Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected SoftwareWord Memory Corruption Vulnerability - CVE-2013-3852Word Memory Corruption Vulnerability - CVE-2013-3853Word Memory Corruption Vulnerability - CVE-2013-3854Word Memory Corruption Vulnerability - CVE-2013-3855Word Memory Corruption Vulnerability - CVE-2013-3856Word Memory Corruption Vulnerability - CVE-2013-3857Word Memory Corruption Vulnerability - CVE-2013-3858Aggregate Severity Rating
Microsoft Office 2003 Service Pack 3
(mso)
Not applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableImportant
Microsoft Word 2003 Service Pack 3 Important 
Remote Code Execution
Not applicableNot applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft Office 2007 Service Pack 3
(mso)
Not applicableNot applicableNot applicableNot applicableNot applicableNot applicableNot applicableImportant
Microsoft Office 2007 Service Pack 3
(msptls)
Not applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Not applicableNot applicableNot applicableNot applicableImportant
Microsoft Word 2007 Service Pack 3 Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Not applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft Word 2010 Service Pack 1 (32-bit editions) Important 
Remote Code Execution
Not applicableNot applicableNot applicableNot applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft Word 2010 Service Pack 2 (32-bit editions) Not applicableNot applicableNot applicableNot applicableNot applicableImportant 
Remote Code Execution
Not applicableImportant
Microsoft Word 2010 Service Pack 1 (64-bit editions) Important 
Remote Code Execution
Not applicableNot applicableNot applicableNot applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft Word 2010 Service Pack 2 (64-bit editions) Not applicableNot applicableNot applicableNot applicableNot applicableImportant 
Remote Code Execution
Not applicableImportant
Microsoft Office Compatibility Pack Service Pack 3 Important 
Remote Code Execution
Not applicableNot applicableImportant 
Remote Code Execution
Not applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important
Microsoft Word Viewer Important 
Remote Code Execution
Not applicableNot applicableImportant 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important 
Remote Code Execution
Important

 

An information disclosure vulnerability exists in the way that Microsoft Word parses specially crafted XML files containing external entities.

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

Mitigating Factors

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 email. For an attack to be successful a user must open an attachment that is sent in an email message.
  • In a web-based attack scenario, an attacker could host a website that contains a specially crafted Office file that is used to attempt to exploit this vulnerability. In addition, compromised websites and websites 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 websites. Instead, an attacker would have to convince users to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker’s website, and convince them to open the specially crafted Office file.

Workarounds

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

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

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

FAQ

What is the scope of the vulnerability? 
This is an information disclosure vulnerability. An attacker who successfully exploited this vulnerability could read data from a file located on the target system. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to produce information that could be used to try to further compromise the affected system.

What causes the vulnerability? 
The vulnerability is caused when Microsoft Word improperly handles XML external entities that are resolved within other XML external entity declarations.

What is an XML External Entity? 
An XML document may consist of one or many storage units. These are called entities. They all have content and are all identified by entity name. External entities allow an XML document to refer to an external file. External entities contain either text or binary data. If they contain text, the content of the external file is inserted at the point of reference and parsed as part of the referring document.

What might an attacker use the vulnerability to do? 
An attacker who successfully exploited this vulnerability would be able to read data from files on the target system. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to produce information that could be used to try to further compromise the affected system.

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

In an email attack scenario, an attacker could exploit the vulnerability by sending a specially crafted file to the user and by convincing the user to open the file in an affected version of Microsoft Word.

In a web-based attack scenario, an attacker would have to host a website that contains an file that is used to attempt to exploit this vulnerability. In addition, compromised websites and websites 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 website. Instead, an attacker would have to convince them to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes them to the attacker's site, and then convince them to open the specially crafted file in an affected version of Microsoft Word.

What systems are primarily at risk from the vulnerability? 
This vulnerability requires that a user open a specially crafted file with an affected application for any malicious action to occur. Therefore, any systems where Word files are frequently viewed, such as workstations or terminal servers, are at the most risk from this vulnerability.

What does the update do? 
The update addresses the vulnerability by correcting the manner in which the XML parser used by Word resolves external entities within a specially crafted file.

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.

Remote code execution vulnerabilities exist in the way that affected Microsoft Office software parses specially crafted files. An attacker who successfully exploited these vulnerabilities could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

To view these vulnerabilities as a standard entry in the Common Vulnerabilities and Exposures list, click the link in the following table:

Vulnerability titleCVE number
Word Memory Corruption VulnerabilityCVE-2013-3847
Word Memory Corruption VulnerabilityCVE-2013-3848
Word Memory Corruption VulnerabilityCVE-2013-3849
Word Memory Corruption VulnerabilityCVE-2013-3850
Word Memory Corruption VulnerabilityCVE-2013-3851
Word Memory Corruption VulnerabilityCVE-2013-3852
Word Memory Corruption VulnerabilityCVE-2013-3853
Word Memory Corruption VulnerabilityCVE-2013-3854
Word Memory Corruption VulnerabilityCVE-2013-3855
Word Memory Corruption VulnerabilityCVE-2013-3856
Word Memory Corruption VulnerabilityCVE-2013-3857
Word Memory Corruption VulnerabilityCVE-2013-3858

Mitigating Factors

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 vulnerabilities cannot be exploited automatically through email. For an attack to be successful a user must open an attachment that is sent in an email message.
  • In a web-based attack scenario, an attacker could host a website that contains a specially crafted Office file that is used to attempt to exploit these vulnerabilities. In addition, compromised websites and websites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit these vulnerabilities. In all cases, however, an attacker would have no way to force users to visit these websites. Instead, an attacker would have to convince them to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes users to the attacker’s website, and convince them to open the specially crafted Office file.
  • An attacker who successfully exploited these vulnerabilities could gain the same user rights as the current 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.

Workarounds

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:

  • Install and configure MOICE to be the registered handler for .doc files

    The Microsoft Office Isolated Conversion Environment (MOICE) feature that is added to the Microsoft Office Compatibility Pack can be used to help open Word, Excel, and PowerPoint binary format files more securely. MOICE is supported only when it is used together with Microsoft Office 2003 or together with Microsoft Office 2007. MOICE is not supported for any other version of Microsoft Office. For more information and installlation instructions, see Microsoft Knowledge Base Article 935865.

    To use MOICE to help protect from exploitation of the vulnerabilities, install and configure MOICE to be the registered handler for .doc formatted files.

  • Use Microsoft Office File Block policy to prevent the opening of .doc and .dot binary files

    You can block specific types of files from being opened or saved in Excel, PowerPoint, and Word by configuring settings in either Group Policy or the Office Customization Tool (OCT). For more information about preventing users from opening specific types of files in Microsoft Office, see Plan File block settings.

    To use file block to help protect from exploitation of the vulnerabilities, configure file block to block *.doc and *.dot binary documents and templates for all affected versions of Microsoft Word.

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

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

FAQ

What is the scope of the vulnerabilities? 
These are remote code execution vulnerabilities in the context of the current user.

What causes the vulnerabilities? 
The vulnerabilities are caused when Microsoft Word does not properly handle objects in memory while parsing specially crafted Office files. System memory may be corrupted in such a way that an attacker could execute arbitrary code.

Are these vulnerabilities all addressed in updates for Microsoft Word? 
These vulnerabilities are exploitable through affected versions of Microsoft Word. However, some of the vulnerabilies are addressed in updates for Microsoft Office because the vulnerable code exists in shared components of Microsoft Office. Consult the following table for details:

CVE numberUpdate that addresses the vulnerability
CVE-2013-3847Updates for Microsoft Word
CVE-2013-3848Updates for Microsoft Word
CVE-2013-3849Updates for Microsoft Word
CVE-2013-3850Updates for Microsoft Word
CVE-2013-3851Updates for Microsoft Office (mso)
CVE-2013-3852Updates for Microsoft Word
CVE-2013-3853Updates for Microsoft Office (msptls)
CVE-2013-3854Updates for Microsoft Office (msptls)
CVE-2013-3855Updates for Microsoft Word
CVE-2013-3856Updates for Microsoft Word
CVE-2013-3857Updates for Microsoft Word
CVE-2013-3858Updates for Microsoft Word

Note that the above table does not include the updates for Microsoft Word Viewer and Microsoft Office Compatibility Pack. For more information on how these vulnerabilities relate to affected software, refer to the Severity Ratings and Vulnerability Identifiers section of this bulletin.

What might an attacker use the vulnerabilities to do? 
An attacker who successfully exploited these vulnerabilities could run arbitrary code in the context of the current user. If the current 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 vulnerabilities? 
Exploitation of these vulnerabilities requires that a user open a specially crafted file with an affected version of Microsoft Office software.

In an email attack scenario, an attacker could exploit the vulnerabilities by sending a specially crafted file to the user and by convincing the user to open the file in an affected version of Microsoft Office software.

In a web-based attack scenario, an attacker could host a website that contains an file that is used to attempt to exploit these vulnerabilities. In addition, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could exploit these vulnerabilities. An attacker would have no way to force users to visit a specially crafted website. Instead, an attacker would have to convince them to visit the website, typically by getting them to click a link in an email message or Instant Messenger message that takes them to the attacker's site, and then convince them to open the specially crafted file in an affected version of Microsoft Office software.

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

What does the update do? 
This update addresses the vulnerabilities by correcting the way that Microsoft Office parses specially crafted files.

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

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

Update Information

Several resources are available to help administrators deploy security updates. 

  • Microsoft Baseline Security Analyzer (MBSA) lets administrators scan local and remote systems for missing security updates and common security misconfigurations. 
  • Windows Server Update Services (WSUS), Systems Management Server (SMS), and System Center Configuration Manager help administrators distribute security updates. 
  • The Update Compatibility Evaluator components included with Application Compatibility Toolkit aid in streamlining the testing and validation of Windows updates against installed applications. 

For more information about these tools and guidance in deploying security updates across networks, see Security Tools for IT Pros

Affected Software

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

Microsoft Office 2003 (all editions), Word 2003 (all editions), Word Viewer

Reference Table

The following table contains the security update information for this software.

Security update file nameFor Microsoft Office 2003 Service Pack 3:
office2003-kb2817474-fullfile-enu.exe
For Microsoft Word 2003 Service Pack 3:
office2003-kb2817682-fullfile-enu.exe
For Microsoft Word Viewer:
office-kb2817683-fullfile-enu.exe
Installation switchesSee Microsoft Knowledge Base Article 197147
Restart requirementIn 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.
Removal informationUse Add or Remove Programs item 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 item in Control Panel. There are several possible causes for this issue. For more information about the removal, see Microsoft Knowledge Base Article 903771.
File informationFor Microsoft Office 2003 Service Pack 3:
See Microsoft Knowledge Base Article 2817474
For Microsoft Word 2003 Service Pack 3:
See Microsoft Knowledge Base Article 2817682
For Microsoft Word Viewer:
See Microsoft Knowledge Base Article 2817683
Registry key verificationNot applicable

Microsoft Office 2007 (all editions), Word 2007 (all editions), Office Compatibility Pack

Reference Table

The following table contains the security update information for this software.

Security update file nameFor Microsoft Office 2007:
msptls2007-kb2597973-fullfile-x86-glb.exe
mso2007-kb2760411-fullfile-x86-glb.exe
For Microsoft Word 2007:
word2007-kb2767773-fullfile-x86-glb.exe
For Microsoft Office Compatibility Pack:
wordconv2007-kb2760823-fullfile-x86-glb.exe
Installation switchesSee Microsoft Knowledge Base Article 912203
Restart requirementIn 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.
Removal informationUse Add or Remove Programs item in Control Panel.
File informationFor Microsoft Office 2007:
See Microsoft Knowledge Base Article 2597973
See Microsoft Knowledge Base Article 2760411
For Microsoft Word 2007:
See Microsoft Knowledge Base Article 2767773
For Microsoft Office Compatibility Pack:
See Microsoft Knowledge Base Article 2760823
Registry key verificationNot applicable

Microsoft Office 2010 (all editions), Word 2010 (all editions)

Reference Table

The following table contains the security update information for this software.

Security update file nameFor Microsoft Word 2010 (32-bit editions):
word2010-kb2760769-fullfile-x86-glb.exe
kb24286772010-kb2767913-fullfile-x86-glb.exe
For Microsoft Word 2010 (64-bit editions):
word2010-kb2760769-fullfile-x64-glb.exe
kb24286772010-kb2767913-fullfile-x64-glb.exe
Installation switchesSee Microsoft Knowledge Base Article 912203
Restart requirementIn 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.
Removal informationUse Add or Remove Programs item in Control Panel.
File informationFor Microsoft Word 2010:
See Microsoft Knowledge Base Article 2760769
See Microsoft Knowledge Base Article 2767913
Registry key verificationNot applicable

Other Information

Acknowledgments

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

  • Timur Yunusov, Alexey Osipov, and Ilya Karpov of Positive Technologies for reporting the XML External Entities Resolution Vulnerability (CVE-2013-3160)
  • Mateusz Jurczyk, Ivan Fratric, and Ben Hawkes of the Google Security Team for reporting multiple Memory Corruption Vulnerabilities in Microsoft Word (CVE-2013-3847, CVE-2013-3848, CVE-2013-3849, CVE-2013-3850, CVE-2013-3851, CVE-2013-3852, CVE-2013-3853, CVE-2013-3854, CVE-2013-3855, CVE-2013-3856, CVE-2013-3857, CVE-2013-3858)

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 go to the active protections websites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.

Support

How to obtain help and support for this security update

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 (September 10, 2013): Bulletin published.
  • V1.1 (September 13, 2013): Revised bulletin to announce detection changes for the Microsoft Office 2007 update (2760411) and the Microsoft Word 2010 update (2767913). These are detection changes only. There were no changes to the update files. Customers who have successfully installed the updates do not need to take any action. Also updated the Known Issues entry in the Knowledge Base Article section from "Yes" to "None".

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

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