Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are Exchange Server Exploit Chains?

ProxyLogon, ProxyShell, and ProxyNotShell each combined a server-side request forgery with a second flaw to turn an anonymous request to a mail server into code execution as SYSTEM.

Illustration for the cybersecurity term Exchange Server Exploit Chains
Home / Blog / Cybersecurity Terms / What Are Exchange Server Exploit Chains?
17 November 2026

What Are Exchange Server Exploit Chains?

What Are Exchange Server Exploit Chains?

Between 2021 and 2023 Microsoft Exchange Server was the single most exploited on-premises product in the world. The vulnerabilities were not isolated: they arrived as chains, in which a server-side request forgery provided authentication as the Exchange server itself, and a second flaw then converted that access into arbitrary code execution. The naming convention — ProxyLogon, ProxyShell, ProxyNotShell, ProxyToken, OWASSRF — reflects a shared root cause rather than a marketing habit.

Why the Architecture Invited It

Exchange has a front end, the Client Access Service, which proxies requests to back-end services on the same or another server. To do so it authenticates to the back end using its own machine account, which holds extensive privileges in Active Directory. If an attacker can persuade the front end to forward a request of their choosing, that request arrives at the back end already authenticated as a highly privileged identity.

Add to this a very large attack surface — Autodiscover, Exchange Web Services, Outlook Web Access, PowerShell remoting, ActiveSync — and a deserialisation-heavy .NET codebase, and the pattern follows naturally.

The Major Chains

What Attackers Did With Access

Compromise of Exchange is rarely about the mail alone. The Exchange server account has rights in Active Directory, the server sits inside the network perimeter, and it holds everybody’s correspondence. Typical follow-on activity included dropping web shells for persistence, dumping LSASS to harvest credentials, running DCSync against domain controllers, exporting mailboxes wholesale, and deploying ransomware. Several ransomware families, including Conti and BlackCat affiliates, used ProxyShell as an initial access route throughout 2021 and 2022.

Patching Was Repeatedly Insufficient

Two lessons recur across all three chains. First, exploitation frequently preceded disclosure, so patching on the day of release did not guarantee a clean server; organisations had to hunt for web shells and other persistence that was already present. Second, Exchange cumulative updates are large, infrequent, and often deferred, and partial mitigations were bypassed. Microsoft’s Exchange Server Health Checker and the Exchange On-premises Mitigation Tool exist precisely because so many servers were running builds months or years behind.

The Position Today

Exchange Server 2016 and 2019 reached end of support on 14 October 2025, succeeded by Exchange Server Subscription Edition. Any organisation still running on-premises Exchange needs a clear answer to three questions: is the build current, is Extended Protection enabled, and is the server reachable from the internet at all.

For most organisations the honest strategic answer is to move mail to a hosted service, which removes this class of vulnerability from your responsibility. Where on-premises Exchange must remain — and there are legitimate reasons — treat it as a Tier 0 asset: emergency patching, no direct internet exposure for management paths, endpoint detection installed on the server, Active Directory permissions reviewed, and regular hunting for web shells in the virtual directories.

Our infrastructure security testing services cover Exchange build verification, exposure review, and compromise assessment together, because patch status alone has never answered the question.

FAQ – Frequently Asked Questions

What Is the Difference Between ProxyLogon and ProxyShell?

Both are chains ending in code execution on Exchange, but they use different vulnerabilities and were patched at different times. ProxyLogon was disclosed in March 2021 and chained a pre-authentication request forgery with an arbitrary file write. ProxyShell used three separate flaws patched in April and May 2021, with mass exploitation following the public technical details in August.

Does Patching Exchange Remove a Web Shell?

No. Patching closes the vulnerability used to install it, but an existing web shell remains on disk and continues to work. After each of these chains, organisations had to search the Exchange virtual directories for unexpected ASPX files, review IIS logs, and investigate further persistence. Assume compromise if your server was exposed and unpatched during an exploitation window.

Is On-Premises Exchange Still Viable?

It can be, but it demands discipline: current cumulative updates applied promptly, Extended Protection for Authentication enabled, no unnecessary internet exposure, endpoint detection on the server, and regular compromise assessment. Exchange 2016 and 2019 reached end of support in October 2025, so anyone remaining on-premises needs a plan for Subscription Edition or a move to a hosted service.

Why Is Exchange Such a Valuable Target?

It sits inside the network, holds the organisation’s correspondence, and its machine account carries substantial Active Directory privileges. Compromise therefore yields intelligence, credentials, and a path to domain compromise in one step. Add an internet-facing attack surface and a complex proxying architecture, and it becomes one of the highest-value targets in a typical estate.

Related Terms

You May Be Interested In These

What Is KVKK Data Breach Notification?

Cybersecurity Terms

17 November 2026

What Is KVKK Data Breach Notification?

Read More
What Is DNS Cache Poisoning?

Cybersecurity Terms

17 November 2026

What Is DNS Cache Poisoning?

Read More
What Are WPS Vulnerabilities?

Cybersecurity Terms

17 November 2026

What Are WPS Vulnerabilities?

Read More