CVE-2020-17144 kev in the critical feed json
Microsoft Exchange Remote Code Execution Vulnerability
published 2020-12-09 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-9098
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Exploited
- added 2021-11-03
- epss
- 36.5%
- EPSS 36.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Microsoft Exchange Remote Code Execution Vulnerability
Patch / fix
cisa required action Apply updates per vendor instructions.
Timeline
- Published
- Added to CISA KEV
- CISA patch deadline
- CISA SSVC: exploitation active
Known exploited
- Added
- 5 y ago
- Patch by
- 2022-05-03 (4 y ago)
- Ransomware
- Not known
- Required action
- Apply updates per vendor instructions.
- Vendor, product
- Microsoft, Exchange Server
- CISA name
- Microsoft Exchange Server Remote Code Execution Vulnerability
CISA SSVC
- Exploitation
- Active, exploited in the wild
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
36.51% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.4 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C |
| CNA | 3.1 | 8.4 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H |
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.0 | AV:N/AC:M/Au:S/C:P/I:P/A:P |
Affected products
- Microsoft Microsoft Exchange Server 2010 Service Pack 3 Update Rollup 31
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
- Technology feeds
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2020-17144
vendor-advisory, patch
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2020-17144
patch, vendor-advisory
-
cisa.gov
/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-17144
government-resource, us-government-resource
Sources
- CVE List CVE-2020-17144
- NVD CVE-2020-17144
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.