SSL-VPN MFA Bypass in SonicWALL SSL-VPN can arise in specific cases due to the separate handling of UPN (User Principal Name) and SAM (Security Account Manager) account names when integrated with Microsoft Active Directory, allowing MFA to be configured independently for each login method and potentially enabling attackers to bypass MFA by exploiting the alternative account name.
Summary
AISonicWall SSL-VPN can handle UPN and SAM account names separately when integrated with Microsoft Active Directory, allowing MFA to be configured independently for each login method. In those cases, an attacker may bypass MFA by using the alternative account name. The input does not specify whether prior authentication or user interaction is required.
Who should check
Teams running SonicWall SonicOS with SSL-VPN integrated with Microsoft Active Directory should check their deployments; affected versions were not provided.
What to do
- 1Consult the SonicWall advisory for affected and fixed versions and remediation guidance.