Microsoft Security Bulletin MS16-104 - Critical
Cumulative Security Update for Internet Explorer (3183038)
Published: September 13, 2016
Version: 1.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 handles:
- zone and integrity settings.
- cross-origin content.
- objects in memory.
- .URL files.
For more information about the vulnerabilities, see the Vulnerability Information section.
For more information about this update, see Microsoft Knowledge Base Article 3183038.
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 (3185319) | Remote Code Execution | Critical | 3175443 in MS16-095 |
Windows Vista x64 Edition Service Pack 2 | Internet Explorer 9 (3185319) | Remote Code Execution | Critical | 3175443 in MS16-095 |
Windows Server 2008 for 32-bit Systems Service Pack 2 | Internet Explorer 9 (3185319) | Remote Code Execution | Moderate | 3175443 in MS16-095 |
Windows Server 2008 for x64-based Systems Service Pack 2 | Internet Explorer 9 (3185319) | Remote Code Execution | Moderate | 3175443 in MS16-095 |
Internet Explorer 10 | ||||
Windows Server 2012 | Internet Explorer 10[1] (3185319) | Remote Code Execution | Moderate | 3175443 in MS16-095 |
Internet Explorer 11 | ||||
Windows 7 for 32-bit Systems Service Pack 1 | Internet Explorer 11 (3185319) | Remote Code Execution | Critical | 3175443 in MS16-095 |
Windows 7 for x64-based Systems Service Pack 1 | Internet Explorer 11 (3185319) | Remote Code Execution | Critical | 3175443 in MS16-095 |
Windows Server 2008 R2 for x64-based Systems Service Pack 1 | Internet Explorer 11[1] (3185319) | Remote Code Execution | Moderate | 3175443 in MS16-095 |
Windows 8.1 for 32-bit Systems | Internet Explorer 11 (3185319) | Remote Code Execution | Critical | 3175443 in MS16-095 |
Windows 8.1 for x64-based Systems | Internet Explorer 11 (3185319) | Remote Code Execution | Critical | 3175443 in MS16-095 |
Windows Server 2012 R2 | Internet Explorer 11 (3185319) | Remote Code Execution | Moderate | 3175443 in MS16-095 |
Windows RT 8.1 | Internet Explorer 11[1][2](3185319) | Remote Code Execution | Critical | 3175443 in MS16-095 |
Windows 10 for 32-bit Systems[3](3185611) | Internet Explorer 11 | Remote Code Execution | Critical | 3176492 |
Windows 10 for x64-based Systems[3](3185611) | Internet Explorer 11 | Remote Code Execution | Critical | 3176492 |
Windows 10 Version 1511 for 32-bit Systems[3](3185614) | Internet Explorer 11 | Remote Code Execution | Critical | 3176493 |
Windows 10 Version 1511 for x64-based Systems[3](3185614) | Internet Explorer 11 | Remote Code Execution | Critical | 3176493 |
Windows 10 Version 1607 for 32-bit Systems[3](3189866) | Internet Explorer 11 | Remote Code Execution | Critical | 3176495 |
Windows 10 Version 1607 for x64-based Systems[3](3189866) | Internet Explorer 11 | Remote Code Execution | Critical | 3176495 |
[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.
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).
Update FAQ
In addition to installing this update are there any further steps I need to carry out to be protected from any of the vulnerabilities discussed in this bulletin?
Yes. Although protecting Windows 10 systems from CVE-2016-3375 requires no additional steps other than installing the September Windows 10 cumulative update, for all other affected operating systems installing the 3185319 cumulative update by itself does not fully protect against CVE-2016-3375 — you must also install security update 3184122 in MS16-116 to be fully protected from the vulnerability.
Does this update contain any additional security-related changes to functionality?
Yes. In addition to the changes that are listed for the vulnerabilities described in this bulletin, this update includes defense-in-depth updates to help improve security-related features.
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 September 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-3247 | Microsoft Browser Memory Corruption Vulnerability | Not applicable | Not applicable | Windows Clients: Important / RCE Windows Servers Low / RCE | Windows Clients: Important / RCE Windows Servers Low / RCE |
CVE-2016-3291 | Microsoft Browser Information Disclosure Vulnerability | Not applicable | Not applicable | Windows Clients: Moderate / ID Windows Servers Low / ID | Windows Clients: Moderate / ID Windows Servers Low / ID |
CVE-2016-3292 | Microsoft Browser Elevation of Privilege Vulnerability | Not applicable | Windows Clients: Important / EoP Windows Servers Low / EoP | Windows Clients: Important / EoP Windows Servers Low / EoP | Windows Clients: Important / EoP Windows Servers Low / EoP |
CVE-2016-3295 | 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-3297 | Microsoft Browser Memory Corruption Vulnerability | Windows Clients: Important / RCE Windows Servers Low / RCE | Windows Clients: Important / RCE Windows Servers Low / RCE | Windows Clients: Important / RCE Windows Servers Low / RCE | Windows Clients: Important / RCE Windows Servers Low / RCE |
CVE-2016-3324 | Internet Explorer Memory Corruption Vulnerability | Windows Clients: Important / RCE Windows Servers Low / RCE | Windows Clients: Important / RCE Windows Servers Low / RCE | Windows Clients: Important / RCE Windows Servers Low / RCE | Windows Clients: Important / RCE Windows Servers Low / RCE |
CVE-2016-3325 | Microsoft Browser Information Disclosure Vulnerability | Not applicable | Not applicable | Not applicable | Windows Clients: Important / ID Windows Servers Low / ID |
CVE-2016-3351 | 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-3353 | Internet Explorer Security Feature Bypass | Windows Clients: Important / SFB Windows Servers Low / SFB | Windows Clients: Important / SFB Windows Servers Low / SFB | Windows Clients: Important / SFB Windows Servers Low / SFB | Windows Clients: Important / SFB Windows Servers Low / SFB |
CVE-2016-3375 | Scripting Engine 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 |
Vulnerability Information
Multiple Microsoft Internet Explorer Memory Corruption Vulnerabilities
Multiple remote code execution vulnerabilities exist in the way that Internet Explorer accesses 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 Internet Explorer, 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 Internet Explorer handles 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-3247 | No | No |
Microsoft Browser Memory Corruption Vulnerability | CVE-2016-3295 | No | No |
Microsoft Browser Memory Corruption Vulnerability | CVE-2016-3297 | No | No |
Internet Explorer Memory Corruption Vulnerability | CVE-2016-3324 | 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.
Scripting Engine Memory Corruption Vulnerability CVE-2016-3375
A remote code execution vulnerability exists in the way that the Microsoft OLE Automation mechanism and the VBScript Scripting Engine in Internet Explorer access objects in memory. The vulnerability 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 vulnerability 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 vulnerability through Internet Explorer, 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 vulnerability. 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.
Note that you must install two updates to be protected from the Scripting Engine Memory Corruption Vulnerability CVE-2016-3375: The update in this bulletin, MS16-104, and the update in MS16-116. The updates address the vulnerability by modifying how the Microsoft OLE Automation mechanism and the VBScript Scripting Engine in Internet Explorer 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 |
---|---|---|---|
Scripting Engine Memory Corruption Vulnerability | CVE-2016-3375 | No | No |
Mitigating Factors
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds
Microsoft has not identified any workarounds for this vulnerability.
FAQ
In addition to installing this update are there any further steps I need to carry out to be protected from CVE-2016-3375?
Yes. Although protecting Windows 10 systems from CVE-2016-3375 requires no additional steps other than installing the September Windows 10 cumulative update, for all other affected operating systems installing the 3185319 cumulative update by itself does not fully protect against CVE-2016-3375 — you must also install security update 3184122 in MS16-116 to be fully protected from the vulnerability.
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.
Internet Explorer Elevation of Privilege Vulnerability CVE-2016-3292
An elevation of privilege vulnerability exists when Internet Explorer fails a check, allowing sandbox escape. An attacker who successfully exploited the vulnerability could use the sandbox escape to elevate privileges on an affected system. This vulnerability by itself does not allow arbitrary code execution; however, it could allow arbitrary code to be run if the attacker uses it in combination with one or more vulnerabilities (such as a remote code execution vulnerability or another elevation of privilege vulnerability) that is capable of leveraging the elevated privileges when code execution is attempted.
The update addresses the vulnerability by correcting how Internet Explorer handles zone and integrity settings.
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 Elevation of Privilege Vulnerability | CVE-2016-3292 | 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-3325
An information disclosure vulnerability exists in the way that the affected components handle objects in memory. An attacker who successfully exploited the vulnerability could obtain information to further compromise a target system.
In a web-based attack scenario an attacker could host a website that is used to attempt to exploit the vulnerabilities. Additionally, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could be used to exploit the vulnerabilities. However, in all cases an attacker would have no way to force users to view 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.
The update addresses the vulnerability by correcting how the affected components 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 Information Disclosure Vulnerability | CVE-2016-3325 | No | No |
Mitigating Factors
Microsoft has not identified any mitigating factors for these vulnerabilities.
Workarounds
Microsoft has not identified any workarounds for these vulnerabilities.
Microsoft Browser Information Disclosure Vulnerability CVE-2016-3351
An information disclosure vulnerability exists in the way that certain functions 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 vulnerabilities. Additionally, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could be used to exploit the vulnerabilities. However, in all cases an attacker would have no way to force users to view 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.
The security update addresses the vulnerability by correcting how certain functions 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 Information Disclosure Vulnerability | CVE-2016-3351 | No | Yes |
Mitigating Factors
Microsoft has not identified any mitigating factors for these vulnerabilities.
Workarounds
Microsoft has not identified any workarounds for these vulnerabilities.
Microsoft Browser Information Disclosure Vulnerability CVE-2016-3291
An information disclosure vulnerability exists in the way that affected Microsoft browsers handle cross-origin requests. An attacker who successfully exploited this vulnerability could determine the origin of all of the web pages in the affected browser.
In a web-based attack scenario, an attacker could host a website that is used to attempt to exploit the vulnerability. Additionally, compromised websites and websites that accept or host user-provided content could contain specially crafted content that could be used to exploit the vulnerabilities. However, in all cases an attacker would have no way to force users to view 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.
The security update addresses the vulnerabilities by correcting how affected browsers handle cross-origin resources.
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-3291 | No | No |
Mitigating Factors
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds
Microsoft has not identified any workarounds for this vulnerability.
Internet Explorer Security Feature Bypass - CVE-2016-3353
A security feature bypass opportunity exists in the way that Internet Explorer handles files from the Internet zone.
In a web-based attack scenario an attacker could host a malicious website that is designed to exploit the security feature bypass. Alternatively, in an email or instant message attack scenario, the attacker could send the targeted user a specially crafted .URL file that is designed to exploit the bypass. Additionally, compromised websites or websites that accept or host user-provided content could contain specially crafted content that could be used to exploit the security feature bypass. In all cases, however, an attacker would have no way to force users to view attacker-controlled content. Instead, an attacker would have to convince users to take action. For example, an attacker could entice users into clicking a link that directs them to the attacker's site or send a malicious attachment.
The update addresses the security feature by correcting how Internet Explorer handles .URL files
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 |
---|---|---|---|
Internet Explorer Security Feature Bypass | CVE-2016-3353 | 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 September 13, 2016: Bulletin published.
Page generated 2016-09-14 17:34-07:00.