Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

ProxyNotShell RCE in Microsoft Exchange Server PowerShell

IdentifiersCVE-2022-41082CWE-502· Deserialization of Untrusted Data

CVE-2022-41082 is a Microsoft Exchange Server remote code execution vulnerability that is part of the ProxyNotShell exploit chain affecting on-premises Exchange Server 2013, 2016, and 2019. The issue is exploitable when Exchange PowerShell is accessible to the attacker and is commonly chained with CVE-2022-41040, an SSRF vulnerability, to reach the vulnerable backend path. Supporting content indicates the vulnerable behavior involves Exchange PowerShell type conversion and unsafe deserialization: Exchange’s custom SerializationTypeConverter ultimately passes attacker-controlled SerializationData into BinaryFormatter.Deserialize() after LanguagePrimitives.ConvertTo() processing. Public analysis of the bug notes that the original exploitation path abused deserialization of allowed types and a subsequent XamlReader.Parse(string) invocation to achieve code execution. Microsoft’s patch introduced additional validation around UnitySerializationHolder-based deserialization to block the known exploitation path. In operational reporting, successful exploitation has been associated with web shell deployment and follow-on intrusion activity.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote code execution on vulnerable Exchange servers. In observed intrusions, attackers used the ProxyNotShell chain to compromise Exchange, deploy web shells, execute PowerShell, conduct Active Directory reconnaissance, exfiltrate data, and establish persistence. Because Exchange typically operates with high privilege and trusted connectivity in enterprise environments, compromise can lead to full Exchange takeover and facilitate broader domain compromise, lateral movement, credential theft, and ransomware deployment.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, implement Microsoft-recommended IIS or WAF URL rewrite/filtering to block exploit traffic matching autodiscover-to-PowerShell patterns, including the published regular expression for ProxyNotShell exploitation. Restrict or disable external access to Exchange PowerShell where operationally feasible, limit exposure of OWA/ECP and related Exchange endpoints to trusted networks, enable Exchange Emergency Mitigation Service, ensure Exchange AMSI integration is enabled and functioning, audit and minimize antivirus exclusions on Exchange paths, and monitor IIS/Exchange logs for suspicious autodiscover.json, X-Rps-CAT, MAPI, and backend PowerShell access patterns.

Remediation

Patch, then assume compromise.

Apply Microsoft’s official security updates for CVE-2022-41082 and the associated ProxyNotShell chain, including the patches released on November 8, 2022, for supported Exchange Server 2013, 2016, and 2019 deployments. Ensure Exchange is fully updated to the latest supported cumulative update and subsequent security updates. After patching, remove temporary mitigations only if Microsoft guidance indicates they are no longer required, and review systems for indicators of compromise such as web shells, suspicious PowerShell activity, and anomalous Exchange child processes.
PUBLIC EXPLOITS

Exploits

3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (4 hidden).

VALID 3 / 7 TOTALView more in app
CVE-2022-41082MaturityPoCVerified exploit

This repository is a proof-of-concept exploit for CVE-2022-41082 (OWASSRF), targeting Microsoft Exchange servers. It consists of three files: a README.md with detailed usage and background, a Python exploit script (poc.py), and a requirements.txt listing dependencies. The main exploit script, poc.py, automates the process of authenticating to the Exchange OWA endpoint, starting a local RPC server, and leveraging the OWASSRF vulnerability to execute arbitrary PowerShell commands on the target server. The attacker provides a command file containing the payload, which is base64-encoded and injected into the PowerShell session. The exploit can be used for a variety of post-exploitation actions, including establishing a reverse shell. The script requires valid credentials for a user with Remote PowerShell access and targets the Exchange server over HTTPS endpoints. The repository is structured as a standalone PoC and does not belong to a larger exploit framework.

soltanali0Disclosed Oct 24, 2024pythonnetwork
OWASSRF-CVE-2022-41082-POCMaturityPoCVerified exploit

This repository provides a working exploit for two Microsoft Exchange vulnerabilities: CVE-2022-41082 (ProxyNotShell/OWASSRF, post-auth RCE) and CVE-2022-41076 (TabShell, privilege escalation via PowerShell sandbox escape). The main exploit is implemented in 'poc.py', a Python script that authenticates to the Exchange OWA endpoint using provided credentials, sets up a local HTTP server to relay PowerShell requests, and abuses the Exchange PowerShell endpoint to execute arbitrary commands on the server. The command to execute is read from a file (default: 'cmd'), which can be set to any desired payload (e.g., launching calc.exe). The exploit leverages the PowerShell Remoting Protocol (PSRP) via a bundled 'pypsrp' library. The included 'TabShell.ps1' PowerShell script is used for privilege escalation after initial access, allowing the attacker to break out of the restricted PowerShell sandbox. The repository is well-structured, with clear separation between the exploit logic, supporting library code, and payload scripts. It targets unpatched Exchange 2013, 2016, and 2019 servers as of November 2022, and requires valid credentials for exploitation. The attack vector is network-based, targeting the Exchange OWA and PowerShell endpoints over HTTP(S).

balki97Disclosed Dec 22, 2022pythonpowershellnetwork
CVE-2022-41082-POCMaturityPoCVerified exploit

This repository provides a working exploit for two Microsoft Exchange vulnerabilities: CVE-2022-41082 (ProxyNotShell/OWASSRF, a post-auth RCE) and CVE-2022-41076 (TabShell, a privilege escalation via PowerShell sandbox escape). The main exploit logic is in 'poc.py', which authenticates to the Exchange OWA endpoint using provided credentials, then abuses the PowerShell endpoint to execute arbitrary commands. The exploit sets up a local HTTP server to relay requests and uses the included 'pypsrp' library for PowerShell Remoting Protocol (PSRP) communication. The payload is customizable and can be any PowerShell command, with examples provided (calc.exe, mspaint.exe, ipconfig.exe). The 'TabShell.ps1' script demonstrates privilege escalation by breaking out of the restricted PowerShell sandbox after initial access is gained. The repository is structured with a main PoC script, a PowerShell privilege escalation script, a command file for payloads, and a full implementation of the pypsrp library for PSRP communication. The exploit is operational and can be used to achieve RCE and privilege escalation on vulnerable, unpatched Exchange servers with valid credentials.

bigherocenterDisclosed Feb 21, 2023pythonpowershellnetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationExchange Serverapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence54

Every observed campaign linking this CVE to a named adversary.

Associated malware15

Malware families riding this exploit, with evidence and IOCs.

Detection signatures3

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.