CVE-2020-17144 — Exchange Server
HIGHCVE-2020-17144 is a high-severity (CVSS 8.4) Deserialization of Untrusted Data vulnerability in microsoft exchange server. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.
Microsoft Exchange Remote Code Execution Vulnerability
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03. Federal agencies were required to remediate by 2022-05-03.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2020-17144.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-17144 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Description
Microsoft Exchange Remote Code Execution Vulnerability
Affected Products
exchange servermicrosoftResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Vendor / applianceDetect
Inventory every microsoft exchange server deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2020-17144 yet — track the microsoft exchange server advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2020-17144 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.