Zero Day Initiative - Exploiting Exchange PowerShell After ProxyNotShell: Part 4 - No Argument Constructor
Briefly

The PowerShell Remoting ConvertViaNoArgumentConstructor conversion mechanism unexpectedly led to the discovery of three critical vulnerabilities in Exchange, emphasizing the importance of thorough security assessments.
The redesign of the deserialization protection mechanism in Exchange, utilizing an allow list for type validation, has fundamentally changed the attack landscape, limiting previously exploitable vulnerabilities.
Microsoft's emphasis on addressing NTLM relaying vulnerabilities highlights the seriousness of potential privilege escalation risks within the Exchange environment, indicating an ongoing commitment to security.
Despite significant hardening measures, the exploration of the allowed classes in Exchange PowerShell revealed additional vulnerabilities, suggesting a need for continuous vigilance and scrutiny in security assessments.
Read at Zero Day Initiative
[
|
]