THE THREAT
eSentire is aware of public Proof-of-Concept (PoC) exploit code for the ProxyNotShell Exchange vulnerabilities (CVE-2022-41040 [CVSS:8.8], CVE-2022-41082 [CVSS:8.0]). The publication of this PoC code is expected to result in an increase in real-world attacks exploiting these vulnerabilities in the immediate future.
The ProxyNotShell vulnerabilities impact Microsoft Exchange Server 2013, 2016, 2019. CVE-2022-41082 allows Remote Code Execution (RCE) when PowerShell is accessible to the attacker. CVE-2022-41040 is a Server-Side Request Forgery (SSRF) vulnerability, that would allow an attacker to run PowerShell in the context of the compromised system. Both vulnerabilities require previous authentication for exploitation.
Limited exploitation of these vulnerabilities has been ongoing since at least September 2022. eSentire released a Security Advisory regarding ProxyNotShell on September 30th; at the time eSentire assessed with 'high confidence that the release of PoC code will result in an increase in real-world attacks against Exchange servers by multiple threat actor groups'. eSentire’s assessment remains the same, and additional attacks exploiting these vulnerabilities are expected.
What we’re doing about it
- eSentire Managed Vulnerability Service (MVS) has plugins in place to identify both vulnerabilities
- Customers with identified vulnerable devices are being contacted by eSentire’s Security Operations Center (SOC)
- eSentire MDR for Network has rules in place to detect exploitation attempts
- IP addresses, associated with real-world attacks, have been blocked via the eSentire Global Deny List
- The eSentire Threat Response Unit (TRU) has performed threat hunts across the eSentire client base for known signs of exploitation based on the September campaigns
- eSentire MDR for Endpoint has detections in place to identify known post- compromise activity such as the deployment of webshells, including China Chopper
- eSentire security teams continue to track these vulnerabilities for additional details and detection opportunities
What you should do about it
- After performing a business impact review, apply the relevant security patches released by Microsoft on November 8th, 2022
- If patching is not immediately possible, alternative mitigations are available
- Microsoft Exchange Online Customers do not need to take any additional actions
Additional information
The PoC exploit code has been tested and found effective against unpatched Exchange Server versions 2016 and 2019. Exploitation of Exchange Server 2013 would require additional code changes to the exploit code.
The ProxyNotShell vulnerabilities were initially disclosed in late September 2022. Microsoft released security patches for both vulnerabilities in the November 2022 Patch Tuesday release. Researchers have dubbed these exploits ProxyNotShell, as they have the same path and SSRF/RCE pair required to exploit ProxyShell, with the additional requirement of authentication. In known real-world attacks, threat actors have exploited the pair of vulnerabilities to deploy the China Chopper webshell on impacted Microsoft Exchange servers.
References:
[1] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41040
[2] https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41082
[3] https://www.esentire.com/security-advisories/microsoft-exchange-vulnerabilities-exploited
