# CVE-2020-0674: Microsoft Internet Explorer Scripting Engine Memory Corruption

> Remote attackers can execute arbitrary code via a use-after-free vulnerability in the Internet Explorer scripting engine.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Feb 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-35jh-2r79-5r66

## What is CVE-2020-0674?

CVE-2020-0674 is a high-severity use after free vulnerability in Microsoft Internet Explorer, published on 11 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Microsoft Internet Explorer.

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

No fix has been published for CVE-2020-0674 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-0674 being exploited?

Yes. Attackers have exploited CVE-2020-0674 in the wild since at least 3 Nov 2021.

Public exploit code:

- This is an exploit for CVE-2020-0674 that runs on the x64 version of IE 8, 9, 10, and 11 on Windows 7. (github_poc): https://github.com/maxpl0it/CVE-2020-0674-Exploit
- 随便放点自己弄的小东西 (github_poc): https://github.com/Neko-chanQwQ/CVE-2020-0674-PoC
- https://github.com/Ken-Abruzzi/CVE-2020-0674 (github_poc): https://github.com/Ken-Abruzzi/CVE-2020-0674
- Microsoft Internet Explorer 11 - Use-After-Free (exploitdb)
- Microsoft Internet Explorer 11 and WPAD service 'Jscript.dll' - Use-After-Free (exploitdb)
- Porting the CVE-2020-0674 exploit for Windows8.1 and Windows10 (github_poc): https://github.com/Micky-Thongam/Internet-Explorer-UAF

## Other vulnerabilities in Microsoft Internet Explorer

- [CVE-2014-1776](https://insights.sbomify.com/CVE-2014-1776/): Microsoft Internet Explorer Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2021-27085](https://insights.sbomify.com/CVE-2021-27085/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0222](https://insights.sbomify.com/CVE-2017-0222/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0210](https://insights.sbomify.com/CVE-2017-0210/): Microsoft Internet Explorer Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2017-0149](https://insights.sbomify.com/CVE-2017-0149/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-0674 is a high-severity use after free vulnerability in Microsoft Internet Explorer, published on 11 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2020-0674 in the wild since at least 3 Nov 2021.

Affected product: Microsoft Internet Explorer. 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-0674/ (Markdown: https://insights.sbomify.com/CVE-2020-0674/index.md)
```

## Sources

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

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