Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2020-1066: .NET Framework COM Object Activation Elevation of Privilege

Published May 21, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS2.5%85th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2020-1066CWE-269

CVE-2020-1066 is a local elevation of privilege vulnerability in Microsoft .NET Framework caused by improper handling of COM object activation. An attacker who has already obtained access to a target system can exploit the flaw by executing a malicious program locally. Successful exploitation allows the attacker to elevate privileges beyond those initially granted. The issue is addressed by correcting how .NET Framework activates COM objects.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows a local attacker to elevate privileges on the affected Windows system. This can enable execution of code with higher integrity or administrative context than the attacker originally possessed, facilitating follow-on actions such as disabling defenses, accessing protected resources, installing additional malware, or moving toward full system compromise.

Mitigation

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

No specific workaround is available from the provided information. Risk can be reduced by limiting local access to systems, preventing execution of untrusted code, enforcing least privilege, and promptly applying the relevant Microsoft security updates for .NET Framework.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update for .NET Framework that fixes the COM object activation flaw underlying CVE-2020-1066. Ensure all affected .NET Framework installations on supported Windows systems are updated to the vendor-provided patched versions through normal security update channels.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2020-1066-EXPThis repository contains a full exploit for CVE-2020-1066, a local privilege escalation vulnerability in Microsoft Windows 7 and Windows Server 2008 R2. The vulnerability exists in the Windows CardSpace (idsvc) service, which runs as SYSTEM and exposes an RPC interface. The exploit abuses improper handling of symbolic links and hardlinks by the service when moving files in the user's %APPDATA% directory, allowing a local attacker to replace arbitrary files with SYSTEM privileges. The repository is structured as a Visual Studio solution with three main components: - CommonUtils: Utility library for file, symlink, hardlink, and registry manipulation, as well as privilege management. - MyComDefine: Contains the MIDL-generated RPC interface definitions and stubs for communicating with the CardSpace service. - MyComEop: The main exploit executable, which orchestrates the attack by creating symlinks, hardlinks, and mount points, and then triggering the vulnerable CardSpace RPC operations to replace target files and escalate privileges. The exploit is highly configurable, allowing the user to specify which file to replace (default is System.EnterpriseServices.tlb), which COM interface or TypeLib to target, and even to execute arbitrary commands as SYSTEM. The README provides detailed background, usage instructions, and references to related projects and the official CVE advisory. The attack vector is local, requiring code execution as a regular user, but does not require administrator privileges. The exploit demonstrates advanced file system manipulation techniques and direct interaction with Windows RPC and COM subsystems.cbwang505 · Disclosed Jun 1, 2020 · c++ · idl · localOperational
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 Corporation.Net Frameworkapplication
FAQ

Frequently asked questions

Is CVE-2020-1066 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-1066?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2020-1066, the earliest disclosed Jun 1, 2020.
Is there a patch for CVE-2020-1066?
Apply the Microsoft security update for .NET Framework that fixes the COM object activation flaw underlying CVE-2020-1066. Ensure all affected .NET Framework installations on supported Windows systems are updated to the vendor-provided patched versions through normal security update channels.
What products are affected by CVE-2020-1066?
Microsoft Corporation .Net Framework.
How severe is CVE-2020-1066?
CVE-2020-1066 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 2.5% (85th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.