Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Internet Explorer Scripting Engine Memory Corruption RCE

IdentifiersCVE-2020-0968CWE-787· Out-of-bounds Write

CVE-2020-0968 is a remote code execution vulnerability in the Internet Explorer scripting engine caused by improper handling of objects in memory. Microsoft describes it as a scripting engine memory corruption vulnerability. The issue can be triggered when Internet Explorer processes malicious content that causes memory corruption in the scripting engine, leading to attacker-controlled code execution in the context of the current user. Supporting content also places this flaw in the broader class of Internet Explorer/JScript memory corruption issues that were exploited in the wild in 2020, including delivery via malicious RTF content that retrieved an HTML page exploiting the vulnerability.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow remote code execution on the target system in the security context of the current user. This can enable full compromise of the affected browser process and, depending on user privileges, installation of malware, data theft, persistence, and further post-compromise activity. The content also notes that the vulnerability was exploited in the wild, including use by espionage operators to deliver follow-on malware.

Mitigation

If you can’t patch tonight, do this now.

Until patching is complete, reduce exposure by disabling or restricting Internet Explorer use, especially legacy or unnecessary browser invocation paths. Limit opening of untrusted RTF, HTML, and web content delivered via email or downloaded from the internet. Use least-privilege user accounts to reduce post-exploitation impact. Standard exploit mitigations such as DEP/NX and ASLR may reduce exploit reliability but are not substitutes for patching.

Remediation

Patch, then assume compromise.

Apply Microsoft's April 2020 security update that patches CVE-2020-0968. Ensure Internet Explorer and the underlying scripting engine components are fully updated across all supported systems. Because the vulnerability was exploited in the wild, patching should be prioritized on systems where Internet Explorer or IE-based rendering paths remain present or reachable.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationInternet Explorerapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence2

Every observed campaign linking this CVE to a named adversary.

Associated malware1

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.