CVE-2024-12802: CWE-305 Authentication Bypass by Primary Weakness in SonicWall SonicOS
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.
AI Analysis
Technical Summary
This vulnerability in SonicWall SonicOS SSL-VPN involves an authentication bypass due to inconsistent MFA enforcement between UPN and SAM account name login methods when integrated with Microsoft Active Directory. Because MFA can be configured separately for these two login identifiers, an attacker may bypass MFA by authenticating with the alternative account name that does not have MFA enforced. The flaw affects multiple SonicOS versions including 6.5.x, 7.x, and 8.0.0-8035. The CVSS 3.1 score of 9.1 reflects critical impact with network attack vector and no required privileges or user interaction. The vendor has not yet provided an official fix or remediation guidance, and no known exploits have been reported.
Potential Impact
Successful exploitation allows an attacker to bypass multi-factor authentication on SonicWall SSL-VPN devices integrated with Microsoft Active Directory, potentially leading to unauthorized access with full confidentiality and integrity impact. This could compromise sensitive data and system integrity without requiring user interaction or privileges. The vulnerability does not impact availability. No known exploits are currently reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, organizations should review their MFA configurations for SonicWall SSL-VPN, specifically ensuring consistent MFA enforcement across all login methods (UPN and SAM). Consider additional compensating controls such as network segmentation or restricting VPN access to trusted IPs. Monitor vendor channels for updates and apply patches promptly once available.
CVE-2024-12802: CWE-305 Authentication Bypass by Primary Weakness in SonicWall SonicOS
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in SonicWall SonicOS SSL-VPN involves an authentication bypass due to inconsistent MFA enforcement between UPN and SAM account name login methods when integrated with Microsoft Active Directory. Because MFA can be configured separately for these two login identifiers, an attacker may bypass MFA by authenticating with the alternative account name that does not have MFA enforced. The flaw affects multiple SonicOS versions including 6.5.x, 7.x, and 8.0.0-8035. The CVSS 3.1 score of 9.1 reflects critical impact with network attack vector and no required privileges or user interaction. The vendor has not yet provided an official fix or remediation guidance, and no known exploits have been reported.
Potential Impact
Successful exploitation allows an attacker to bypass multi-factor authentication on SonicWall SSL-VPN devices integrated with Microsoft Active Directory, potentially leading to unauthorized access with full confidentiality and integrity impact. This could compromise sensitive data and system integrity without requiring user interaction or privileges. The vulnerability does not impact availability. No known exploits are currently reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, organizations should review their MFA configurations for SonicWall SSL-VPN, specifically ensuring consistent MFA enforcement across all login methods (UPN and SAM). Consider additional compensating controls such as network segmentation or restricting VPN access to trusted IPs. Monitor vendor channels for updates and apply patches promptly once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- sonicwall
- Date Reserved
- 2024-12-19T16:22:43.405Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a0fe2c7e1370fbb4890d7ea
Added to database: 5/22/2026, 4:59:51 AM
Last enriched: 5/22/2026, 5:14:44 AM
Last updated: 5/23/2026, 1:16:50 PM
Views: 45
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.