# CVE-2020-1569: Microsoft Edge Memory Corruption Vulnerability

> Remote code execution via memory corruption in Microsoft Edge allows attackers to gain user rights by tricking users into visiting malicious websites.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x3v3-356g-f4j9

## What is CVE-2020-1569?

CVE-2020-1569 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 17 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A remote code execution vulnerability exists when Microsoft Edge improperly accesses objects in memory. The vulnerability could corrupt memory in such a way that enables 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, an 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.
An attacker could host a specially crafted website that is designed to exploit the vulnerability through Microsoft Edge, and then convince a user to view the website. The attacker could also take advantage of compromised websites and 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 by way of enticement in an email or Instant Messenger message, or by getting them to open an attachment sent through email.
The security update addresses the vulnerability by modifying how Microsoft Edge handles objects in memory.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2020-1569?

It affects 1 product.


Products: Microsoft Edge.

## How do I fix CVE-2020-1569?

No fix has been published for CVE-2020-1569 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-1569 being exploited?

There is no known exploitation of CVE-2020-1569 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Edge

- [CVE-2021-26411](https://insights.sbomify.com/CVE-2021-26411/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7200](https://insights.sbomify.com/CVE-2016-7200/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7201](https://insights.sbomify.com/CVE-2016-7201/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2017-0037](https://insights.sbomify.com/CVE-2017-0037/): Microsoft Edge and Internet Explorer Type Confusion (high 8.1, exploited in the wild)
- [CVE-2016-3351](https://insights.sbomify.com/CVE-2016-3351/): Microsoft Internet Explorer and Edge Information Disclosure (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1569 and fix it if it is affected.

What it is: CVE-2020-1569 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 17 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1569 in the wild and no public exploit code.

Affected product: Microsoft Edge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1569/ (Markdown: https://insights.sbomify.com/CVE-2020-1569/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1569
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1569
- OSV: https://osv.dev/vulnerability/CVE-2020-1569

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1569/
Summaries are generated and may contain mistakes; the official description above is the record.