Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2022-41082: Microsoft Exchange Server Remote PowerShell RCE (ProxyNotShell component)

Published Oct 3, 2022 · Updated 16 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.0High · v3.1
EPSS100.0%100th percentile
CISA KEVYesAdded Sep 30, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2022-41082CWE-502 · Deserialization of Untrusted Data

CVE-2022-41082 is an insecure deserialization vulnerability affecting on-premises Microsoft Exchange Server 2013, 2016, and 2019. An authenticated attacker who can access Exchange Remote PowerShell can trigger arbitrary code execution on the server. It is the code-execution component of ProxyNotShell, which chains it with CVE-2022-41040 to reach PowerShell through server-side request forgery, and OWASSRF, which chains it with CVE-2022-41080 through Outlook Web Access. Both chains have been exploited in the wild. Exchange Online is unaffected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation permits arbitrary code and PowerShell command execution on a vulnerable Exchange server, potentially compromising the Exchange environment and the confidentiality, integrity, and availability of hosted email. Attackers can use the resulting access to install backdoors, steal credentials and data, and move laterally into connected infrastructure. Observed exploitation chains have supported persistent access and ransomware operations.

Mitigation

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

Until patching is possible, restrict Exchange and Remote PowerShell access through firewall or VPN controls, disable Remote PowerShell for non-administrative users where feasible, and disable Outlook Web Access if necessary to prevent OWASSRF exposure. Historical ProxyNotShell IIS URL Rewrite or WAF filters are not sufficient protection because OWASSRF bypasses those mitigations. Restrict outbound connections from Exchange servers using allow lists, and monitor for suspicious Exchange requests, unexpected PowerShell activity, and webshell behavior. Network restrictions do not protect against attackers who already have internal access.

Remediation

Patch, then assume compromise.

Apply the applicable Microsoft Exchange security updates released on November 8, 2022, covered by KB5019758, or a later applicable update incorporating those fixes. These updates address CVE-2022-41082 and its associated chaining vulnerabilities, CVE-2022-41040 and CVE-2022-41080. Verify installation and investigate potentially exposed servers for prior exploitation; patching does not remove existing backdoors.

Public exploits

Exploits

4 exploits validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.

View more in app →
exchange_proxynotshell_rce.rbThis repository contains a single Metasploit module: 'exchange_proxynotshell_rce.rb', which exploits the ProxyNotShell vulnerabilities (CVE-2022-41040 and CVE-2022-41082) in Microsoft Exchange Server 2019. The exploit chains an SSRF (Server-Side Request Forgery) and a deserialization flaw to achieve remote code execution on the target Exchange server. The attacker must have valid credentials to authenticate. The module supports two payload types: direct command execution and Windows executable dropper. The exploit interacts with Exchange's HTTP endpoints, specifically '/mapi/nspi/' for version checking and '/Autodiscover/autodiscover.json' for the SSRF and PowerShell backend access. The code is operational and leverages Metasploit's payload system, allowing for customizable payloads. The repository is structured as a typical Metasploit exploit module, with all logic contained in a single Ruby file.Disclosed Sep 28, 2022 · Framework: metasploit · ruby · networkWeaponizedOWASSRF-CVE-2022-41082-POCThis 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).balki97 · Disclosed Dec 22, 2022 · python · powershell · networkOperationalCVE-2022-41082-POCThis 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.bigherocenter · Disclosed Feb 21, 2023 · python · powershell · networkOperationalCVE-2022-41082This 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.soltanali0 · Disclosed Oct 24, 2024 · python · networkPoC
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
FAQ

Frequently asked questions

Is CVE-2022-41082 exploited in the wild?
Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Sep 30, 2022.
Is there a public exploit for CVE-2022-41082?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2022-41082, the earliest disclosed Sep 28, 2022.
Is there a patch for CVE-2022-41082?
Apply the applicable Microsoft Exchange security updates released on November 8, 2022, covered by KB5019758, or a later applicable update incorporating those fixes. These updates address CVE-2022-41082 and its associated chaining vulnerabilities, CVE-2022-41040 and CVE-2022-41080.
What products are affected by CVE-2022-41082?
Microsoft Corporation Exchange Server.
How severe is CVE-2022-41082?
CVE-2022-41082 has a CVSS v3.1 score of 8.0 (High) and an EPSS score of 100.0% (100th percentile) as of Nov 4, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence61Every report linking this CVE to a named adversary.
Associated malware34Malware families linked to this CVE, with evidence and IOCs.
Detection signatures5YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.