LiveActive security incident?Get immediate response
CVE Record

CVE-2020-1570: 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-1570 is a Microsoft Internet Explorer scripting engine memory corruption flaw. A malicious website or hosted content could let an attacker run code as the logged-in user. If that user has administrator rights, the attacker could take over the system.

Executive priority

Treat this as a prompt legacy-browser patch and exposure-reduction item. There is no source evidence of active exploitation, but the impact is serious because successful exploitation can execute code and potentially take over admin sessions.

Technical view

The vulnerability is remote code execution caused by incorrect object handling in Internet Explorer scripting engine memory. Microsoft lists Internet Explorer 9 and 11 as affected. The security update changes how the scripting engine handles objects in memory.

Likely exposure

Exposure is most likely in environments that still use Internet Explorer 9 or 11, or applications and Office documents that host the IE rendering engine. The provided data does not include a full platform matrix.

Exploitation context

The source describes web-based exploitation requiring specially crafted content and user interaction. It also notes ActiveX content in applications or Office documents hosting IE rendering. The bundle marks KEV as false and provides no active exploitation evidence.

Researcher notes

Evidence is limited to Microsoft/CVE source data. CVSS, CWE, exact platform applicability, and exploit maturity are not provided in the bundle. Avoid assuming broader product impact beyond Internet Explorer 9 and 11 and IE-rendering-engine hosting scenarios described by Microsoft.

Mitigation direction

  • Apply the Microsoft security update for CVE-2020-1570.
  • Check MSRC guidance for exact affected platforms and update packages.
  • Reduce or retire Internet Explorer 9 and 11 usage where possible.
  • Review exposure from applications or documents hosting the IE rendering engine.
  • Limit administrative user rights on systems that may encounter web content.

Validation and detection

  • Inventory endpoints with Internet Explorer 9 or 11 present or enabled.
  • Verify CVE-2020-1570 patch status against Microsoft guidance.
  • Identify business apps or Office workflows using the IE rendering engine.
  • Confirm high-risk users are not routinely browsing as local administrators.
  • Review web-content handling controls for legacy browser paths.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-1570 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftInternet Explorer 111.0.0Listed
MicrosoftInternet Explorer 91.0.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.