15.2 C
London
Monday, August 21, 2017

MS16-152 – Important: Security Update for Windows Kernel (3199709) – Version:...

Security Update for Windows Kernel (3199709)Published: December 13, 2016Version: 1.0This security update resolves a vulnerability in Microsoft Windows.

The vulnerability could allow information disclosure when the Windows kernel improperly handles objects in memory.This security update is rated Important for all supported versions of Windows 10 and Window Server 2016.

For more information, see the Affected Software and Vulnerability Severity Ratings section.The security update addresses the vulnerability by correcting how the Windows kernel handles objects in memory.

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

For more information about this update, see Microsoft Knowledge Base Article 3199709.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 past version or edition, see Microsoft Support Lifecycle.The severity ratings indicated for each affected software 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 December bulletin summary.Note Please see the Security Update Guide for a new approach to consuming the security update information. You can customize your views and create affected software spreadsheets, as well as download data via a restful API.

For more information, please see the Security Updates Guide FAQ.

As a reminder, the Security Updates Guide will be replacing security bulletins as of February 2017. Please see our blog post, Furthering our commitment to security updates, for more details.[1] Windows 10 and Windows Server 2016 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. Please note that effective December 13, 2016, Windows 10 and Windows Server 2016 details for the Cumulative Updates will be documented in Release Notes. Please refer to the Release Notes for OS Build numbers, Known Issues, and affected file list information.*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).Note A vulnerability discussed in this bulletin affects Windows Server 2016 Technical Preview 5.

To be protected from the vulnerability, Microsoft recommends that customers running this operating system apply the current update, which is available from Windows Update. Windows Kernel Memory Information Disclosure Vulnerability - CVE-2016-7258An information disclosure vulnerability exists in Microsoft Windows when the Windows kernel fails to properly handle certain page fault system calls.

An authenticated attacker who successfully exploited the vulnerability could disclose information from one process to another.To exploit the vulnerability, an attacker would have to either log on locally to an affected system, or convince a locally authenticated user to execute a specially crafted application.The security update addresses the vulnerability by correcting how the Windows kernel handles certain page fault system calls.The following table contain a link to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list: Vulnerability title CVE number Publicly disclosed Exploited Windows Kernel Memory Information Disclosure Vulnerability CVE-2016-7258 No No Mitigating FactorsMicrosoft has not identified any mitigating factors for this vulnerability.WorkaroundsMicrosoft has not identified any workarounds for this vulnerability.For Security Update Deployment information, see the Microsoft Knowledge Base article referenced here in the Executive Summary.Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See Acknowledgments for more information.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.V1.0 (December 13, 2016): Bulletin published. Page generated 2016-12-07 12:30-08:00.

MS16-154 – Critical: Security Update for Adobe Flash Player (3209498) –...

Security Update for Adobe Flash Player (3209498)Published: December 13, 2016Version: 1.0This security update resolves vulnerabilities in Adobe Flash Player when installed on all supported editions of Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows RT 8.1, Windows 10, and Windows Server 2016.This security update is rated Critical.

The update addresses the vulnerabilities in Adobe Flash Player by updating the affected Adobe Flash libraries contained within Internet Explorer 10, Internet Explorer 11, and Microsoft Edge.

For more information, see the Affected Software section.For more information about this update, see Microsoft Knowledge Base Article 3209498.This security update addresses the following vulnerabilities, which are described in Adobe Security Bulletin APSB16-39:CVE-2016-7867, CVE-2016-7868, CVE-2016-7869, CVE-2016-7870, CVE-2016-7871, CVE-2016-7872, CVE-2016-7873, CVE-2016-7874, CVE-2016-7875, CVE-2016-7876, CVE-2016-7877, CVE-2016-7878, CVE-2016-7879, CVE-2016-7880, CVE-2016-7881, CVE-2016-7890, CVE-2016-7892The 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 Aggregate Severity and Impact Updates Replaced*            Windows 8.1 Windows 8.1 for 32-bit Systems Adobe Flash Player(3209498) CriticalRemote Code Execution 3202790 in MS16-141 Windows 8.1 for x64-based Systems Adobe Flash Player(3209498) CriticalRemote Code Execution 3202790 in MS16-141 Windows Server 2012 and Windows Server 2012 R2 Windows Server 2012 Adobe Flash Player(3209498) ModerateRemote Code Execution 3202790 in MS16-141 Windows Server 2012 R2 Adobe Flash Player(3209498) ModerateRemote Code Execution 3202790 in MS16-141 Windows RT 8.1 Windows RT 8.1 Adobe Flash Player(3209498)[1] CriticalRemote Code Execution 3202790 in MS16-141 Windows 10 Windows 10 for 32-bit Systems Adobe Flash Player(3209498)[2] CriticalRemote Code Execution 3202790 in MS16-141 Windows 10 for x64-based Systems Adobe Flash Player(3209498)[2] CriticalRemote Code Execution 3202790 in MS16-141 Windows 10 Version 1511 for 32-bit Systems Adobe Flash Player(3209498)[2] CriticalRemote Code Execution 3202790 in MS16-141 Windows 10 Version 1511 for x64-based Systems Adobe Flash Player(3209498)[2] CriticalRemote Code Execution 3202790 in MS16-141 Windows 10 Version 1607 for 32-bit Systems Adobe Flash Player(3209498)[2] CriticalRemote Code Execution 3202790 in MS16-141 Windows 10 Version 1607 for x64-based Systems Adobe Flash Player(3209498)[2] CriticalRemote Code Execution 3202790 in MS16-141 Windows Server 2016 Windows Server 2016 for 64-bit Systems Adobe Flash Player(3209498)[2] CriticalRemote Code Execution 3202790 in MS16-141 [1]This update is available via Windows Update.[2]The Adobe Flash Player updates for Windows 10 updates are available via Windows Update or 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).How could an attacker exploit these vulnerabilities? In a web-based attack scenario where the user is using Internet Explorer for the desktop, an attacker could host a specially crafted website that is designed to exploit any of these vulnerabilities through Internet Explorer and then convince a user to view the website.

An attacker could also embed an ActiveX control marked "safe for initialization" in an application or Microsoft Office document that hosts the IE rendering engine.

The attacker could also take advantage of compromised websites and websites that accept or host user-provided content or advertisements.

These websites could contain specially crafted content that could exploit any of these 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 by clicking a link in an email message or in an Instant Messenger message that takes users to the attacker's website, or by opening an attachment sent through email.In a web-based attack scenario where the user is using Internet Explorer in the Windows 8-style UI, an attacker would first need to compromise a website already listed in the Compatibility View (CV) list.

An attacker could then host a website that contains specially crafted Flash content designed to exploit any of these vulnerabilities through Internet Explorer and then convince a user to view the website.

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 by clicking a link in an email message or in an Instant Messenger message that takes users to the attacker's website, or by opening an attachment sent through email.

For more information about Internet Explorer and the CV List, please see the MSDN Article, Developer Guidance for websites with content for Adobe Flash Player in Windows 8.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:In a web-based attack scenario where the user is using Internet Explorer for the desktop, an attacker could host a website that contains a webpage that is used to exploit any of 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 any of 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 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. Internet Explorer in the Windows 8-style UI will only play Flash content from sites listed on the Compatibility View (CV) list.

This restriction requires an attacker to first compromise a website already listed on the CV list.

An attacker could then host specially crafted Flash content designed to exploit any of these vulnerabilities through Internet Explorer and then convince a user to view the website.

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 by clicking a link in an email message or in an Instant Messenger message that takes users to the attacker's website, or by opening an attachment sent through email. By default, all supported versions of Microsoft Outlook and Windows Live Mail open HTML email messages in the Restricted sites zone.

The Restricted sites zone, which disables scripts and ActiveX controls, helps reduce the risk of an attacker being able to use any of these vulnerabilities to execute malicious code.
If a user clicks a link in an email message, the user could still be vulnerable to exploitation of any of these vulnerabilities through the web-based attack scenario. By default, Internet Explorer on Windows Server 2012 and Windows Server 2012 R2 runs in a restricted mode that is known as Enhanced Security Configuration.

This mode can help reduce the likelihood of the exploitation of these Adobe Flash Player vulnerabilities in Internet Explorer. Workaround refers to a setting or configuration change that would help block known attack vectors before you apply the update.Prevent Adobe Flash Player from running You can disable attempts to instantiate Adobe Flash Player in Internet Explorer and other applications that honor the kill bit feature, such as Office 2007 and Office 2010, by setting the kill bit for the control in the registry. Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To set the kill bit for the control in the registry, perform the following steps: Paste the following into a text file and save it with the .reg file extension. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{D27CDB6E-AE6D-11CF-96B8-444553540000}] "Compatibility Flags"=dword:00000400 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\ActiveX Compatibility\{D27CDB6E-AE6D-11CF-96B8-444553540000}] "Compatibility Flags"=dword:00000400 Double-click the .reg file to apply it to an individual system.You can also apply this workaround across domains by using Group Policy.

For more information about Group Policy, see the TechNet article, Group Policy collection. Note You must restart Internet Explorer for your changes to take effect. Impact of workaround.

There is no impact as long as the object is not intended to be used in Internet Explorer. How to undo the workaround. Delete the registry keys that were added in implementing this workaround.  Prevent Adobe Flash Player from running in Internet Explorer through Group Policy Note The Group Policy MMC snap-in can be used to set policy for a machine, for an organizational unit, or for an entire domain.

For more information about Group Policy, visit the following Microsoft Web sites: Group Policy Overview What is Group Policy Object Editor? Core Group Policy tools and settings To disable Adobe Flash Player in Internet Explorer through Group Policy, perform the following steps: Note This workaround does not prevent Flash from being invoked from other applications, such as Microsoft Office 2007 or Microsoft Office 2010. Open the Group Policy Management Console and configure the console to work with the appropriate Group Policy object, such as local machine, OU, or domain GPO. Navigate to the following node:Administrative Templates -> Windows Components -> Internet Explorer -> Security Features -> Add-on Management Double-click Turn off Adobe Flash in Internet Explorer and prevent applications from using Internet Explorer technology to instantiate Flash objects. Change the setting to Enabled. Click Apply and then click OK to return to the Group Policy Management Console. Refresh Group Policy on all systems or wait for the next scheduled Group Policy refresh interval for the settings to take effect.  Prevent Adobe Flash Player from running in Office 2010 on affected systems Note This workaround does not prevent Adobe Flash Player from running in Internet Explorer. Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. For detailed steps that you can use to prevent a control from running in Internet Explorer, see Microsoft Knowledge Base Article 240797.

Follow the steps in the article to create a Compatibility Flags value in the registry to prevent a COM object from being instantiated in Internet Explorer. To disable Adobe Flash Player in Office 2010 only, set the kill bit for the ActiveX control for Adobe Flash Player in the registry using the following steps: Create a text file named Disable_Flash.reg with the following contents: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Common\COM\Compatibility\{D27CDB6E-AE6D-11CF-96B8-444553540000}] "Compatibility Flags"=dword:00000400 Double-click the .reg file to apply it to an individual system. Note You must restart Internet Explorer for your changes to take effect. You can also apply this workaround across domains by using Group Policy.

For more information about Group Policy, see the TechNet article, Group Policy collection. Prevent ActiveX controls from running in Office 2007 and Office 2010 To disable all ActiveX controls in Microsoft Office 2007 and Microsoft Office 2010, including Adobe Flash Player in Internet Explorer, perform the following steps: Click File, click Options, click Trust Center, and then click Trust Center Settings. Click ActiveX Settings in the left-hand pane, and then select Disable all controls without notifications. Click OK to save your settings. Impact of workaround. Office documents that use embedded ActiveX controls may not display as intended. How to undo the workaround. To re-enable ActiveX controls in Microsoft Office 2007 and Microsoft Office 2010, perform the following steps: Click File, click Options, click Trust Center, and then click Trust Center Settings. Click ActiveX Settings in the left-hand pane, and then deselect Disable all controls without notifications. Click OK to save your settings. Set Internet and Local intranet security zone settings to "High" to block ActiveX Controls and Active Scripting in these zones You can help protect against exploitation of these vulnerabilities by changing your settings for the Internet security zone to block ActiveX controls and Active Scripting. You can do this by setting your browser security to High. To raise the browsing security level in Internet Explorer, perform the following steps: On the Internet Explorer Tools menu, click Internet Options. In the Internet Options dialog box, click the Security tab, and then click Internet. Under Security level for this zone, move the slider to High.

This sets the security level for all websites you visit to High. Click Local intranet. Under Security level for this zone, move the slider to High.

This sets the security level for all websites you visit to High. Click OK to accept the changes and return to Internet Explorer. Note If no slider is visible, click Default Level, and then move the slider to High. Note Setting the level to High may cause some websites to work incorrectly.
If you have difficulty using a website after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites.

This will allow the site to work correctly even with the security setting set to High. Impact of workaround. There are side effects to blocking ActiveX Controls and Active Scripting. Many websites on the Internet or an intranet use ActiveX or Active Scripting to provide additional functionality.

For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements.

Blocking ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites.
If you do not want to block ActiveX Controls or Active Scripting for such sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".   Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone You can help protect against exploitation of these vulnerabilities by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone.

To do this, perform the following steps: In Internet Explorer, click Internet Options on the Tools menu. Click the Security tab. Click Internet, and then click Custom Level. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK. Click Local intranet, and then click Custom Level. Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK. Click OK to return to Internet Explorer, and then click OK again. Note Disabling Active Scripting in the Internet and Local intranet security zones may cause some websites to work incorrectly.
If you have difficulty using a website after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites.

This will allow the site to work correctly. Impact of workaround. There are side effects to prompting before running Active Scripting. Many websites that are on the Internet or on an intranet use Active Scripting to provide additional functionality.

For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround.

For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting.
If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".   Add sites that you trust to the Internet Explorer Trusted sites zone After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone.

This will allow you to continue to use trusted websites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone. To do this, perform the following steps: In Internet Explorer, click Tools, click Internet Options, and then click the Security tab. In the Select a web content zone to specify its current security settings box, click Trusted Sites, and then click Sites. If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box. In the Add this website to the zone box, type the URL of a site that you trust, and then click Add. Repeat these steps for each site that you want to add to the zone. Click OK two times to accept the changes and return to Internet Explorer. Note Add any sites that you trust not to take malicious action on your system.

Two sites in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com.

These are the sites that will host the update, and they require an ActiveX control to install the update. For Security Update Deployment information, see the Microsoft Knowledge Base article referenced here in the Executive Summary.Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See Acknowledgments for more information.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.V1.0 (December 13, 2016): Bulletin published. Page generated 2016-12-13 9:58Z-08:00.

MS16-145 – Critical: Cumulative Security Update for Microsoft Edge (3204062) –...

Multiple Microsoft Browser Memory Corruption Vulnerabilities Multiple remote code execution vulnerabilities exist when affected Microsoft browsers improperly access objects in memory.

The vulnerabilities could corrupt memory in such a way that an atta...

MS16-148 – Critical: Security Update for Microsoft Office (3204068) – Version:...

Multiple Microsoft Office Memory Corruption Vulnerabilities Multiple remote code execution vulnerabilities exist in Microsoft Office software when the Office software fails to properly handle objects in memory.

An attacker who successfully exploited the 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 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. Exploitation of the 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 the specially crafted file to the user and convincing the user to open the file.
In a web-based attack scenario an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file that is designed to exploit the vulnerabilities.

An attacker would have no way to force users to visit the website.
Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an email or Instant Messenger message, and then convince them to open the specially crafted file. Note that where the severity is indicated as Critical in the Affected Software and Vulnerability Severity Ratings table, the Preview Pane is an attack vector for CVE-2016-7298. The security update addresses the vulnerabilities by correcting how Office 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 Office Memory Corruption Vulnerability CVE-2016-7263 No No Microsoft Office Memory Corruption Vulnerability CVE-2016-7277 No No Microsoft Office Memory Corruption Vulnerability CVE-2016-7289 No No Mitigating Factors Microsoft has not identified any mitigating factors for these vulnerabilities. Workarounds Microsoft has not identified any workarounds for these vulnerabilities. Uniscribe Remote Code Execution Vulnerability CVE-2016-7274 A remote code execution vulnerability exists in Windows due to the way Windows Uniscribe handles objects in the memory.

An attacker who successfully exploited this vulnerability could take 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. There are multiple ways an attacker could exploit this vulnerability. In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit this vulnerability and then convince a user to view the website.

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 by getting them to click a link in an email message or in an Instant Messenger message that takes users to the attacker's website, or by opening an attachment sent through email. In a file sharing attack scenario, an attacker could provide a specially crafted document file that is designed to exploit this vulnerability, and then convince a user to open the document file. The security update addresses these vulnerabilities by correcting how the Windows Uniscribe handles objects in the 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 Uniscribe Remote Code Execution Vulnerability CVE-2016-7274 No No Mitigating Factors Microsoft has not identified any mitigating factor for this vulnerability. Workarounds Microsoft has not identified any workarounds for this vulnerability. Microsoft Office OLE DLL Side Loading Vulnerability – CVE-2016-7275 A remote code execution vulnerability exists when Microsoft Office improperly validates input before loading libraries.

An attacker who successfully exploited the vulnerability 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. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. To exploit the vulnerability, an attacker would need access to the local system and the ability to execute a specially crafted application on the system. The security update addresses the vulnerability by correcting how Microsoft Office validates input before loading libraries. 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 Office OLE DLL Side Loading Vulnerability CVE-2016-7275 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 Office Security Feature Bypass Vulnerability – CVE-2016-7267 A security feature bypass vulnerability exists in Microsoft Office software when the Office software improperly handles the parsing of file formats.

The security feature bypass by itself does not allow arbitrary code execution. However, to successfully exploit the vulnerability, an attacker would have to use it in conjunction with another vulnerability, such as a remote code execution vulnerability, to take advantage of the security feature bypass vulnerability and run arbitrary code. To exploit the vulnerability would require that an attacker convince a user to open a specially crafted file with an affected version of Microsoft Office software. The security update addresses the vulnerability by correcting how Office software handles the parsing of file formats. 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 Office Security Feature Bypass Vulnerability CVE-2016-7267 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 Office Security Feature Bypass Vulnerability – CVE-2016-7262 A security feature bypass vulnerability exists when Microsoft Office improperly handles input.

An attacker who successfully exploited the vulnerability could execute arbitrary commands. In a file sharing attack scenario, an attacker could provide a specially crafted document file that is designed to exploit the vulnerability, and then convince users to open the document file and interact with the document by clicking on a specific cell. The update addresses the vulnerability by correcting how Microsoft Office handles input. 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 Office Security Feature Bypass Vulnerability CVE-2016-7262 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 Office Security Feature Bypass Vulnerability – CVE-2016-7266 A security feature bypass vulnerability exists when Microsoft Office improperly checks registry settings when an attempt is made to run embedded content.

An attacker who successfully exploited the vulnerability could execute arbitrary commands.
In a file sharing attack scenario, an attacker could provide a specially crafted document file that is designed to exploit the vulnerability, and then convince users to attempt to open the document multiple times. The update addresses the vulnerability by correcting how Microsoft Office checks registry settings when a user attempts to open or execute embedded content. 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 Office Security Feature Bypass Vulnerability CVE-2016-7266 No No Mitigating Factors Microsoft has not identified any mitigating factors for this vulnerability. Workarounds Microsoft has not identified any workarounds for this vulnerability. GDI Information Disclosure Vulnerability – CVE-2016-7257 An information disclosure vulnerability exists when Microsoft Office fails to properly handle objects in memory, allowing an attacker to retrieve information that could lead to an Address Space Layout Randomization (ASLR) bypass.

An attacker who successfully exploited this vulnerability could cause an information disclosure to bypass the ASLR security feature that protects users from a broad class of vulnerabilities. The security feature bypass itself does not allow arbitrary code execution. However, an attacker could use the ASLR bypass vulnerability in conjunction with another vulnerability, such as a remote code execution vulnerability, that could take advantage of the ASLR bypass to run arbitrary code. To exploit this vulnerability, an attacker could convince a use to run a specially crafted application.

The security update addresses the vulnerability by correcting how Microsoft Office handles addresses 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 GDI Information Disclosure Vulnerability CVE-2016-7257 No No Mitigating Factors Microsoft has not identified any mitigating factors for this vulnerability. Workarounds Microsoft has not identified any workarounds for this vulnerability. Multiple Microsoft Office Information Disclosure Vulnerabilities Multiple information disclosure vulnerabilities exist when affected Microsoft Office software reads out of bound memory, which could disclose the contents of memory.

An attacker who successfully exploited the vulnerabilities could view out of bound memory. Exploitation of the vulnerabilities requires that a user open a specially crafted file with an affected version of Microsoft Office software. The security update addresses the vulnerabilities by properly initializing affected variables. 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 Office Information Disclosure Vulnerability CVE-2016-7264 No No Microsoft Office Information Disclosure Vulnerability CVE-2016-7265 No No Microsoft Office Information Disclosure Vulnerability CVE-2016-7268 No No Microsoft Office Information Disclosure Vulnerability CVE-2016-7276 No No Microsoft Office Information Disclosure Vulnerability CVE-2016-7290 No No Microsoft Office Information Disclosure Vulnerability CVE-2016-7291 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 (MAU) Office Elevation of Privilege Vulnerability – CVE-2016-7300 An elevation of privilege vulnerability exists when the Microsoft AutoUpdate (MAU) application for Mac improperly validates updates before executing them.

An attacker who successfully exploited the vulnerability who already has the ability to execute code on a system could elevate privileges.

To exploit the vulnerability, the attacker could place a crafted executable in a specific location used by the update application to execute arbitrary code in a privileged context. This update addresses the vulnerability by ensuring that the Microsoft AutoUpdate (MAU) for Mac properly validates packages prior to installing them. 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 (MAU) Office Elevation of Privilege Vulnerability CVE-2016-7300 No No Mitigating Factors Microsoft has not identified any mitigating factors for this vulnerability. Workarounds Microsoft has not identified any workarounds for this vulnerability.

MS16-146 – Critical: Security Update for Microsoft Graphics Component (3204066) –...

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 severity ratings indicated for each affected software 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 December bulletin summary.Note Please see the Security Update Guide for a new approach to consuming the security update information. You can customize your views and create affected software spreadsheets, as well as download data via a restful API.

For more information, please see the Security Updates Guide FAQ.

As a reminder, the Security Updates Guide will be replacing security bulletins as of February 2017. Please see our blog post, Furthering our commitment to security updates, for more details.[2] Windows 10 and Windows Server 2016 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. Please note that effective December 13, 2016, Windows 10 and Windows Server 2016 for the Cumulative Updates details will be documented in Release Notes. Please refer to the Release Notes for OS Build numbers, Known Issues, and affected file list information.[3] 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.

Although an update is available for Windows Server 2016 Technical Preview 5 via Windows Update, Microsoft recommends that customers upgrade to Window Server 2016 at your earliest convenience.*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).

MS16-DEC – Microsoft Security Bulletin Summary for December 2016 – Version:...

The following tables list the bulletins in order of major software category and severity.Use these tables to learn about the security updates that you may need to install. You should review each software program or component listed to see whether any security updates pertain to your installation.
If a software program or component is listed, then the severity rating of the software update is also listed.Note You may have to install several security updates for a single vulnerability. Review the whole column for each bulletin identifier that is listed to verify the updates that you have to install, based on the programs or components that you have installed on your system. Windows Vista Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating Critical None Critical Critical Important Windows Vista Service Pack 2 Internet Explorer 9 (3203621)(Critical)Microsoft Windows Hyperlink Object Library(3208481)(Critical) Not applicable Windows Vista Service Pack 2(3204724)(Important)Windows Vista Service Pack 2(3205638)(Critical) Windows Vista Service Pack 2(3196348)(Critical) Windows Vista Service Pack 2(3204808)(Important)Windows Vista Service Pack 2(3196726)(Important) Windows Vista x64 Edition Service Pack 2 Internet Explorer 9 (3203621)(Critical)Microsoft Windows Hyperlink Object Library(3208481)(Critical) Not applicable Windows Vista x64 Edition Service Pack 2(3204724)(Important)Windows Vista x64 Edition Service Pack 2(3205638)(Critical) Windows Vista x64 Edition Service Pack 2(3196348)(Critical) Windows Vista x64 Edition Service Pack 2(3204808)(Important)Windows Vista x64 Edition Service Pack 2(3196726)(Important) Windows Server 2008 Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating Moderate None Critical Critical Important Windows Server 2008 for 32-bit Systems Service Pack 2 Internet Explorer 9 (3203621)(Moderate)Microsoft Windows Hyperlink Object Library(3208481)(Moderate) Not applicable Windows Server 2008 for 32-bit Systems Service Pack 2(3204724)(Important)Windows Server 2008 for 32-bit Systems Service Pack 2(3205638)(Critical) Windows Server 2008 for 32-bit Systems Service Pack 2(3196348)(Critical) Windows Server 2008 for 32-bit Systems Service Pack 2(3204808)(Important)Windows Server 2008 for 32-bit Systems Service Pack 2(3196726)(Important) Windows Server 2008 for x64-based Systems Service Pack 2 Internet Explorer 9 (3203621)(Moderate)Microsoft Windows Hyperlink Object Library(3208481)(Moderate) Not applicable Windows Server 2008 for x64-based Systems Service Pack 2(3204724)(Important)Windows Server 2008 for x64-based Systems Service Pack 2(3205638)(Critical) Windows Server 2008 for x64-based Systems Service Pack 2(3196348)(Critical) Windows Server 2008 for x64-based Systems Service Pack 2(3204808)(Important)Windows Server 2008 for x64-based Systems Service Pack 2(3196726)(Important) Windows Server 2008 for Itanium-based Systems Service Pack 2 Not applicable Not applicable Windows Server 2008 for Itanium-based Systems Service Pack 2(3204724)(Important)Windows Server 2008 for Itanium-based Systems Service Pack 2(3205638)(Critical) Windows Server 2008 for Itanium-based Systems Service Pack 2(3196348)(Critical) Windows Server 2008 for Itanium-based Systems Service Pack 2(3204808)(Important)Windows Server 2008 for Itanium-based Systems Service Pack 2(3196726)(Important) Windows 7 Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating Critical None Critical Critical Important Windows 7 for 32-bit Systems Service Pack 1Security Only Internet Explorer 11(3205394)(Critical) Not applicable                    Windows 7 for 32-bit Systems Service Pack 1(3205394)(Critical) Windows 7 for 32-bit Systems Service Pack 1(3205394)(Critical) Windows 7 for 32-bit Systems Service Pack 1(3205394)(Important) Windows 7 for 32-bit Systems Service Pack 1Monthly Rollup Internet Explorer 11(3207752)(Critical) Not applicable Windows 7 for 32-bit Systems Service Pack 1(3207752)(Critical) Windows 7 for 32-bit Systems Service Pack 1(3207752)(Critical) Windows 7 for 32-bit Systems Service Pack 1(3207752)(Important) Windows 7 for x64-based Systems Service Pack 1Security Only Internet Explorer 11(3205394)(Critical) Not applicable Windows 7 for x64-based Systems Service Pack 1(3205394)(Critical) Windows 7 for x64-based Systems Service Pack 1(3205394)(Critical) Windows 7 for x64-based Systems Service Pack 1(3205394)(Important) Windows 7 for x64-based Systems Service Pack 1Monthly Rollup Internet Explorer 11(3207752)(Critical) Not applicable Windows 7 for x64-based Systems Service Pack 1(3207752)(Critical) Windows 7 for x64-based Systems Service Pack 1(3207752)(Critical) Windows 7 for x64-based Systems Service Pack 1(3207752)(Important) Windows Server 2008 R2 Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating Moderate None Critical Critical Important Windows Server 2008 R2 for x64-based Systems Service Pack 1Security Only Internet Explorer 11(3205394)(Moderate) Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1(3205394)(Critical) Windows Server 2008 R2 for x64-based Systems Service Pack 1(3205394)(Critical) Windows Server 2008 R2 for x64-based Systems Service Pack 1(3205394)(Important) Windows Server 2008 R2 for x64-based Systems Service Pack 1Monthly Rollup Internet Explorer 11(3207752)(Moderate) Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1(3207752)(Critical) Windows Server 2008 R2 for x64-based Systems Service Pack 1(3207752)(Critical) Windows Server 2008 R2 for x64-based Systems Service Pack 1(3207752)(Important) Windows Server 2008 R2 for Itanium-based Systems Service Pack 1Security Only Not applicable Not applicable Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3205394)(Critical) Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3205394)(Critical) Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3205394)(Important) Windows Server 2008 R2 for Itanium-based Systems Service Pack 1Monthly Rollup Not applicable Not applicable Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3207752)(Critical) Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3207752)(Critical) Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3207752)(Important) Windows 8.1 Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating Critical None Critical Critical Important Windows 8.1 for 32-bit SystemsSecurity Only Internet Explorer 11(3205400)(Critical) Not applicable Windows 8.1 for 32-bit Systems(3205400)(Critical) Windows 8.1 for 32-bit Systems(3205400)(Critical) Windows 8.1 for 32-bit Systems(3205400)(Important) Windows 8.1 for 32-bit SystemsMonthly Rollup Internet Explorer 11(3205401)(Critical) Not applicable Windows 8.1 for 32-bit Systems(3205401)(Critical) Windows 8.1 for 32-bit Systems(3205401)(Critical) Windows 8.1 for 32-bit Systems(3205401)(Important) Windows 8.1 for x64-based SystemsSecurity Only Internet Explorer 11(3205400)(Critical) Not applicable Windows 8.1 for x64-based Systems(3205400)(Critical) Windows 8.1 for x64-based Systems(3205400)(Critical) Windows 8.1 for x64-based Systems(3205400)(Important) Windows 8.1 for x64-based SystemsMonthly Rollup Internet Explorer 11(3205401)(Critical) Not applicable Windows 8.1 for x64-based Systems(3205401)(Critical) Windows 8.1 for x64-based Systems(3205401)(Critical) Windows 8.1 for x64-based Systems(3205401)(Important) Windows Server 2012 and Windows Server 2012 R2 Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating Moderate None Critical Critical Important Windows Server 2012Security Only Internet Explorer 10(3205408)(Moderate) Not applicable Windows Server 2012(3205408)(Critical) Windows Server 2012(3205408)(Critical) Windows Server 2012(3205408)(Important) Windows Server 2012Monthly Rollup Internet Explorer 10(3205409)(Moderate) Not applicable Windows Server 2012(3205409)(Critical) Windows Server 2012(3205409)(Critical) Windows Server 2012(3205409)(Important) Windows Server 2012 R2Security Only Internet Explorer 11(3205400)(Moderate) Not applicable Windows Server 2012 R2(3205400)(Critical) Windows Server 2012 R2(3205400)(Critical) Windows Server 2012 R2(3205400)(Important) Windows Server 2012 R2Monthly Rollup Internet Explorer 11(3205401)(Moderate) Not applicable Windows Server 2012 R2(3205401)(Critical) Windows Server 2012 R2(3205401)(Critical) Windows Server 2012 R2(3205401)(Important) Windows RT 8.1 Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating Critical None Critical Critical Important Windows RT 8.1Monthly Rollup Internet Explorer 11(3205401)(Critical) Not applicable Windows RT 8.1(3205401)(Critical) Windows RT 8.1(3205401)(Critical) Windows RT 8.1(3205401)(Important) Windows 10 Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating Critical Critical Critical Critical Important Windows 10 for 32-bit Systems Internet Explorer 11(3205383)(Critical) Microsoft Edge(3205383)(Critical) Windows 10 for 32-bit Systems(3205383)(Critical) Windows 10 for 32-bit Systems(3205383)(Critical) Windows 10 for 32-bit Systems(3205383)(Important) Windows 10 for x64-based Systems Internet Explorer 11(3205383)(Critical) Microsoft Edge(3205383)(Critical) Windows 10 for x64-based Systems(3205383)(Critical) Windows 10 for x64-based Systems(3205383)(Critical) Windows 10 for x64-based Systems(3205383)(Important) Windows 10 Version 1511 for 32-bit Systems Internet Explorer 11(3205386)(Critical) Microsoft Edge(3205386)(Critical) Windows 10 Version 1511 for 32-bit Systems(3205386)(Critical) Windows 10 Version 1511 for 32-bit Systems(3205386)(Critical) Windows 10 Version 1511 for 32-bit Systems(3205386)(Important) Windows 10 Version 1511 for x64-based Systems Internet Explorer 11(3205386)(Critical) Microsoft Edge(3205386)(Critical) Windows 10 Version 1511 for x64-based Systems(3205386)(Critical) Windows 10 Version 1511 for x64-based Systems(3205386)(Critical) Windows 10 Version 1511 for x64-based Systems(3205386)(Important) Windows 10 Version 1607 for 32-bit Systems Internet Explorer 11(3206632)(Critical) Microsoft Edge(3206632)(Critical) Windows 10 Version 1607 for 32-bit Systems(3206632)(Critical) Windows 10 Version 1607 for 32-bit Systems(3206632)(Critical) Windows 10 Version 1607 for 32-bit Systems(3206632)(Important) Windows 10 Version 1607 for x64-based Systems Internet Explorer 11(3206632)(Critical) Microsoft Edge(3206632)(Critical) Windows 10 Version 1607 for x64-based Systems(3206632)(Critical) Windows 10 Version 1607 for x64-based Systems(3206632)(Critical) Windows 10 Version 1607 for x64-based Systems(3206632)(Important) Windows Server 2016 Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating Moderate Moderate Critical Critical Important Windows Server 2016 for x64-based Systems Internet Explorer 11(3206632)(Moderate) Microsoft Edge(3206632)(Moderate) Windows Server 2016 for x64-based Systems(3206632)(Critical) Windows Server 2016 for x64-based Systems(3206632)(Critical) Windows Server 2016 for x64-based Systems(3206632)(Important) Server Core installation option Bulletin Identifier MS16-144 MS16-145 MS16-146 MS16-147 MS16-149 Aggregate Severity Rating None None Critical Critical Important Windows Server 2008 for 32-bit Systems Service Pack 2(Server Core installation) Not applicable Not applicable Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)(3204724)(Important)Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)(3205638)(Critical) Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)(3196348)(Critical) Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)(3204808)(Important)Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)(3196726)(Important) Windows Server 2008 for x64-based Systems Service Pack 2(Server Core installation) Not applicable Not applicable Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)(3204724)(Important)Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)(3205638)(Critical) Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)(3196348)(Critical) Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)(3204808)(Important)Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)(3196726)(Important) Windows Server 2008 R2 for x64-based Systems Service Pack 1(Server Core installation)Security Only Not applicable Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3205394)(Critical) Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3205394)(Critical) Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3205394)(Important) Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)Monthly Rollup Not applicable Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3207752)(Critical) Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3207752)(Critical) Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3207752)(Important) Windows Server 2012(Server Core installation)Security Only Not applicable Not applicable Windows Server 2012 (Server Core installation)(3205408)(Critical) Windows Server 2012 (Server Core installation)(3205408)(Critical) Windows Server 2012 (Server Core installation)(3205408)(Important) Windows Server 2012(Server Core installation)Monthly Rollup Not applicable Not applicable Windows Server 2012 (Server Core installation)(3205409)(Critical) Windows Server 2012 (Server Core installation)(3205409)(Critical) Windows Server 2012 (Server Core installation)(3205409)(Important) Windows Server 2012 R2(Server Core installation)Security Only Not applicable Not applicable Windows Server 2012 R2 (Server Core installation)(3205400)(Critical) Windows Server 2012 R2 (Server Core installation)(3205400)(Critical) Windows Server 2012 R2 (Server Core installation)(3205400)(Important) Windows Server 2012 R2(Server Core installation)Monthly Rollup Not applicable Not applicable Windows Server 2012 R2 (Server Core installation)(3205401)(Critical) Windows Server 2012 R2 (Server Core installation)(3205401)(Critical) Windows Server 2012 R2 (Server Core installation)(3205401)(Important) Windows Server 2016 for x64-based Systems(Server Core installation) Not applicable Not applicable Windows Server 2016 for x64-based Systems(Server Core installation)(3206632)(Critical) Windows Server 2016 for x64-based Systems(Server Core installation)(3206632)(Critical) Windows Server 2016 for x64-based Systems(Server Core installation)(3206632)(Important) Windows Vista Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating None Important None Important None Windows Vista Service Pack 2 Not applicable Windows Vista Service Pack 2(3204723)(Important) Not applicable Windows Vista Service Pack 2(3203838)(Important) Not applicable Windows Vista x64 Edition Service Pack 2 Not applicable Windows Vista x64 Edition Service Pack 2(3204723)(Important) Not applicable Windows Vista x64 Edition Service Pack 2(3203838)(Important) Not applicable Windows Server 2008 Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating None Important None Important None Windows Server 2008 for 32-bit Systems Service Pack 2 Not applicable Windows Server 2008 for 32-bit Systems Service Pack 2(3204723)(Important) Not applicable Windows Server 2008 for 32-bit Systems Service Pack 2(3203838)(Important) Not applicable Windows Server 2008 for x64-based Systems Service Pack 2 Not applicable Windows Server 2008 for x64-based Systems Service Pack 2(3204723)(Important) Not applicable Windows Server 2008 for x64-based Systems Service Pack 2(3203838)(Important) Not applicable Windows Server 2008 for Itanium-based Systems Service Pack 2 Not applicable Windows Server 2008 for Itanium-based Systems Service Pack 2(3204723)(Important) Not applicable Windows Server 2008 for Itanium-based Systems Service Pack 2(3203838)(Important) Not applicable Windows 7 Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating None Important None Important None Windows 7 for 32-bit Systems Service Pack 1Security Only Not applicable Windows 7 for 32-bit Systems Service Pack 1(3205394)(Important) Not applicable                    Windows 7 for 32-bit Systems Service Pack 1(3205394)(Important) Not applicable Windows 7 for 32-bit Systems Service Pack 1Monthly Rollup Not applicable Windows 7 for 32-bit Systems Service Pack 1(3207752)(Important) Not applicable Windows 7 for 32-bit Systems Service Pack 1(3207752)(Important) Not applicable Windows 7 for x64-based Systems Service Pack 1Security Only Not applicable Windows 7 for x64-based Systems Service Pack 1(3205394)(Important) Not applicable Windows 7 for x64-based Systems Service Pack 1(3205394)(Important) Not applicable Windows 7 for x64-based Systems Service Pack 1Monthly Rollup Not applicable Windows 7 for x64-based Systems Service Pack 1(3207752)(Important) Not applicable Windows 7 for x64-based Systems Service Pack 1(3207752)(Important) Not applicable Windows Server 2008 R2 Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating None Important None Important None Windows Server 2008 R2 for x64-based Systems Service Pack 1Security Only Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1(3205394)(Important) Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1(3205394)(Important) Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1Monthly Rollup Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1(3207752)(Important) Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1(3207752)(Important) Not applicable Windows Server 2008 R2 for Itanium-based Systems Service Pack 1Security Only Not applicable Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3205394)(Important) Not applicable Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3205394)(Important) Not applicable Windows Server 2008 R2 for Itanium-based Systems Service Pack 1Monthly Rollup Not applicable Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3207752)(Important) Not applicable Windows Server 2008 R2 for Itanium-based Systems Service Pack 1(3207752)(Important) Not applicable Windows 8.1 Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating None Important None Important Critcal Windows 8.1 for 32-bit SystemsSecurity Only Not applicable Windows 8.1 for 32-bit Systems(3205400)(Important) Not applicable Windows 8.1 for 32-bit Systems(3205400)(Important) Adobe Flash Player(3209498)(Critical) Windows 8.1 for 32-bit SystemsMonthly Rollup Not applicable Windows 8.1 for 32-bit Systems(3205401)(Important) Not applicable Windows 8.1 for 32-bit Systems(3205401)(Important) Not applicable Windows 8.1 for x64-based SystemsSecurity Only Not applicable Windows 8.1 for x64-based Systems(3205400)(Important) Not applicable Windows 8.1 for x64-based Systems(3205400)(Important) Adobe Flash Player(3209498)(Critical) Windows 8.1 for x64-based SystemsMonthly Rollup Not applicable Windows 8.1 for x64-based Systems(3205401)(Important) Not applicable Windows 8.1 for x64-based Systems(3205401)(Important) Not applicable Windows Server 2012 and Windows Server 2012 R2 Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating None Important None Important Moderate Windows Server 2012Security Only Not applicable Windows Server 2012(3205408)(Important) Not applicable Windows Server 2012(3205408)(Important) Adobe Flash Player(3209498)(Moderate) Windows Server 2012Monthly Rollup Not applicable Windows Server 2012(3205409)(Important) Not applicable Windows Server 2012(3205409)(Important) Not applicable Windows Server 2012 R2Security Only Not applicable Windows Server 2012 R2(3205400)(Important) Not applicable Windows Server 2012 R2(3205400)(Important) Adobe Flash Player(3209498)(Moderate) Windows Server 2012 R2Monthly Rollup Not applicable Windows Server 2012 R2(3205401)(Important) Not applicable Windows Server 2012 R2(3205401)(Important) Not applicable Windows RT 8.1 Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating None Important None Important Critical Windows RT 8.1Monthly Rollup Not applicable Windows RT 8.1(3205401)(Important) Not applicable Windows RT 8.1(3205401)(Important) Adobe Flash Player(3209498)(Critical) Windows 10 Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating Important Important Important Important Critical Windows 10 for 32-bit Systems Windows 10 for 32-bit Systems(3205383)(Important) Windows 10 for 32-bit Systems(3205383)(Important) Windows 10 for 32-bit Systems(3205383)(Important) Windows 10 for 32-bit Systems(3205383)(Important) Adobe Flash Player(3209498)(Critical) Windows 10 for x64-based Systems Windows 10 for x64-based Systems(3205383)(Important) Windows 10 for x64-based Systems(3205383)(Important) Windows 10 for x64-based Systems(3205383)(Important) Windows 10 for x64-based Systems(3205383)(Important) Adobe Flash Player(3209498)(Critical) Windows 10 Version 1511 for 32-bit Systems Windows 10 Version 1511 for 32-bit Systems(3205386)(Important) Windows 10 Version 1511 for 32-bit Systems(3205386)(Important) Windows 10 Version 1511 for 32-bit Systems(3205386)(Important) Windows 10 Version 1511 for 32-bit Systems(3205386)(Important) Adobe Flash Player(3209498)(Critical) Windows 10 Version 1511 for x64-based Systems Windows 10 Version 1511 for x64-based Systems(3205386)(Important) Windows 10 Version 1511 for x64-based Systems(3205386)(Important) Windows 10 Version 1511 for x64-based Systems(3205386)(Important) Windows 10 Version 1511 for x64-based Systems(3205386)(Important) Adobe Flash Player(3209498)(Critical) Windows 10 Version 1607 for 32-bit Systems Windows 10 Version 1607 for 32-bit Systems(3206632)(Important) Windows 10 Version 1607 for 32-bit Systems(3206632)(Important) Windows 10 Version 1607 for 32-bit Systems(3206632)(Important) Windows 10 Version 1607 for 32-bit Systems(3206632)(Important) Adobe Flash Player(3209498)(Critical) Windows 10 Version 1607 for x64-based Systems Windows 10 Version 1607 for x64-based Systems(3206632)(Important) Windows 10 Version 1607 for x64-based Systems(3206632)(Important) Windows 10 Version 1607 for x64-based Systems(3206632)(Important) Windows 10 Version 1607 for x64-based Systems(3206632)(Important) Adobe Flash Player(3209498)(Critical) Windows Server 2016 Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating Important Important Important Important Moderate Windows Server 2016 for x64-based Systems Windows Server 2016 for x64-based Systems(3206632)(Important) Windows Server 2016 for x64-based Systems(3206632)(Important) Windows Server 2016 for x64-based Systems(3206632)(Important) Windows Server 2016 for x64-based Systems(3206632)(Important) Adobe Flash Player(3209498)(Moderate) Server Core installation Bulletin Identifier MS16-150 MS16-151 MS16-152 MS16-153 MS16-154 Aggregate Severity Rating Important Important Important Important None Windows Server 2008 for 32-bit Systems Service Pack 2(Server Core installation) Not applicable Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)(3204723)(Important) Not applicable Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)(3203838)(Important) Not applicable Windows Server 2008 for x64-based Systems Service Pack 2(Server Core installation) Not applicable Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)(3204723)(Important) Not applicable Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)(3203838)(Important) Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1(Server Core installation)Security Only Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3205394)(Important) Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3205394)(Important) Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)Monthly Rollup Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3207752)(Important) Not applicable Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)(3207752)(Important) Not applicable Windows Server 2012(Server Core installation)Security Only Not applicable Windows Server 2012 (Server Core installation)(3205408)(Important) Not applicable Not applicable Not applicable Windows Server 2012(Server Core installation)Monthly Rollup Not applicable Windows Server 2012 (Server Core installation)(3205409)(Important) Not applicable Not applicable Not applicable Windows Server 2012 R2(Server Core installation)Security Only Not applicable Windows Server 2012 R2 (Server Core installation)(3205400)(Important) Not applicable Windows Server 2012 R2 (Server Core installation)(3205400)(Important) Not applicable Windows Server 2012 R2(Server Core installation)Monthly Rollup Not applicable Windows Server 2012 R2 (Server Core installation)(3205401)(Important) Not applicable Windows Server 2012 R2 (Server Core installation)(3205401)(Important) Not applicable Windows Server 2016 for x64-based Systems(Server Core installation) Windows Server 2016 for x64-based Systems(Server Core installation)(3206632)(Important) Windows Server 2016 for x64-based Systems(Server Core installation)(3206632)(Important) Windows Server 2016 for x64-based Systems(Server Core installation)(3206632)(Important) Windows Server 2016 for x64-based Systems(Server Core installation)(3206632)(Important) Not applicable This bulletin spans more than one software category.
See other tables in this section for additional affected software. Microsoft .NET Framework Windows Vista and Windows Server 2008Microsoft .NET Framework Updates for 2.0, 4.5.2, 4.6 (KB3210142) Windows Vista Bulletin Identifier MS16-155 Aggregate Severity Rating Important Windows Vista for 32-bit Systems Service Pack 2 Microsoft .NET Framework 3.5(3210129)(Important)Microsoft .NET Framework 4.5.2(3210139)(Important)Microsoft .NET Framework 4.6(3210136)(Important) Windows Vista for x64-based Systems Service Pack 2 Microsoft .NET Framework 3.5(3210129)(Important)Microsoft .NET Framework 4.5.2(3210139)(Important)Microsoft .NET Framework 4.6(3210136)(Important) Windows Server 2008 Bulletin Identifier MS16-155 Aggregate Severity Rating Important Windows Server 2008 for 32-bit Systems Service Pack 2 Microsoft .NET Framework 3.5(3210129)(Important)Microsoft .NET Framework 4.5.2(3210139)(Important)Microsoft .NET Framework 4.6(3210136)(Important) Windows Server 2008 for x64-based Systems Service Pack 2 Microsoft .NET Framework 3.5(3210129)(Important)Microsoft .NET Framework 4.5.2(3210139)(Important)Microsoft .NET Framework 4.6(3210136)(Important) Windows 7 and Windows Server 2008 R2Microsoft .NET Framework Updates for 3.5.1, 4.5.2, 4.6/4.6.1, 4.6.2 (KB3205402) Windows 7 Bulletin Identifier MS16-155 Aggregate Severity Rating Important Windows 7 for 32-bit Systems Service Pack 1 Microsoft .NET Framework 3.5(3210131)(Important)Microsoft .NET Framework 4.5.2(3210139)(Important)Microsoft .NET Framework 4.6/4.6.1(3210136)(Important)Microsoft .NET Framework 4.6.2(3205379)(Important) Windows 7 for x64-based Systems Service Pack 1 Microsoft .NET Framework 3.5(3210131)(Important)Microsoft .NET Framework 4.5.2(3210139)(Important)Microsoft .NET Framework 4.6/4.6.1(3210136)(Important)Microsoft .NET Framework 4.6.2(3205379)(Important) Windows Server 2008 R2 Bulletin Identifier MS16-155 Aggregate Severity Rating Important Windows Server 2008 R2 for x64-based Systems Service Pack 1 Microsoft .NET Framework 3.5(3210131)(Important)Microsoft .NET Framework 4.5.2(3210139)(Important)Microsoft .NET Framework 4.6/4.6.1(3210136)(Important)Microsoft .NET Framework 4.6.2(3205379)(Important) Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 Microsoft .NET Framework 3.5(3210131)(Important) Windows Server 2012Microsoft .NET Framework Updates for 3.5, 4.5.2, 4.6/4.6.1, 4.6.2 (KB3205403) Bulletin Identifier MS16-155 Aggregate Severity Rating Important Windows Server 2012 Microsoft .NET Framework 3.5(3210130)(Important)Microsoft .NET Framework 4.5.2(3210138)(Important)Microsoft .NET Framework 4.6/4.6.1(3210133)(Important)Microsoft .NET Framework 4.6.2(3205377)(Important) Windows 8.1 and Windows Server 2012 R2Microsoft .NET Framework Updates for 3.5, 4.5.2, 4.6/4.6.1, 4.6.2 (KB3205404) Windows 8.1 Bulletin Identifier MS16-155 Aggregate Severity Rating Important Windows 8.1 for 32-bit Systems Microsoft .NET Framework 3.5(3210132)(Important)Microsoft .NET Framework 4.5.2(3210137)(Important)Microsoft .NET Framework 4.6/4.6.1(3210135)(Important)Microsoft .NET Framework 4.6.2(3205378)(Important) Windows 8.1 for x64-based Systems Microsoft .NET Framework 3.5(3210132)(Important)Microsoft .NET Framework 4.5.2(3210137)(Important)Microsoft .NET Framework 4.6/4.6.1(3210135)(Important)Microsoft .NET Framework 4.6.2(3205378)(Important) Windows Server 2012 R2 Windows Server 2012 R2 Microsoft .NET Framework 3.5(3210132)(Important)Microsoft .NET Framework 4.5.2(3210137)(Important)Microsoft .NET Framework 4.6/4.6.1(3210135)(Important)Microsoft .NET Framework 4.6.2(3205378)(Important) Windows 10 Bulletin Identifier MS16-155 Aggregate Severity Rating Important Windows 10 Version 1607 for 32-bit Systems(3206632) Microsoft .NET Framework 4.6.2(Important) Windows 10 Version 1607 for x64-based Systems(3206632) Microsoft .NET Framework 4.6.2(Important) Windows Server 2016 Bulletin Identifier MS16-155 Aggregate Severity Rating Important Windows Server 2016 for x64-based Systems(3206632) Microsoft .NET Framework 4.6.2(Important) Server Core installation option Bulletin Identifier MS16-155 Aggregate Severity Rating Important Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) Microsoft .NET Framework 3.5(3210131)(Important)Microsoft .NET Framework 4.6/4.6.1(3210136)(Important)Microsoft .NET Framework 4.6.2(3205379)(Important) Windows Server 2012 (Server Core installation) Microsoft .NET Framework 3.5(3210130)(Important)Microsoft .NET Framework 4.5.2(3210138)(Important)Microsoft .NET Framework 4.6/4.6.1(3210133)(Important)Microsoft .NET Framework 4.6.2(3205377)(Important) Windows Server 2012 R2 (Server Core installation) Microsoft .NET Framework 3.5(3210132)(Important)Microsoft .NET Framework 4.5.2(3210137)(Important)Microsoft .NET Framework 4.6/4.6.1(3210135)(Important)Microsoft .NET Framework 4.6.2(3205378)(Important) Windows Server 2016 for x64-based Systems (Server Core installation)(3206632) Microsoft .NET Framework 4.6.2(Important) This bulletin spans more than one software category.
See other tables in this section for additional affected software. Microsoft Office 2007 Bulletin Identifier MS16-148 Aggregate Severity Rating Critical Microsoft Office 2007 Service Pack 3 Microsoft Excel 2007 Service Pack 3(3128019)(Important)Microsoft Word 2007 Service Pack 3(3128025)(Important)Microsoft Office 2007 Service Pack 3(2883033)(Critical)Microsoft Office 2007 Service Pack 3(3128020)(Important) Microsoft Office 2010 Bulletin Identifier MS16-148 Aggregate Severity Rating Critical Microsoft Office 2010 Service Pack 2 (32-bit editions) Microsoft Office 2010 Service Pack 2 (32-bit editions)(3128032)(Important)Microsoft Office 2010 Service Pack 2 (32-bit editions)(3118380)(Important)Microsoft Office 2010 Service Pack 2 (32-bit editions)(2889841)(Critical)Microsoft Excel 2010 Service Pack 2 (32-bit editions)(3128037)(Important)Microsoft Publisher 2010 Service Pack 2 (32-bit editions)(3114395)(Important)Microsoft Word 2010 Service Pack 2 (32-bit editions)(3128034)(Important) Microsoft Office 2010 Service Pack 2 (64-bit editions) Microsoft Office 2010 Service Pack 2 (64-bit editions)(3128032)(Important)Microsoft Office 2010 Service Pack 2 (64-bit editions)(3118380)(Important)Microsoft Office 2010 Service Pack 2 (64-bit editions)(2889841)(Critical)Microsoft Excel 2010 Service Pack 2 (64-bit editions)(3128037)(Important)Microsoft Publisher 2010 Service Pack 2 (64-bit editions)(3114395)(Important)Microsoft Word 2010 Service Pack 2 (64-bit editions)(3128034)(Important) Microsoft Office 2013 Bulletin Identifier MS16-148 Aggregate Severity Rating Important Microsoft Office 2013 Service Pack 1 (32-bit editions) Microsoft Excel 2013 Service Pack 1 (32-bit editions)(3128008)(Important)Microsoft Office 2013 Service Pack 1 (32-bit editions)(3127968)(Important) Microsoft Office 2013 Service Pack 1 (64-bit editions) Microsoft Excel 2013 Service Pack 1 (64-bit editions)(3128008)(Important)Microsoft Office 2013 Service Pack 1 (64-bit editions)(3127968)(Important) Microsoft Office 2013 RT Bulletin Identifier MS16-148 Aggregate Severity Rating Important Microsoft Office 2013 RT Service Pack 1 Microsoft Excel 2013 RT Service Pack 1(3128008)(Important)Microsoft Office 2013 RT Service Pack 1(3127968)(Important) Microsoft Office 2016 Bulletin Identifier MS16-148 Aggregate Severity Rating Important Microsoft Office 2016 (32-bit edition) Microsoft Excel 2016 (32-bit edition)(3128016)(Important)Microsoft Office 2016 (32-bit edition)(3127986)(Important)Microsoft Office 2016 (32-bit edition)(Important)[1] Microsoft Office 2016 (64-bit edition) Microsoft Excel 2016 (64-bit edition)(3128016)(Important)Microsoft Office 2016 (64-bit edition)(3127986)(Important)Microsoft Office 2016 (64-bit edition)(Important)[1] Microsoft Office for Mac 2011 Bulletin Identifier MS16-148 Aggregate Severity Rating Important Microsoft Office for Mac 2011(3198808)(Important)Microsoft Excel for Mac 2011(3198808)(Important)Microsoft Word for Mac 2011(3198808)(Important) Microsoft Office 2016 for Mac Bulletin Identifier MS16-148 Aggregate Severity Rating Important Microsoft Office 2016 for Mac(3198800)(Important)Microsoft Excel 2016 for Mac(3198800)(Important) Other Office for Mac Software Bulletin Identifier MS16-148 Aggregate Severity Rating Important Microsoft Auto Updater for Mac Microsoft Auto Updater for Mac[2](Important) Other Office Software Bulletin Identifier MS16-148 Aggregate Severity Rating Critical Microsoft Office Compatibility Pack Service Pack 3 Microsoft Office Compatibility Pack Service Pack 3(3128022)(Important)Microsoft Office Compatibility Pack Service Pack 3(3128024)(Important) Microsoft Excel Viewer Microsoft Excel Viewer(3128023)(Important) Microsoft Word Viewer Microsoft Word Viewer(3128044)(Important)Microsoft Word Viewer(3127995)(Critical) [1]This entry references the Click-to-Run (C2R) version only.This bulletin spans more than one software category.
See other tables in this section for additional affected software.This bulletin spans more than one software category.
See other tables in this section for additional affected software.

MS16-147 – Critical: Security Update for Microsoft Uniscribe (3204063) – Version:...

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 severity ratings indicated for each affected software 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 December bulletin summary.Note Please see the Security Update Guide for a new approach to consuming the security update information. You can customize your views and create affected software spreadsheets, as well as download data via a restful API.

For more information, please see the Security Updates Guide FAQ.

As a reminder, the Security Updates Guide will be replacing security bulletins as of February 2017. Please see our blog post, Furthering our commitment to security updates, for more details.[1]Beginning with the October 2016 release, Microsoft has changed 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.[2] Windows 10 and Windows Server 2016 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. Please note that effective December 13, 2016, Windows 10 and Windows Server 2016 details for the Cumulative Updates will be documented in Release Notes. Please refer to the Release Notes for OS Build numbers, Known Issues, and affected file list information.*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).Note The vulnerability discussed in this bulletin affects Windows Server 2016 Technical Preview 5.

Although an update is available for Windows Server 2016 Technical Preview 5 via Windows Update, Microsoft recommends that customers upgrade to Window Server 2016 at their earliest convenience. 

MS16-150 – Important: Security Update for Secure Kernel Mode (3205642) –...

Security Update for Secure Kernel Mode (3205642)Published: December 13, 2016Version: 1.0This security update resolves a vulnerability in Microsoft Windows.

The vulnerability could allow elevation of privilege if a locally-authenticated attacker runs a specially crafted application on a targeted system.

An attacker who successfully exploited the vulnerability could violate virtual trust levels (VTL).This security update is rated Important for all supported editions of Windows 10 and Windows Server 2016.

For more information, see the Affected Software section.The update addresses the vulnerability by correcting how Windows Secure Kernel Mode handles objects in memory properly enforce VLTs.

For more information about the vulnerability, see the Vulnerability Information section.For more information about this update, see Microsoft Knowledge Base Article 3205642.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 severity ratings indicated for each affected software 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 December bulletin summary.Note Please see the Security Update Guide for a new approach to consuming the security update information. You can customize your views and create affected software spreadsheets, as well as download data via a restful API.

For more information, please see the Security Updates Guide FAQ.

As a reminder, the Security Updates Guide will be replacing security bulletins as of February 2017. Please see our blog post, Furthering our commitment to security updates, for more details.[1] Windows 10 and Windows Server 2016 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. Please note that effective December 13, 2016, Windows 10 and Windows Server 2016 details for the Cumulative Updates will be documented in Release Notes. Please refer to the Release Notes for OS Build numbers, Known Issues, and affected file list information.*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).Note The vulnerability discussed in this bulletin affects Windows Server 2016 Technical Preview 5.

Although an update is available for Windows Server 2016 Technical Preview 5 via Windows Update, Microsoft recommends that customers upgrade to Window Server 2016 at your earliest convenienceWindows Secure Kernel Mode Elevation of Privilege Vulnerability– CVE-2016-7271An elevation of privilege vulnerability exists when Windows Secure Kernel Mode fails to properly handle objects in memory.

An attacker who successfully exploited the vulnerability could violate virtual trust levels (VTL).A locally-authenticated attacker could attempt to exploit the vulnerability by running a specially crafted application on a targeted system.The security update addresses the vulnerability by correcting how Windows handles objects in memory to properly enforce VLTsThe 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 Secure Kernel Mode Elevation of Privilege Vulnerability CVE-2016-7271 No No Mitigating FactorsMicrosoft has not identified any mitigating factors for this vulnerability.WorkaroundsMicrosoft has not identified any workarounds for this vulnerability.For Security Update Deployment information, see the Microsoft Knowledge Base article referenced here in the Executive Summary.Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See Acknowledgments for more information.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.V1.0 (December 13, 2016): Bulletin published. Page generated 2016-12-07 12:28-08:00.

MS16-155 – Important: Security Update for .NET Framework (3205640) – Version:...

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 severity ratings indicated for each affected software 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 December bulletin summary.Note: Please see the Security Update Guide for a new approach to consuming the security update information. You can customize your views and create affected software spreadsheets, as well as download data via a restful API.

For more information, please see the Security Updates Guide FAQ.

As a reminder, the Security Updates Guide will be replacing security bulletins as of February 2017. Please see our blog post, Furthering our commitment to security updates, for more details.[1]Beginning with the October 2016 release, Microsoft has changed the update servicing model for Microsoft .NET Framework.

For more information, please see this Microsoft .NET Blog Post.[2]This number is the Parent package KB number. Users will be offered the Parent KB; however, the package KB numbers listed for each platform will be displayed in Add Remove Programs.[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. Please note that effective December 13, 2016, Windows 10 and Windows Server 2016 details for the Cumulative Updates will be documented in Release Notes. Please refer to the Release Notes for OS Build numbers, Known Issues, and affected file list information.Note The vulnerability discussed in this bulletin affects Windows Server 2016 Technical Preview 5.

Although an update is available for Windows Server 2016 Technical Preview 5 via Windows Update, Microsoft recommends that customers upgrade to Window Server 2016 at your earliest convenience. Operating System Component                                                             .NET Information Disclosure Vulnerability - CVE-2016-7270 Updates Replaced          Windows Vista and Windows Server 2008Microsoft .NET Framework Updates for 2.0, 4.5.2, 4.6 (KB3210142) [2] Windows Vista Windows Vista for 32-bit Systems Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 2(3210129) Not applicable[4] 3188744 in MS16-120 3163244 in MS16-091 Windows Vista for x64-based Systems Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 2(3210129) Not applicable[4] 3188744 in MS16-120 3163244 in MS16-091 Windows Vista for 32-bit Systems Service Pack 2 Microsoft .NET Framework 4.5.2(3210139) Not applicable[4] 3188744 in MS16-120 Windows Vista for x64-based Systems Service Pack 2 Microsoft .NET Framework 4.5.2(3210139) Not applicable[4] 3188744 in MS16-120 Windows Vista for 32-bit Systems Service Pack 2 Microsoft .NET Framework 4.6(3210136) Not applicable[4] 3188744 in MS16-120 Windows Vista for x64-based Systems Service Pack 2 Microsoft .NET Framework 4.6(3210136) Not applicable[4] 3188744 in MS16-120 Windows Server 2008 Windows Server 2008 for 32-bit Systems Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 2(3210129) Not applicable[4] 3188744 in MS16-120 3163244 in MS16-091 Windows Server 2008 for x64-based Systems Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 2(3210129) Not applicable[4] 3188744 in MS16-120 3163244 in MS16-091 Windows Server 2008 for Itanium-based Systems Service Pack 2 Microsoft .NET Framework 2.0 Service Pack 2(3210129) Not applicable[4] 3188744 in MS16-120 3163244 in MS16-091 Windows Server 2008 for 32-bit Systems Service Pack 2 Microsoft .NET Framework 4.5.2(3210139) Not applicable[4] 3188744 in MS16-120 Windows Server 2008 for x64-based Systems Service Pack 2 Microsoft .NET Framework 4.5.2(3210139) Not applicable[4] 3188744 in MS16-120 Windows Server 2008 for 32-bit Systems Service Pack 2 Microsoft .NET Framework 4.6(3210136) Not applicable[4] 3188744 in MS16-120 Windows Server 2008 for x64-based Systems Service Pack 2 Microsoft .NET Framework 4.6(3210136) Not applicable[4] 3188744 in MS16-120 Windows 7 and Windows Server 2008 R2Microsoft .NET Framework Updates for 3.5.1, 4.5.2, 4.6,4.6.1, 4.6.2 (KB3205402) [2] Windows 7 Windows 7 for 32-bit Systems Service Pack 1 Microsoft .NET Framework 3.5.1(3210131) Not applicable[4] None Windows 7 for x64-based Systems Service Pack 1 Microsoft .NET Framework 3.5.1(3210131) Not applicable[4] None Windows 7 for 32-bit Systems Service Pack 1 Microsoft .NET Framework 4.5.2(3210139) Not applicable[4] All previously released updates[4] Windows 7 for x64-based Systems Service Pack 1 Microsoft .NET Framework 4.5.2(3210139) Not applicable[4] All previously released updates[4] Windows 7 for 32-bit Systems Service Pack 1 Microsoft .NET Framework 4.6/4.6.1(3210136) Not applicable[4] All previously released updates[4] Windows 7 for x64-based Systems Service Pack 1 Microsoft .NET Framework 4.6/4.6.1(3210136) Not applicable[4] All previously released updates[4] Windows 7 for 32-bit Systems Service Pack 1 Microsoft .NET Framework 4.6.2(3205379) ImportantInformation Disclosure None Windows 7 for x64-based Systems Service Pack 1 Microsoft .NET Framework 4.6.2(3205379) ImportantInformation Disclosure None Windows Server 2008 R2 Windows Server 2008 R2 for x64-based Systems Service Pack 1 Microsoft .NET Framework 3.5.1(3210131) Not applicable[4] None Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 Microsoft .NET Framework 3.5.1(3210131) Not applicable[4] None Windows Server 2008 R2 for x64-based Systems Service Pack 1 Microsoft .NET Framework 4.5.2(3210139) Not applicable[4] All previously released updates[4] Windows Server 2008 R2 for x64-based Systems Service Pack 1 Microsoft .NET Framework 4.6/4.6.1(3210136) Not applicable[4] All previously released updates[4] Windows Server 2008 R2 for x64-based Systems Service Pack 1 Microsoft .NET Framework 4.6.2(3205379) ImportantInformation Disclosure None Windows Server 2012Microsoft .NET Framework Updates for 3.5, 4.5.2, 4.6,4.6.1, 4.6.2 (KB3205403) [2] Windows Server 2012 Microsoft .NET Framework 3.5(3210130) Not applicable[4] None Windows Server 2012 Microsoft .NET Framework 4.5.2(3210138) Not applicable[4] All previously released updates[4] Windows Server 2012 Microsoft .NET Framework 4.6/4.6.1(3210133) Not applicable[4] All previously released updates[4] Windows Server 2012 Microsoft .NET Framework 4.6.2(3205377) ImportantInformation Disclosure None Windows 8.1 and Windows Server 2012 R2Microsoft .NET Framework Updates for 3.5, 4.5.2, 4.6,4.6.1, 4.6.2 (KB3205404) [2] Windows 8.1 Windows 8.1 for 32-bit Systems Microsoft .NET Framework 3.5(3210132) Not applicable[4] None Windows 8.1 for x64-based Systems Microsoft .NET Framework 3.5(3210132) Not applicable[4] None Windows 8.1 for 32-bit Systems Microsoft .NET Framework 4.5.2(3210137) Not applicable[4] All previously released updates[4] Windows 8.1 for x64-based Systems Microsoft .NET Framework 4.5.2(3210137) Not applicable[4] All previously released updates[4] Windows 8.1 for 32-bit Systems Microsoft .NET Framework 4.6/4.6.1(3210135) Not applicable[4] All previously released updates[4] Windows 8.1 for x64-based Systems Microsoft .NET Framework 4.6/4.6.1(3210135) Not applicable[4] All previously released updates[4] Windows 8.1 for 32-bit Systems Microsoft .NET Framework 4.6.2(3205378) ImportantInformation Disclosure None Windows 8.1 for x64-based Systems Microsoft .NET Framework 4.6.2(3205378) ImportantInformation Disclosure None Windows 8.1 RT Windows 8.1 RT Microsoft .NET Framework 4.5.2(3210137) Not applicable[4] All previously released updates[4] Windows 8.1 RT Microsoft .NET Framework 4.6/4.6.1(3210135) Not applicable[4] All previously released updates[4] Windows 8.1 RT Microsoft .NET Framework 4.6.2(3205378) ImportantInformation Disclosure None Windows 2012 R2 Windows Server 2012 R2 Microsoft .NET Framework 3.5(3210132) Not applicable[4] None Windows Server 2012 R2 Microsoft .NET Framework 4.5.2(3210137) Not applicable[4] All previously released updates[4] Windows Server 2012 R2 Microsoft .NET Framework 4.6/4.6.1(3210135) Not applicable[4] All previously released updates[4] Windows Server 2012 R2 Microsoft .NET Framework 4.6.2(3205378) ImportantInformation Disclosure None Windows 10 Windows 10 Version 1607 for 32-bit Systems [3](3206632) Microsoft .NET Framework 4.6.2 ImportantInformation Disclosure 3200970 Windows 10 Version 1607 for x64-based Systems [3](3206632) Microsoft .NET Framework 4.6.2 ImportantInformation Disclosure 3200970 Windows Server 2016 for x64-based Systems [3](3206632) Microsoft .NET Framework 4.6.2 ImportantInformation Disclosure 3200970 Server Core installation option Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) Microsoft .NET Framework 3.5.1(3210131) Not applicable[4] None Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) Microsoft .NET Framework 4.6/4.6.1(3210136) Not applicable[4] All previously released updates[4] Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) Microsoft .NET Framework 4.6.2(3205379) ImportantInformation Disclosure None Windows Server 2012 (Server Core installation) Microsoft .NET Framework 3.5(3210130) Not applicable[4] None Windows Server 2012 (Server Core installation) Microsoft .NET Framework 4.5.2(3210138) Not applicable[4] All previously released updates[4] Windows Server 2012 (Server Core installation) Microsoft .NET Framework 4.6/4.6.1(3210133) Not applicable[4] All previously released updates[4] Windows Server 2012 (Server Core installation) Microsoft .NET Framework 4.6.2(3205377) ImportantInformation Disclosure None Windows Server 2012 R2 (Server Core installation) Microsoft .NET Framework 3.5(3210132) Not applicable[4] None Windows Server 2012 R2 (Server Core installation) Microsoft .NET Framework 4.5.2(3210137) Not applicable[4] All previously released updates[4] Windows Server 2012 R2 (Server Core installation) Microsoft .NET Framework 4.6/4.6.1(3210135) Not applicable[4] All previously released updates[4] Windows Server 2012 R2 (Server Core installation) Microsoft .NET Framework 4.6.2(3205378) ImportantInformation Disclosure None Windows Server 2016 for x64-based Systems (Server Core installation)[3](3206632) Microsoft .NET Framework 4.6.2 ImportantInformation Disclosure 3200970 [1]Beginning with the October 2016 release, Microsoft has changed the update servicing model for Microsoft .NET Framework.

For more information, please see this Microsoft .NET Blog Post.[2] This number is the Parent package KB number. Users will be offered the Parent KB; however, the package KB numbers listed for each platform will be displayed in Add Remove Programs.[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. Please note that effective December 13, 2016, Windows 10 and Windows Server 2016 details for the Cumulative Updates will be documented in Release Notes. Please refer to the Release Notes for OS Build numbers, Known Issues, and affected file list information.[4]Microsoft .NET Framework 2.0, 4.5.2 and 4.6/4.6.1 are rollup patches and include all previous updates as well as this month’s updates. Please see This Page for more information.Note The vulnerability discussed in this bulletin affects Windows Server 2016 Technical Preview 5.

An update is available for Windows Server 2016 Technical Preview 5 via Windows Update.

To be protected from the vulnerability, Microsoft recommends that customers running Windows Server 2016 Technical Preview 5 upgrade to Windows Server 2016.

MS16-151 – Important: Security Update for Windows Kernel-Mode Drivers (3205651) –...

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 severity ratings indicated for each affected software 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 December bulletin summary.Note Please see the Security Update Guide for a new approach to consuming the security update information. You can customize your views and create affected software spreadsheets, as well as download data via a restful API.

For more information, please see the Security Updates Guide FAQ.

As a reminder, the Security Updates Guide will be replacing security bulletins as of February 2017. Please see our blog post, Furthering our commitment to security updates, for more details.[1]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.[3] Windows 10 and Windows Server 2016 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. Please note that effective December 13, 2016, Windows 10 and Windows Server 2016 details for the Cumulative Updates will be documented in Release Notes. Please refer to the Release Notes for OS Build numbers, Known Issues, and affected file list information.*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).

MS16-153 – Important: Security Update for Common Log File System Driver...

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 December bulletin summary.Note: Please see the Security Update Guide for a new approach to consuming the security update information. You can customize your views and create affected software spreadsheets, as well as download data via a restful API.

For more information, please see the Security Updates Guide FAQ.

As a reminder, the Security Updates Guide will be replacing security bulletins as of February 2017. Please see our blog post, Furthering our commitment to security updates, for more details.[1]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 and Windows Server 2016.

For more information, please see this Microsoft TechNet article.[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 update is available via the Windows Update Catalog. Please note that effective December 13, 2016, Windows 10 and Windows Server 2016 details for the Cumulative Updates will be documented in Release Notes. Please refer to the Release Notes for OS Build numbers, Known Issues, and affected file list information.Note The vulnerability discussed in this bulletin affects Windows Server 2016 Technical Preview 5.

Although an update is available for Windows Server 2016 Technical Preview 5 via Windows Update, Microsoft recommends that customers upgrade to Window Server 2016 at your earliest convenience. *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).

MS16-144 – Critical: Cumulative Security Update for Internet Explorer (3204059) –...

Multiple Information Disclosure Vulnerabilities Information disclosure vulnerabilities exist in the way that the affected components handle objects in memory.

An attacker who successfully exploited these vulnerabilities could obtain information to further compromise a target system. In a web-based attack scenario an attacker could host a website in an 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 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 Windows Hyperlink Object Library Information Disclosure Vulnerability CVE-2016-7278 No No Microsoft Browser Information Disclosure Vulnerability CVE-2016-7282 Yes No Internet Explorer Information Disclosure Vulnerability CVE-2016-7284 No No Mitigating Factors Microsoft has not identified any mitigating factors for these vulnerabilities. Workarounds Microsoft has not identified any workarounds for these vulnerabilities. Multiple Microsoft Browser Memory Corruption Vulnerabilities Remote code execution vulnerabilities exist when Microsoft Browsers improperly accesses objects in memory.

These vulnerabilities could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user.

An attacker who successfully exploited these 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 these 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 these 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 by an enticement in an email or Instant Messenger message, or by getting them to open an attachment sent through email. The update addresses these 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-7279 No No Internet Explorer Memory Corruption Vulnerability CVE-2016-7283 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 Security Feature Bypass Vulnerability A security feature bypass vulnerability exists when the Microsoft browsers fail to correctly apply Same Origin Policy for scripts running inside Web Workers. An attacker could trick a user into loading a page with malicious content.

To exploit this vulnerability, an attacker would need to trick a user into loading a page or visiting a site.

The page could also be injected into a compromised site or ad network. The update addresses the vulnerability by correcting the Same Origin Policy check for scripts running inside Web Workers. The following table contains links to the standard entry for the vulnerability in the Common Vulnerabilities and Exposures list: Vulnerability title CVE number Publicly disclosed Exploited Microsoft Browser Security Feature Bypass Vulnerability CVE-2016-7281 Yes No Mitigating Factors Microsoft has not identified any mitigating factors for this vulnerability. Workarounds Microsoft has not identified any workarounds for this vulnerability. Multiple Scripting Engine Memory Corruption Vulnerabilities Multiple remote code execution vulnerabilities exist in the way affected Microsoft scripting engines render when handling objects in memory in Microsoft browsers.

The vulnerabilities could corrupt memory in such a way that an attacker could 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, an attacker who successfully exploited the vulnerabilities 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. In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerabilities through a Microsoft browser and then convince a user to view the website.

An attacker could also embed an ActiveX control marked "safe for initialization" in an application or Microsoft Office document that hosts the Edge rendering engine.

The attacker could also take advantage of compromised websites, and websites that accept or host user-provided content or advertisements.

These websites could contain specially crafted content that could exploit the vulnerabilities. The security update addresses the vulnerabilities by modifying how the affected Microsoft scripting engines 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-7202 Yes No Scripting Engine Memory Corruption Vulnerability CVE-2016-7287 No No Mitigating Factors Microsoft has not identified any mitigating factors for these vulnerabilities. Workarounds Microsoft has not identified any workarounds for these vulnerabilities.