Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
ProxyShell is a three-vulnerability chain against on-premises Exchange that was patched quietly in spring 2021, then exploited at scale once the technical details were presented in August.

What Is ProxyShell?
ProxyShell is a chain of three vulnerabilities in on-premises Microsoft Exchange Server that, combined, give an unauthenticated attacker the ability to write files to the server and execute code. What makes it instructive is the timeline: Microsoft patched all three during April and May 2021, but the advisories carried little detail, many organisations did not apply them, and mass exploitation only began after the research was presented publicly in August.
Orange Tsai of DEVCORE found the chain and used it to win the Pwn2Own Vancouver competition in April 2021. Microsoft issued fixes in the April and May security updates, describing them in general terms. On 5 August 2021 he presented the full research at Black Hat USA under the title “ProxyLogon is Just the Tip of the Iceberg”, explaining the Exchange frontend architecture that made the whole class possible.
Working exploit code appeared within days of the presentation. Scanning for vulnerable Exchange servers began almost immediately, and by mid-August thousands of servers carried web shells, typically dropped into C:\inetpub\wwwroot\aspnet_client\ with randomly generated filenames.
The follow-on activity was predominantly criminal rather than espionage. LockFile ransomware used ProxyShell for initial access during August 2021, combining it with PetitPotam to reach domain controllers. Conti affiliates adopted it as a standard entry route, and Squirrelwaffle campaigns used compromised Exchange servers to send malicious email from inside legitimate conversation threads—mail that passed authentication checks because it genuinely came from the organisation.
The population hit was the same one that suffered through ProxyLogon five months earlier: smaller organisations running Exchange as infrastructure nobody owned, often several cumulative updates behind, where the April and May patches had never been applied because no advisory had told them it was urgent.
ProxyShell is the clearest case study available for why severity communication matters as much as patch availability. The fixes existed for four months before exploitation began. Organisations with a disciplined monthly Exchange patching cycle were never at risk. Everyone else learned about the chain from an incident.
There is also an Exchange-specific trap: security updates install only on recent cumulative update levels. An organisation several CUs behind cannot apply the security patch at all without first completing a cumulative update, which is a larger change requiring a maintenance window. The gap between “patch released” and “patch installable” is therefore much wider for Exchange than for most products, and that gap is where these incidents happen.
If you are assessing a server retrospectively:
aspnet_client.As with the earlier chain, patching an exploited server does not evict the attacker. Web shells, scheduled tasks, and added mailbox permissions all survive the update, so a compromise assessment is a separate exercise from patch verification.
Our Penetration Test Services include external mail infrastructure testing, which regularly identifies Exchange servers that are reachable, out of support, and several cumulative updates behind what their owners believe.
Most were not patched. The three fixes shipped in April and May 2021 with brief advisories that did not convey urgency, so many organisations deferred them. A second group could not install the security update at all because their Exchange cumulative update level was too old, and completing a CU upgrade requires a maintenance window they had not scheduled before exploitation began in August.
They are separate chains against the same product, found by the same researcher. ProxyLogon uses a server-side request forgery plus an Offline Address Book file write, and was exploited before patches existed in March 2021. ProxyShell uses an Autodiscover path confusion flaw, a PowerShell privilege escalation, and a mailbox export file write, and was exploited months after patches were available.
Exchange allows an administrator to export a mailbox to a PST file at a specified network or local path. The chain uses its escalated privileges to request an export with the destination set to a file inside the Exchange web root, with an ASPX extension. The resulting file contains attacker-controlled mailbox content, including a web shell, which IIS then executes when requested.
If you ran an on-premises Exchange server during the second half of 2021 and cannot confirm it was patched before August, yes. Web shells dropped at the time persist indefinitely, and investigations still uncover them years later. Check the web directories for unexpected ASPX files and review mailbox permission changes, even if the server has since been patched or migrated.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.