Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
ProxyNotShell is the autumn 2022 Exchange exploit chain that required a valid mailbox account, and whose published URL-rewrite mitigations were bypassed repeatedly before a patch arrived.

What Is ProxyNotShell?
ProxyNotShell refers to the pairing of CVE-2022-41040 and CVE-2022-41082 in on-premises Microsoft Exchange Server, first reported in the wild in September 2022. The slightly unusual name reflects what distinguishes it from the earlier chains: it requires authentication. An attacker needs valid credentials for any mailbox on the server, which is why it was initially described as not quite the same class of problem as ProxyShell.
In practice that distinction offered less comfort than it sounded. A single phished mailbox password, or a credential from an earlier breach, was sufficient.
CVE-2022-41040 is a server-side request forgery in the Autodiscover service, reachable by any authenticated user. CVE-2022-41082 is a remote code execution flaw in Exchange PowerShell remoting, reachable once the first flaw has delivered a request to the backend. Together they produce code execution as the Exchange service account, which on a typical deployment means extensive Active Directory privileges.
The Vietnamese security company GTSC discovered the chain while investigating an incident in August 2022 and reported it through the Zero Day Initiative. They published their findings on 29 September 2022 after observing continued exploitation, at which point no patch existed.
Microsoft’s initial guidance was a URL Rewrite rule for IIS, designed to block the Autodiscover request pattern the exploit used. What followed was uncomfortable to watch. Researchers demonstrated a bypass within a day by altering the request format. Microsoft revised the rule. A further bypass appeared. The rule was revised again, and the advisory was updated several times over the following weeks.
Each iteration illustrated the limits of pattern-matching mitigation: the rule blocked known exploit strings rather than fixing the underlying flaw, so any variation that still reached the vulnerable code defeated it. A patch finally arrived on 8 November 2022 as part of the regular update cycle, more than two months after the first reported exploitation.
Organisations relying on the rewrite rule in the interim were protected only against the exact variants it covered at the time they applied it—and many never applied the revisions.
In December 2022, CrowdStrike investigated a set of Play ransomware intrusions and found attackers reaching the same remote code execution flaw by a different route. Rather than using the Autodiscover SSRF, they abused CVE-2022-41080, a separate Exchange privilege escalation, to reach the PowerShell backend through Outlook Web Access. The technique was named OWASSRF.
The significance was that the URL Rewrite mitigations, which targeted the Autodiscover path, did nothing against it. Servers whose administrators believed themselves mitigated were being compromised. Only the November patch, which addressed CVE-2022-41080 as well, actually closed it.
The indicators overlap with the earlier Exchange chains, which is convenient for anyone who built rules then. Watch for the IIS worker process spawning cmd.exe, powershell.exe, or net.exe; new ASPX files in the Exchange web directories; and PowerShell remoting connections from external addresses. Exchange’s own HttpProxy logs record the Autodiscover request pattern, and the OWA logs record the OWASSRF variant, so both log sets are worth retaining.
Our Managed Security Services (MDR) monitor exactly these process-lineage signals on mail infrastructure, which detect exploitation regardless of which chain delivered it.
The name contrasts it with ProxyShell. The earlier chain was exploitable without any credentials, whereas this one requires an authenticated mailbox user, so researchers named it to signal that it was not quite the same thing. The nickname proved somewhat optimistic, since obtaining a single valid mailbox credential is a routine step for most attackers.
Only briefly and only against known patterns. Each published rule was bypassed within days by varying the request format, and Microsoft revised the guidance several times. The OWASSRF technique then reached the same vulnerability through Outlook Web Access, which the Autodiscover-focused rules did not cover at all. The November 2022 security update was the first reliable protection.
It raises the bar substantially, because the chain begins with an authenticated session and MFA makes credential reuse much harder. It is not absolute: legacy protocols that bypass modern authentication, and tokens stolen through session hijacking, can still provide the required authentication. Combine MFA on Outlook Web Access with blocking basic authentication and restricting PowerShell remoting.
Confirm the cumulative update and security update levels are current, since Exchange security patches require a recent CU. Verify that PowerShell remoting is not available to ordinary users from the internet, that basic authentication is disabled, and that multi-factor authentication covers web access. Then review the web directories for unexpected ASPX files and check process lineage alerting is in place.
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.