Microsoft Security Bulletin MS16-142 - Critical
Cumulative Security Update for Internet Explorer (3198467)
Published: November 8, 2016 | Updated: December 13, 2016
Version: 2.0
Executive Summary
This security update resolves vulnerabilities in Internet Explorer. The most severe of the vulnerabilities could allow remote code execution if a user views a specially crafted webpage using Internet Explorer. An attacker who successfully exploited the vulnerabilities could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
This security update is rated Critical for Internet Explorer 9 (IE 9), and Internet Explorer 11 (IE 11) on affected Windows clients, and Moderate for Internet Explorer 9 (IE 9), Internet Explorer 10 (IE 10), and Internet Explorer 11 (IE 11) on affected Windows servers. For more information, see the Affected Software section.
The update addresses the vulnerabilities by correcting how Internet Explorer:
- modifies objects in memory
- uses the XSS filter to handle RegEx
For more information about the vulnerabilities, see the Vulnerability Information section.
For more information about this update, see Microsoft Knowledge Base Article 3198467.
Affected Software
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.
Operating System | Component | Maximum Security Impact | Aggregate Severity Rating | Updates Replaced* |
---|---|---|---|---|
Internet Explorer 9 | ||||
Windows Vista Service Pack 2 | Internet Explorer 9 (3197655) | Remote Code Execution | Critical | 3191492 in MS16-118 |
Windows Vista x64 Edition Service Pack 2 | Internet Explorer 9 (3197655) | Remote Code Execution | Critical | 3191492 in MS16-118 |
Windows Server 2008 for 32-bit Systems Service Pack 2 | Internet Explorer 9 (3197655) | Remote Code Execution | Moderate | 3191492 in MS16-118 |
Windows Server 2008 for x64-based Systems Service Pack 2 | Internet Explorer 9 (3197655) | Remote Code Execution | Moderate | 3191492 in MS16-118 |
Internet Explorer 10 | ||||
Windows Server 2012 Security Only[4] | Internet Explorer 10[1] (3197876) | Remote Code Execution | Moderate | None |
Windows Server 2012 Monthly Roll-Up[4] | Internet Explorer 10[1] (3197877) | Remote Code Execution | Moderate | 3185332 in MS16-118 |
Internet Explorer 11 | ||||
Windows 7 for 32-bit Systems Service Pack 1 Security Only[4] | Internet Explorer 11 (3197867) | Remote Code Execution | Critical | None |
Windows 7 for 32-bit Systems Service Pack 1 Monthly Roll Up[4] | Internet Explorer 11 (3197868) | Remote Code Execution | Critical | 3185330 in MS16-118 |
Windows 7 for x64-based Systems Service Pack 1 Security Only[4] | Internet Explorer 11 (3197867) | Remote Code Execution | Critical | None |
Windows 7 for x64-based Systems Service Pack 1 Monthly Roll-Up[4] | Internet Explorer 11 (3197868) | Remote Code Execution | Critical | 3185330 in MS16-118 |
Windows Server 2008 R2 for x64-based Systems Service Pack 1 Security Only[4] | Internet Explorer 11[1] (3197867) | Remote Code Execution | Moderate | None |
Windows Server 2008 R2 for x64-based Systems Service Pack 1 Monthly Roll-Up[4] | Internet Explorer 11 (3197868) | Remote Code Execution | Moderate | 3185330 in MS16-118 |
Windows 8.1 for 32-bit Systems Security Only[4] | Internet Explorer 11 (3197873) | Remote Code Execution | Critical | None |
Windows 8.1 for 32-bit Systems Monthly Roll-Up[4] | Internet Explorer 11 (3197874) | Remote Code Execution | Critical | 3185331 in MS16-118 |
Windows 8.1 for x64-based Systems Security Only[4] | Internet Explorer 11 (3197873) | Remote Code Execution | Critical | None |
Windows 8.1 for x64-based Systems Monthly Roll-Up[4] | Internet Explorer 11 (3197874) | Remote Code Execution | Critical | 3185331 in MS16-118 |
Windows Server 2012 R2 Security Only[4] | Internet Explorer 11 (3197873) | Remote Code Execution | Moderate | None |
Windows Server 2012 R2 Monthly Roll-Up[4] | Internet Explorer 11 (3197874) | Remote Code Execution | Moderate | 3185331 in MS16-118 |
Windows RT 8.1 Monthly Roll-Up[4] | Internet Explorer 11[1][2](3197874) | Remote Code Execution | Critical | 3185331 in MS16-118 |
Windows 10 for 32-bit Systems[3]\ (3198585) | Internet Explorer 11 | Remote Code Execution | Critical | 3192440 |
Windows 10 for x64-based Systems[3]\ (3198585) | Internet Explorer 11 | Remote Code Execution | Critical | 3192440 |
Windows 10 Version 1511 for 32-bit Systems[3](3198586) | Internet Explorer 11 | Remote Code Execution | Critical | 3192441 |
Windows 10 Version 1511 for x64-based Systems[3](3198586) | Internet Explorer 11 | Remote Code Execution | Critical | 3192441 |
Windows 10 Version 1607 for 32 bit Systems [2] (3200970) | Internet Explorer 11 | Remote Code Execution | Critical | 3194798 |
Windows 10 Version 1607 for x64-based Systems [2] (3200970) | Internet Explorer 11 | Remote Code Execution | Critical | 3194798 |
Windows Server 2016 for x64-based Systems [2] (3200970) | Internet Explorer 11 | Remote Code Execution | Moderate | 3194798 |
[1]For information about changes in support for Internet Explorer beginning January 12, 2016, see Microsoft Support Lifecycle.
[2]This update is available via Windows Update.
[3]Windows 10 updates are cumulative. The monthly security release includes all security fixes for vulnerabilities that affect Windows 10, in addition to non-security updates. The updates are available via the Microsoft Update Catalog.
[4]Beginning with the October 2016 release, Microsoft is changing the update servicing model for Windows 7, Windows Server 2008 R2, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2. For more information, please see this Microsoft TechNet article.
Note The vulnerabilities discussed in this bulletin affect Windows Server 2016 Technical Preview 5. To be protected from the vulnerabilities, Microsoft recommends that customers running this operating system apply the current update, which is available exclusively from Windows Update.
*The Updates Replaced column shows only the latest update in any chain of superseded updates. For a comprehensive list of updates replaced, go to the Microsoft Update Catalog, search for the update KB number, and then view update details (updates replaced information is provided on the Package Details tab).
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.
Where specified in the Severity Ratings and Impact table, Critical, Important, and Moderate values indicate severity ratings. For more information, see Security Bulletin Severity Rating System. Refer to the following key for the abbreviations used in the table to indicate maximum impact:
Abbreviation | Maximum Impact |
---|---|
RCE | Remote Code Execution |
EoP | Elevation of Privilege |
ID | Information Disclosure |
SFB | Security Feature Bypass |
Vulnerability Severity Ratings and Impact | |||||
---|---|---|---|---|---|
CVE number | Vulnerability title | Internet Explorer 9 | Internet Explorer 10 | Internet Explorer 11 | Internet Explorer 11 on Windows 10 |
CVE-2016-7195 | Microsoft Browser Memory Corruption Vulnerability | Windows Clients: Critical / RCE\ \ Windows Servers: Moderate / RCE | Windows Clients: Critical / RCE\ \ Windows Servers: Moderate / RCE | Windows Clients: Critical / RCE \ \ Windows Servers: Moderate / RCE | Windows Clients: Critical / RCE \ \ Windows Servers: Moderate / RCE |
CVE-2016-7196 | Microsoft Browser Memory Corruption Vulnerability | Not applicable | Windows Clients: Critical / RCE\ \ Windows Servers: Moderate / RCE | Windows Clients: Critical / RCE\ \ Windows Servers: Moderate / RCE | Windows Clients: Critical / RCE\ \ Windows Servers: Moderate / RCE |
CVE-2016-7198 | Microsoft Browser Memory Corruption Vulnerability | Windows Clients: Critical / RCE\ \ Windows Servers: Moderate / RCE | Windows Clients: Critical / RCE \ \ Windows Servers: Moderate / RCE | Windows Clients: Critical / RCE \ \ Windows Servers: Moderate / RCE | Windows Clients: Critical / RCE \ \ Windows Servers: Moderate / RCE |
CVE-2016-7199 | Microsoft Browser Information Disclosure Vulnerability | Windows Clients: Moderate / ID \ \ Windows Servers: Low / ID | Windows Clients: Moderate / ID\ \ Windows Servers: Low / ID | Windows Clients: Moderate / ID \ \ Windows Servers: Low / ID | Windows Clients: Important / ID \ \ Windows Servers: Low / ID |
CVE-2016-7227 | Microsoft Browser Information Disclosure Vulnerability | Windows Clients: Important / ID\ \ Windows Servers: Low / ID | Windows Clients: Important / ID\ \ Windows Servers: Low / ID | Windows Clients: Important / ID \ \ Windows Servers: Low / ID | Windows Clients: Important / ID \ \ Windows Servers: Low / ID |
CVE-2016-7239 | Microsoft Browser Information Disclosure Vulnerability | Windows Clients: Moderate / ID\ \ Windows Servers: Low / ID | Windows Clients: Moderate / ID \ \ Windows Servers: Low / ID | Windows Clients: Moderate / ID \ \ Windows Servers: Low / ID | Windows Clients: Moderate / ID \ \ Windows Servers: Low / ID |
CVE-2016-7241 | Microsoft Browser Memory Corruption Vulnerability | Not applicable | Not applicable | Windows Clients: Critical / RCE \ \ Windows Servers: Moderate / RCE | Windows Clients: Critical / RCE \ \ Windows Servers: Moderate / RCE |
Vulnerability Information
Multiple Microsoft Browser Memory Corruption Vulnerabilities
Multiple remote code execution vulnerabilities exist in the way that Microsoft browsers access objects in memory. The vulnerabilities could corrupt memory in a way that could allow an attacker to execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerabilities could gain the same user rights as the current user. If the current user is logged on with administrative user rights, the attacker could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
An attacker could host a specially crafted website that is designed to exploit the vulnerabilities through Microsoft browsers, and then convince a user to view the website. The attacker could also take advantage of compromised websites, or websites that accept or host user-provided content or advertisements, by adding specially crafted content that could exploit the vulnerabilities. In all cases, however, an attacker would have no way to force users to view the attacker-controlled content. Instead, an attacker would have to convince users to take action, typically via an enticement in email or instant message, or by getting them to open an email attachment.
The update addresses the vulnerabilities by modifying how Microsoft browsers handle objects in memory.
The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:
Vulnerability title | CVE number | Publicly disclosed | Exploited |
---|---|---|---|
Microsoft Browser Memory Corruption Vulnerability | CVE-2016-7195 | No | No |
Microsoft Browser Memory Corruption Vulnerability | CVE-2016-7196 | No | No |
Microsoft Browser Memory Corruption Vulnerability | CVE-2016-7198 | No | No |
Microsoft Browser Memory Corruption Vulnerability | CVE-2016-7241 | No | No |
Mitigating Factors
Microsoft has not identified any mitigating factors for these vulnerabilities.
Workarounds
Microsoft has not identified any workarounds for these vulnerabilities.
FAQ
I am running Internet Explorer on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2. Does this mitigate these vulnerabilities?
Yes. By default, Internet Explorer on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted web content on a server. This is a mitigating factor for websites that you have not added to the Internet Explorer Trusted sites zone.
Can EMET help mitigate attacks that attempt to exploit these vulnerabilities?
Yes. The Enhanced Mitigation Experience Toolkit (EMET) enables users to manage security mitigation technologies that help make it more difficult for attackers to exploit memory corruption vulnerabilities in a given piece of software. EMET can help mitigate attacks that attempt to exploit these vulnerabilities in Internet Explorer on systems where EMET is installed and configured to work with Internet Explorer.
For more information about EMET, see the Enhanced Mitigation Experience Toolkit.
Microsoft Browser Information Disclosure Vulnerability CVE-2016-7199
An information disclosure vulnerability exists when affected Microsoft browsers improperly allow cross-frame interaction. An attacker who successfully exploited this vulnerability could obtain the browser frame or window state from a different domain.
For an attack to be successful, an attacker must persuade a user to open a malicious website from a secure website. This update addresses the vulnerability by denying permission to read state of the object model, to which frames or windows in a different domain shouldn’t have access to.
The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:
Vulnerability title | CVE number | Publicly disclosed | Exploited |
---|---|---|---|
Microsoft Browser Information Disclosure Vulnerability | CVE-2016-7199 | Yes | No |
Mitigating Factors
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds
Microsoft has not identified any workarounds for this vulnerability.
Microsoft Browser Information Disclosure Vulnerability CVE-2016-7227
An information disclosure vulnerability exists when affected Microsoft scripting engines do not properly handle objects in memory. The vulnerability could allow an attacker to detect specific files on the user's computer. In a web-based attack scenario, an attacker could host a website that is used to attempt to exploit the vulnerability.
In addition, compromised websites and websites that accept or host user-generated content could contain specially crafted content that could exploit the vulnerability. In all cases, however, an attacker would have no way to force a user to view the attacker-controlled content. Instead, an attacker would have to convince users to take action. For example, an attacker could trick users into clicking a link that takes them to the attacker's site.
An attacker who successfully exploited the vulnerability could potentially read data that was not intended to be disclosed. Note that the vulnerability would not allow an attacker to execute code or to elevate a user’s rights directly, but the vulnerability could be used to obtain information in an attempt to further compromise the affected system. The update addresses the vulnerability by helping to restrict what information is returned to Internet Explorer.The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:
Vulnerability title | CVE number | Publicly disclosed | Exploited |
---|---|---|---|
Microsoft Browser Information Disclosure Vulnerability | CVE-2016-7227 | No | No |
Mitigating Factors
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds
Microsoft has not identified any workarounds for this vulnerability.
Microsoft Browser Information Disclosure Vulnerability CVE-2016-7239
An information disclosure vulnerability exists when the Microsoft browser XSS filter is abused to leak sensitive page information. An attacker who successfully exploited the vulnerability could obtain sensitive information from certain web pages.
To exploit the vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The update addresses the vulnerability by changing how the XSS filter handles RegEx.
The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:
Vulnerability title | CVE number | Publicly disclosed | Exploited |
---|---|---|---|
Microsoft Browser Information Disclosure Vulnerability | CVE-2016-7239 | No | No |
Mitigating Factors
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds
Microsoft has not identified any workarounds for this vulnerability.
Security Update Deployment
For Security Update Deployment information see the Microsoft Knowledge Base article referenced in the Executive Summary.
Acknowledgments
Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgments for more information.
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
- V1.0 November 8, 2016: Bulletin published.
- V2.0 (December 13, 2016): Revised bulletin to announce the following updates have been rereleased with a detection change that addresses a supersedence issue that certain customers experienced when attempting to install the November Security Only updates.
- Security Only update 3197867 for all supported releases of Windows 7 and Windows Server 2008 R2. For more information, see Microsoft Knowledge Base Article 3197867.
- Monthly Rollup 3197868 for all supported releases of Windows 7 and Windows Server 2008 R2. For more information, see Microsoft Knowledge Base Article 3197868.
- Security Only update 3197876 for Windows Server 2012. For more information, see Microsoft Knowledge Base Article 3197876.
- Monthly Rollup 3197877 for Windows Server 2012. For more information, see Microsoft Knowledge Base Article 3197877.
- Security Only update 3197873 for Windows 8.1 and Windows Server 2012 R2. For more information, see Microsoft Knowledge Base Article 3197873.
- Monthly Rollup 3197874 for Windows 8.1 and Windows Server 2012 R2. For more information, see Microsoft Knowledge Base Article 3197874.
- These are detection changes only. There were no changes to the update files. Customers who have already successfully installed any of these updates do not need to take any action. For more information, see the Microsoft Knowledge Base article for the respective update.
Page generated 2016-12-12 11:26-08:00.