Описание
Scripting Engine Memory Corruption Vulnerability
A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer. The vulnerability 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 vulnerability 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 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.
In a web-based attack scenario, an attacker could host a specially crafted website that is designed to exploit the vulnerability through Internet Explorer and then convince a user to view the website. 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 the vulnerability.
The security update addresses the vulnerability by modifying how the scripting engine handles objects in memory.
Меры по смягчению последствий
By default, Internet Explorer on Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 and Windows Server 2019 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.
Обходное решение
Impact of Workaround
Please note: Implementing these steps might result in reduced functionality for components or features that rely on jscript.dll. For example, depending on the environment, this could include client configurations that leverage proxy automatic configuration scripts (PAC scripts). These features and others may be impacted.
Microsoft recommends these mitigation steps only if there is indication that you are under elevated risk. If you implement the workaround, you will need to revert the mitigation steps before installing any future updates to continue to be protected.
By default, IE11, IE10, and IE9 uses Jscript9.dll which is not impacted by this vulnerability. This vulnerability only affects certain websites that utilize jscript as the scripting engine.
Restrict access to 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:
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
I applied the workaround to restrict access to JScript.dll as described in ADV200001. Do I need to undo the workaround before I apply the February security update?
Yes. Customers who applied the workaround need to undo it before applying the updates to address this vulnerability.
How do I undo the workaround?
See "How to undo the workaround" in the Workaround section of this Security Vulnerability.
Обновления
| Продукт | Статья | Обновление |
|---|---|---|
| Internet Explorer 10 on Windows Server 2012 | ||
| Internet Explorer 11 on Windows Server 2012 | ||
| Internet Explorer 11 on Windows 7 for x64-based Systems Service Pack 1 | ||
| Internet Explorer 11 on Windows 8.1 for 32-bit systems | ||
| Internet Explorer 11 on Windows 8.1 for x64-based systems | ||
| Internet Explorer 11 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 | ||
| Internet Explorer 11 on Windows Server 2012 R2 | ||
| Internet Explorer 9 on Windows Server 2008 for x64-based Systems Service Pack 2 | ||
| Internet Explorer 9 on Windows Server 2008 for 32-bit Systems Service Pack 2 | ||
| Internet Explorer 11 on Windows 10 Version 1803 for 32-bit Systems |
Показывать по
Возможность эксплуатации
Publicly Disclosed
Exploited
Latest Software Release
Older Software Release
DOS
EPSS
6.4 Medium
CVSS3
Связанные уязвимости
A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0673, CVE-2020-0710, CVE-2020-0711, CVE-2020-0712, CVE-2020-0713, CVE-2020-0767.
A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2020-0673, CVE-2020-0710, CVE-2020-0711, CVE-2020-0712, CVE-2020-0713, CVE-2020-0767.
Уязвимость обработчика сценариев браузера Internet Explorer, позволяющая нарушителю выполнить произвольный код
Microsoft Guidance on Scripting Engine Memory Corruption Vulnerability
EPSS
6.4 Medium
CVSS3