ProxyLogon (CVE-2021-26855): when on-premises Exchange servers were hacked en masse

A chain of Exchange Server flaws let attackers take over mail servers without a password. Lessons for anyone still running Exchange on-premises.

Publicly disclosed: 2 March 2021

On 2 March 2021 Microsoft released emergency updates for Exchange Server: a chain of four vulnerabilities, later called ProxyLogon, allowed attackers to bypass authentication and run code on the server. Exploitation had already started before the patch, and after publication many groups scanned the internet for unpatched servers and installed web shells.

CVESeverityAffectedFixed in
CVE-2021-26855Critical, CVSS 9.1 (SSRF, authentication bypass)Exchange Server 2013, 2016, 2019Security updates of March 2021
CVE-2021-26857, -26858, -27065High (code execution, file write)Exchange Server 2013, 2016, 2019Security updates of March 2021

Lessons learned

Many servers were compromised in the days between disclosure and patching. Installing the update did not remove web shells already planted by attackers, so patched servers could still be under control of intruders.

How to protect Exchange today

  1. Run only supported Exchange versions and install every Security Update and Cumulative Update promptly.
  2. Do not publish Outlook Web Access and ECP to the internet without a reverse proxy, WAF or VPN where possible.
  3. After any critical Exchange vulnerability, check for compromise: unknown .aspx files, new accounts, mailbox export requests.
  4. Enable Microsoft's Exchange Emergency Mitigation service and AMSI integration.
  5. Consider moving email to a managed cloud service if you cannot patch quickly.

Patching closes the door. Checking for compromise finds out who already came in.

Sources: Microsoft Security Blog, NVD CVE-2021-26855.

Need help with this? Contact CySec for a free consultation.


All articles

Need help with this?

Our engineers can review your current setup and propose concrete improvements.