Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2021-24085: Microsoft Exchange Server Spoofing Vulnerability

Published Feb 25, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS4.6%92nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2021-24085CWE-20

CVE-2021-24085 is a spoofing vulnerability in Microsoft Exchange Server. Publicly available context identifies the issue by Microsoft’s title and indicates vendor and network detection coverage, but does not provide technical detail about the vulnerable component, code path, protocol element, or the precise spoofing mechanism. The available information is therefore insufficient to accurately describe the vulnerable function or exploitation workflow beyond its classification as an Exchange Server spoofing issue.

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 would allow an attacker to spoof trusted content, identity, or communication context within Microsoft Exchange Server. The specific downstream security consequences are not described in the available information, so the exact effect on confidentiality, integrity, or availability cannot be stated with confidence.

Mitigation

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

If immediate patching is not possible, reduce exposure of Exchange services to untrusted networks where feasible, increase monitoring for exploitation attempts using available network and host detections, and perform threat hunting on exposed Exchange systems. Mitigation details specific to CVE-2021-24085 are not available in the provided information, so patching remains the primary corrective action.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update released for CVE-2021-24085 on supported Microsoft Exchange Server versions. Because the available information does not include product-version-specific guidance, administrators should follow Microsoft’s official bulletin and cumulative update requirements for the affected Exchange release.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2021-24085This repository provides a multi-stage proof-of-concept exploit for CVE-2021-24085, a Cross Site Request Forgery (CSRF) Elevation of Privilege vulnerability in Microsoft Exchange Server. The exploit consists of three main components: 1. `poc.py` (Python): Authenticates to the Exchange OWA interface using provided credentials, locates the Exchange Auth Certificate, exports it (including the private key) to the server's filesystem, and downloads it to the attacker's machine. This step requires valid credentials and sufficient privileges. 2. `YellowCanary/Poc/Program.cs` (C#): A console application that, given a user SID, the exported certificate, and its password, generates a valid msExchEcpCanary CSRF token for the target user. This token is required to perform privileged actions via the Exchange Control Panel (ECP). 3. `poc.js` (JavaScript): A browser-based CSRF exploit that, using the generated token, uploads a malicious Office add-in manifest file to the Exchange server via a POST request to the UploadHandler endpoint. This can result in privilege escalation or account takeover if a privileged user visits the attacker's page. The repository is structured with a Visual Studio C# project for the token generator, standalone Python and JavaScript proof-of-concept scripts, and supporting documentation. The exploit demonstrates a full attack chain from credentialed access to privilege escalation via CSRF token forgery and malicious file upload. Multiple network endpoints and file paths are fingerprintable, including Exchange OWA and ECP URLs, and the location of the exported certificate.sourceincite · Disclosed Feb 15, 2021 · python · csharp · network · browserPoC
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-2021-24085 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2021-24085 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2021-24085?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2021-24085, the earliest disclosed Feb 15, 2021.
Is there a patch for CVE-2021-24085?
Apply the Microsoft security update released for CVE-2021-24085 on supported Microsoft Exchange Server versions. Because the available information does not include product-version-specific guidance, administrators should follow Microsoft’s official bulletin and cumulative update requirements for the affected Exchange release.
What products are affected by CVE-2021-24085?
Microsoft Corporation Exchange Server.
How severe is CVE-2021-24085?
CVE-2021-24085 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 4.6% (92nd percentile) as of Oct 16, 2026.
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 activityCommunity discussion across Reddit, Mastodon, and other social sources.