Microsoft Security Bulletin MS16-107 - Critical

• 10/11/2017
• 23 minutes to read
• Contributors
  • 

Security Update for Microsoft Office (3185852)

Published: September 13, 2016 | Updated: September 22, 2016

Version: 2.0

Executive Summary

This security update resolves vulnerabilities in Microsoft Office. The most severe of the vulnerabilities could allow remote code execution if a user opens a specially crafted Microsoft Office file. An attacker who successfully exploited the vulnerabilities could run arbitrary code in the context of the current user. Customers whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

For more information, see the Affected Software and Vulnerability Severity Ratings section.

The security update addresses the vulnerabilities by correcting how:

• Microsoft Office saves documents.
• Click-to-Run components handle memory addresses.
• affected versions of Office and Office components handle objects in memory.
• Microsoft Outlook determines the end of MIME messages.

For more information about the vulnerabilities, see the Vulnerability Information section.

For more information about this update, see Microsoft Knowledge Base Article 3185852.

Affected Software and Vulnerability Severity Ratings

The following software versions or editions are affected. Versions or editions that are not listed 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.

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.

Microsoft Office Software (Table 1 of 2)

^[2]This reference is for the Click-to-Run (C2R) version only. For more information and the current Click-to-Run version number, see Update Office 2013 or Office 365.

^[3]As of September 22, 2016, the 3186805 update is available for Microsoft Office for Mac 2011, and the 3186807 update is available for Microsoft Office 2016 for Mac. For more information, see Microsoft Knowledge Base Article 3186805 and Microsoft Knowledge Base Article 3186807.

*The Updates Replaced column shows only the latest update in a chain of superseded updates. For a comprehensive list of updates replaced, go to the Microsoft Update Catalog, search for the update number, and then view update details (updates replaced information is on the Package Details tab).

Microsoft Office Software (Table 2 of 2)

^[2]This reference is for the Click-to-Run (C2R) version only. For more information and the current Click-to-Run version number, see Update Office 2013 or Office 365.

^[3]As of September 22, 2016, the 3186805 update is available for Microsoft Office for Mac 2011, and the 3186807 update is available for Microsoft Office 2016 for Mac. For more information, see Microsoft Knowledge Base Article 3186805 and Microsoft Knowledge Base Article 3186807.

*The Updates Replaced column shows only the latest update in a chain of superseded updates. For a comprehensive list of updates replaced, go to the Microsoft Update Catalog, search for the update number, and then view update details (updates replaced information is on the Package Details tab).

Microsoft Office Services and Web Apps

Update FAQ

I am being offered this update for software that is not specifically indicated as being affected in the Affected Software and Vulnerability Severity Ratings 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. Furthermore, 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 more information on this behavior and recommended actions, see Microsoft Knowledge Base Article 830335. For a list of Microsoft Office products that an update may apply to, refer to the Microsoft Knowledge Base Article associated with the specific update.

Vulnerability Information

Microsoft APP-V ASLR Bypass – CVE-2016-0137

An information disclosure vulnerability exists in the way that the Click-to-Run (C2R) components handle objects in memory, which could lead to an Address Space Layout Randomization (ASLR) bypass.

An attacker who successfully exploited the information disclosure vulnerability could use the obtained information to bypass the ASLR security mechanism in Windows, which helps protect users from a broad class of vulnerabilities. The ASLR bypass by itself does not allow arbitrary code execution; however, an attacker could use the ASLR bypass in conjunction with another vulnerability, such as a remote code execution vulnerability, that could leverage the ASLR bypass to run arbitrary code.

To exploit the ASLR bypass, an attacker would have to log on to an affected system and run a specially crafted application. Workstations are primarily vulnerable to the potential ASLR bypass.

The security update addresses the ASLR bypass by correcting how C2R components handle memory addresses.

The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list: