CVE-2016-0187

Обходное решение

Restrict access to VBScript.dll and JScript.dll For 32-bit systems, enter the following command at an administrative command prompt:

For 64-bit systems, enter the following command at an administrative command prompt:

Impact of Workaround. Websites that use VBScript or JScript may not work properly.

How to undo the workaround. For 32-bit systems, enter the following command at an administrative command prompt:

For 64-bit systems, enter the following command at an administrative command prompt:

FAQ

For my particular system and Internet Explorer configuration, which update addresses the vulnerabilities discussed in CVE-2016-0187 or CVE-2016-0189? CVE-2016-0187 and CVE-2016-0189 are vulnerabilities in the JScript and VBScript engines. Although the attack vector is through Internet Explorer, the vulnerabilities are addressed by the updates released in this bulletin (MS16-051) for systems running Internet Explorer 9, Internet Explorer 10, and Internet Explorer 11. For Internet Explorer 7 and earlier, the vulnerabilities are addressed by the updates described in MS16-053.

I am running Internet Explorer on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2. Does this mitigate these vulnerabilities? Yes. By default, Internet Explorer on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted web content on a server. This is a mitigating factor for websites that you have not added to the Internet Explorer Trusted sites zone.

Can EMET help mitigate attacks that attempt to exploit these vulnerabilities? Yes. The Enhanced Mitigation Experience Toolkit (EMET) enables users to manage security mitigation technologies that help make it more difficult for attackers to exploit memory corruption vulnerabilities in a given piece of software. EMET can help mitigate attacks that attempt to exploit these vulnerabilities in Internet Explorer on systems where EMET is installed and configured to work with Internet Explorer.

For more information about EMET, see the Enhanced Mitigation Experience Toolkit.

Why do I see both JScript.dll and VBScript.dll in the packages for this cumulative security update? This security update ships as a cumulative update for the JScript and VBScript scripting engines. While both engines are included in this release, the components affected by the security fixes covered by this bulletin are listed above in the section Affected Software.

How do I determine which versions of JScript and VBScript scripting engines are installed on my system? The JScript and VBScript scripting engines are installed with supported releases of Microsoft Windows. In addition, installing a newer version of Internet Explorer on a system can change the versions of the JScript and VBScript scripting engines that are installed.

To determine which versions of the JScript or VBScript scripting engines are installed on your system, perform the following steps:

1. Open Windows Explorer.
2. Navigate to the %systemroot%\system32 directory.
3. For VBScript, right-click vbscript.dll, select Properties, and then click the Details tab.
4. For JScript, right-click jscript.dll, select Properties, and then click the Details tab.

The version number is listed in the File Version field. If your file version starts with 5.8, for example 5.8.7600.16385, then VBScript 5.8 is installed on your system.

Once I know the versions of the JScript or VBScript scripting engine installed on my system, where do I get the update? The affected software in this bulletin apply to systems without Internet Explorer installed and to systems with Internet Explorer 7 or earlier versions installed. Customers with systems running Internet Explorer 8 or later should apply the Internet Explorer Cumulative Update (MS16-051), which also addresses the vulnerabilities discussed in this bulletin.