CVE-2020-0674: Scripting Engine Memory Corruption Vulnerability

Overview

Severity
Medium (CVSS 6.4)
CVSS Vector
CVSS:3.0/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
Category
Remote Code Execution
Exploit Status
Actively Exploited
Exploitation Likelihood
Detected
Publicly Disclosed
Yes
Patch Tuesday
2020-Feb
Released
2020-02-11
Last Updated
2020-02-12
EPSS Score
93.64% (percentile: 99.8%)
CISA KEV
Listed — due 2022-05-03

Description

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.

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.

Known Exploits (3)

  • Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability — added 2023-12-10T11:52:48Z
  • Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability — added 2020-09-30T08:08:42Z
  • Microsoft Internet Explorer Scripting Engine Memory Corruption Vulnerability — added 2020-05-07T22:02:25Z

Detection & Weaponization (1 sources)

Maturity: Exploit

  • GitHub PoC: 4 repositories

Affected Products (32)

Browser

  • Internet Explorer 10 on Windows Server 2012
  • Internet Explorer 11 on Windows 10 Version 1803 for 32-bit Systems
  • Internet Explorer 11 on Windows 10 Version 1803 for x64-based Systems
  • Internet Explorer 11 on Windows 10 Version 1803 for ARM64-based Systems
  • Internet Explorer 11 on Windows 10 Version 1809 for 32-bit Systems
  • Internet Explorer 11 on Windows 10 Version 1809 for x64-based Systems
  • Internet Explorer 11 on Windows 10 Version 1809 for ARM64-based Systems
  • Internet Explorer 11 on Windows Server 2019
  • Internet Explorer 11 on Windows 10 Version 1909 for 32-bit Systems
  • Internet Explorer 11 on Windows 10 Version 1909 for x64-based Systems
  • Internet Explorer 11 on Windows 10 Version 1909 for ARM64-based Systems
  • Internet Explorer 11 on Windows 10 Version 1709 for 32-bit Systems
  • Internet Explorer 11 on Windows 10 Version 1709 for x64-based Systems
  • Internet Explorer 11 on Windows 10 Version 1709 for ARM64-based Systems
  • Internet Explorer 11 on Windows 10 Version 1903 for 32-bit Systems
  • Internet Explorer 11 on Windows 10 Version 1903 for x64-based Systems
  • Internet Explorer 11 on Windows 10 Version 1903 for ARM64-based Systems
  • Internet Explorer 11 on Windows 10 for 32-bit Systems
  • Internet Explorer 11 on Windows 10 for x64-based Systems
  • Internet Explorer 11 on Windows 10 Version 1607 for 32-bit Systems
  • Internet Explorer 11 on Windows 10 Version 1607 for x64-based Systems
  • Internet Explorer 11 on Windows Server 2016
  • Internet Explorer 11 on Windows 7 for 32-bit Systems Service Pack 1
  • 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 RT 8.1
  • Internet Explorer 11 on Windows Server 2008 R2 for x64-based Systems Service Pack 1
  • Internet Explorer 11 on Windows Server 2012
  • Internet Explorer 11 on Windows Server 2012 R2

ESU

  • 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

Security Updates (11)

Acknowledgments

Yi Huang(@C0rk1_H) & Kang Yang(@dnpushme) of Qihoo 360 ATA, Clément Lecigne of Google’s Threat Analysis Group

Revision History

  • 2020-02-11: Information published.
  • 2020-02-11: Added FAQ to explain that if customers applied the workaround to restrict access to JScript.dll, it must be undone before installing the updates for this vulnerability. This is an informational change only.
  • 2020-02-12: Added the applicable mitigation and workaround to provide consistency with ADV200001, which CVE-2020-9674 addresses. Customers should only apply the workaround if they are unable to install the February security updates. This is an informational change only.