Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2020-17144: Authenticated Deserialization RCE in Microsoft Exchange 2010

Published Dec 9, 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.
CVSS8.8High · v3.1
EPSS36.5%99th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2020-17144CWE-502 · Deserialization of Untrusted Data

CVE-2020-17144 is a post-authentication deserialization vulnerability in Microsoft Exchange 2010 that permits remote code execution on a vulnerable server. Exploitation requires a valid login. APT28 has exploited the vulnerability against exposed Exchange servers, including through Outlook Web Access. The vulnerable function and precise serialized input format are currently not available.

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 permits remote code execution on the affected Exchange server. Observed attacks have used the vulnerability to escalate privileges and help establish persistent access. The precise execution identity and scope of privileges obtained are currently not available.

Mitigation

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

Harden authentication with multifactor authentication where supported, strong unique passwords, and account lockout controls. Apply least privilege, network segmentation, centralized logging, and endpoint detection to reduce credential abuse and detect exploitation or subsequent activity. These controls do not replace remediation of the deserialization vulnerability.

Remediation

Patch, then assume compromise.

Apply Microsoft security updates addressing CVE-2020-17144, prioritizing exposed Exchange servers. The exact update identifier and fixed build are currently not available.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
CVE-2020-17144-EXPThis repository is a C# exploit for CVE-2020-17144, targeting Microsoft Exchange Server 2010. The exploit leverages a deserialization vulnerability in Exchange Web Services (EWS) to write a webshell to the server's autodiscover directory, specifically at 'C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\autodiscover\Services.aspx'. The main entry point is 'Program.cs', which takes three arguments: the target Exchange server's domain, a username, and a password. The exploit uses the ysoserial.net gadget chain to generate a malicious serialized payload, which is then uploaded to the server via the EWS API. The default payload writes a simple webshell, but the code can be modified to execute arbitrary commands. The repository includes all necessary code to generate the payload and interact with the Exchange server, and references the Exchange Web Services Managed API. The README provides usage instructions and notes that the exploit requires valid user credentials and an Exchange 2010 environment.Airboi · Disclosed Dec 9, 2020 · csharp · xml · networkOperationalCVE-2020-17144This repository contains a weaponized exploit for CVE-2020-17144, a deserialization vulnerability in Microsoft Exchange 2010's MRM.AutoTag.Model. The main exploit file (CVE-2020-17144.cs) authenticates to the Exchange Web Services endpoint using provided credentials and uploads a malicious configuration containing a serialized payload (compiled from e.cs as e.dll). The payload, when deserialized by Exchange, starts an HTTP listener on port 80 at /ews/soap/. This backdoor allows an attacker to execute arbitrary system commands by sending HTTP requests with a specific query parameter (e.g., http://[target]/ews/soap/?pass=whoami). The repository includes a batch file (make.bat) for building the exploit and payload DLL. The exploit requires valid Exchange credentials and targets Exchange 2010 servers vulnerable to CVE-2020-17144. The structure is straightforward: CVE-2020-17144.cs (exploit logic), e.cs (payload/backdoor), make.bat (build script), and README.md (usage instructions).zcgonvh · Disclosed Dec 9, 2020 · csharp · batch · networkOperational
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 CorporationExchange Serverapplication
FAQ

Frequently asked questions

Is CVE-2020-17144 exploited in the wild?
Yes. As of Oct 10, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2020-17144?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2020-17144, the earliest disclosed Dec 9, 2020.
Is there a patch for CVE-2020-17144?
Apply Microsoft security updates addressing CVE-2020-17144, prioritizing exposed Exchange servers. The exact update identifier and fixed build are currently not available.
What products are affected by CVE-2020-17144?
Microsoft Corporation Exchange Server.
How severe is CVE-2020-17144?
CVE-2020-17144 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 36.5% (99th percentile) as of Oct 10, 2026.
Activity feed

Recent activity

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

View more in app →
+8 more in the timeline. Sign up to see them
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 evidence9Every report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.