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.
                
            Metrics
Affected Vendors & Products
References
        History
                    Thu, 09 Jan 2025 15:15:00 +0000
| Type | Values Removed | Values Added | 
|---|---|---|
| Metrics | cvssV3_1 
 
 | 
Thu, 09 Jan 2025 09:15:00 +0000
| Type | Values Removed | Values Added | 
|---|---|---|
| Description | 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. | |
| Weaknesses | CWE-305 | |
| References |  | 
 MITRE
                        MITRE
                    Status: PUBLISHED
Assigner: sonicwall
Published: 2025-01-09T09:08:26.012Z
Updated: 2025-01-09T14:30:34.676Z
Reserved: 2024-12-19T16:22:43.405Z
Link: CVE-2024-12802
 Vulnrichment
                        Vulnrichment
                    Updated: 2025-01-09T14:30:28.552Z
 NVD
                        NVD
                    Status : Received
Published: 2025-01-09T09:15:06.587
Modified: 2025-01-09T15:15:14.683
Link: CVE-2024-12802
 Redhat
                        Redhat
                    No data.