CVE-2024-22394 Exposed: SonicWall SSL-VPN’s Authentication Flaw

Recently, a critical flaw, nestled within the SSL-VPN feature of SonicWall’s SonicOS, has been brought to light, exposing a gap wide enough for remote attackers to slip through unnoticed.

CVE-2024-22394

Dubbed CVE-2024-22394, this vulnerability exposes an improper authentication flaw, potentially allowing remote attackers to bypass authentication on affected devices. With a CVSS score of 8.6, indicating a high severity level, this vulnerability poses a substantial threat to the security of numerous organizations relying on SonicWall’s technology to safeguard their networks.

An improper authentication vulnerability has been identified in SonicWall SonicOS SSL-VPN feature, which in specific conditions could allow a remote attacker to bypass authentication,stated SonicWall’s advisory.

This vulnerability has the potential to compromise the security of hundreds of thousands of active VPNs worldwide. Given the critical role that VPNs play in enabling secure remote access for organizations, any vulnerability within such systems is cause for immediate attention and action.

This vulnerability specifically affects Gen7 SonicWall firewalls running SonicOS firmware version 7.1.1-7040. The following SonicWall devices are impacted by CVE-2024-22394:

Products Affected Version
Gen7 – TZ270, TZ270W, TZ370, TZ370W, TZ470, TZ470W, TZ570, TZ570W, TZ570P, TZ670, NSa 2700, NSa 3700, NSa 4700, NSa 5700, NSa 6700, NSsp 10700, NSsp 11700, NSsp 13700, NSv 270, NSv 470, NSv 870. SonicOS 7.1.1-7040

Organizations relying on these configurations for their network security infrastructure are urged to take swift action to address this vulnerability before it is exploited by malicious actors.

SonicWall has promptly acknowledged the existence of this vulnerability through an advisory statement. According to SonicWall’s PSIRT (Product Security Incident Response Team), while there have been no reported instances of active exploitation in the wild, the company is taking proactive measures to address the issue swiftly and effectively.

The lack of reports regarding a Proof of Concept (PoC) or any malicious exploitation of this vulnerability offers some reassurance. However, the absence of evidence does not guarantee the absence of risk. Organizations must remain vigilant and proactive in mitigating potential threats to their network security.