ProxyShell vs. ProxyLogon: Key Differences and Exchange Patching Risks

Summary
Huntress explains how ProxyShell differs from ProxyLogon, both affecting on-premises Microsoft Exchange servers, and warns that unpatched servers face remote code execution. It urges administrators to apply the latest security patches.
Key points
- ProxyShell was disclosed in August 2021 and was actively used against on-premises Microsoft Exchange servers that had not been properly patched.
- The article says ProxyShell exploitation could provide remote code execution with administrator-level access.
- ProxyLogon was disclosed in March 2021; the article attributes its exploitation to HAFNIUM and says it enabled remote code execution against internet-accessible victim servers.
- Huntress reported about 380 webshells discovered in the ProxyShell exploitation at the time, compared with roughly twice that number for ProxyLogon; compromised ProxyLogon servers were still surfacing.
- The article warns that attackers could use Exchange access to move laterally, obtain sensitive information, or deploy ransomware.
- Huntress recommends applying the latest security patch to on-premises Exchange servers and monitoring for indicators of compromise.
Article Details
- Vulnerability Types
- Remote code execution
- Exploitation Status
- active
- Exploit Availability
- public_poc
- Patch Status
- available
- Workarounds
- Install the latest security patch on on-premises Exchange servers.
