CVE-2020-0878

Microsoft Browser Memory Corruption Vulnerability

MEDIUM
4.2
CVSS Score
Published: September 11, 2020 at 05:08 PM UTC
Updated: June 17, 2026 at 02:46 AM UTC
19 products affected across 1 vendorInternet ExplorerEdgeChakraCore

Using ChakraCore by Microsoft?

Get instant alerts when new vulnerabilities affect ChakraCore - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.2
Exploitation
CISA KEV
Exploit prediction
EPSS 3%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score2.7%

EPSS (Exploit Prediction Scoring System) estimates a 2.7% chance this CVE is exploited in the wild within the next 30 days — higher than 86% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Edge and Internet Explorer contain a memory corruption vulnerability that allows attackers to execute code in the context of the current user.

Required Action
Apply updates per vendor instructions.
Ransomware Use
Known
Added to KEV
Nov 3, 2021
Remediation Due
May 3, 2022
1637 days overdue

Description

<p>A remote code execution vulnerability exists in the way that Microsoft browsers access objects in memory. The vulnerability could corrupt memory in a way that could allow an attacker to 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, 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.</p> <p>An attacker could host a specially crafted website that is designed to exploit the vulnerability 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 the vulnerability. 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 via an enticement in email or instant message, or by getting them to open an email attachment.</p> <p>The security update addresses the vulnerability by modifying how Microsoft browsers handle objects in memory.</p>

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < publication
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
1.0..0 ≤ v < publication1.0..0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
microsoft-windows-10-1507 (environment) · microsoft-windows-10-1607 (environment) · microsoft-windows-10-1709 (environment) · microsoft-windows-10-1803 (environment) · microsoft-windows-10-1809 (environment) · microsoft-windows-10-1903 (environment) · microsoft-windows-10-1909 (environment) · microsoft-windows-10-2004 (environment) · microsoft-windows-server-2016 (environment) · microsoft-windows-server-2019 (environment)
1.0.0 ≤ v < publication1.0.0119
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
microsoft-windows-10-1507 (environment) · microsoft-windows-10-1607 (environment) · microsoft-windows-10-1709 (environment) · microsoft-windows-10-1803 (environment) · microsoft-windows-10-1809 (environment) · microsoft-windows-10-1903 (environment) · microsoft-windows-10-1909 (environment) · microsoft-windows-10-2004 (environment) · microsoft-windows-7 (environment) · microsoft-windows-8-1 (environment) · microsoft-windows-rt-8-1 (environment) · microsoft-windows-server-2008 (environment) · microsoft-windows-server-2012 (environment) · microsoft-windows-server-2016 (environment) · microsoft-windows-server-2019 (environment)
All versions
All versions
All versions
All versions
All versions
All versions
All versions

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

SSVC — Action Prioritization

SSVCActiveNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.2MEDIUMmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card