CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HHigh (7.8) in Microsoft Exchange Server. In CISA KEV since 2021-11-03, with known ransomware use. EPSS 99.8% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExplain CVE-2021-27065 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-27065?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-27065?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-27065 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Microsoft Exchange Server 2013 Cumulative Update 21 | from 15.00.0 before 15.00.1395.012 |
| Microsoft Exchange Server 2013 Cumulative Update 22 | from 15.00.0 before 15.00.1473.006 |
| Microsoft Exchange Server 2013 Cumulative Update 23 | from 15.00.0 before 15.00.1497.012 |
| Microsoft Exchange Server 2013 Service Pack 1 | from 15.00.0 before 15.00.0847.064 |
| Microsoft Exchange Server 2016 Cumulative Update 10 | from 15.01.0 before 15.01.1531.012 |
| Microsoft Exchange Server 2016 Cumulative Update 11 | from 15.01.0 before 15.01.1591.018 |
| Microsoft Exchange Server 2016 Cumulative Update 12 | from 15.01.0 before 15.01.1713.010 |
| Microsoft Exchange Server 2016 Cumulative Update 13 | from 15.01.0 before 15.01.1779.008 |
| Microsoft Exchange Server 2016 Cumulative Update 14 | from 15.01.0 before 15.01.1847.012 |
| Microsoft Exchange Server 2016 Cumulative Update 15 | from 15.01.0 before 15.01.1913.012 |
| Microsoft Exchange Server 2016 Cumulative Update 16 | from 15.01.0 before 15.01.1979.008 |
| Microsoft Exchange Server 2016 Cumulative Update 17 | from 15.01.0 before 15.01.2044.013 |
| Microsoft Exchange Server 2016 Cumulative Update 18 | from 15.01.0 before 15.01.2106.013 |
| Microsoft Exchange Server 2016 Cumulative Update 19 | from 15.01.0 before 15.01.2176.009 |
| Microsoft Exchange Server 2016 Cumulative Update 8 | from 15.01.0 before 15.01.1415.010 |
| Microsoft Exchange Server 2016 Cumulative Update 9 | from 15.01.0 before 15.01.1466.016 |
| Microsoft Exchange Server 2019 | from 15.02.0 before 15.02.0221.018 |
| Microsoft Exchange Server 2019 Cumulative Update 1 | from 15.02.0 before 15.01.1979.006 |
| Microsoft Exchange Server 2019 Cumulative Update 2 | from 15.02.0 before 15.02.0397.011 |
| Microsoft Exchange Server 2019 Cumulative Update 3 | from 15.02.0 before 15.02.0464.015 |
| Microsoft Exchange Server 2019 Cumulative Update 4 | from 15.02.0 before 15.02.0659.012 |
| Microsoft Exchange Server 2019 Cumulative Update 5 | from 15.02.0 before 15.02.0595.008 |
| Microsoft Exchange Server 2019 Cumulative Update 6 | from 15.02.0 before 15.02.0529.013 |
| Microsoft Exchange Server 2019 Cumulative Update 7 | from 15.02.0 before 15.02.0721.013 |
| Microsoft Exchange Server 2019 Cumulative Update 8 | from 15.02.0 before 15.02.0792.010 |
Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.