Vigilbase CVEConnect your agent

SonicWall SonicOS SSLVPN Improper Authentication Vulnerability

Exploited · KEV 2025-02-18RansomwareCVE-2024-53704CWE-287

Exploited since 2025-02-18. 2 of 8 rule sources name it; Cloudflare blocks by default. Our CRS test: not blocked.

Edge rules
2/8
Our test
Not blocked
CVSS
8.2
EPSS
95.3% Top 0.1%
Posts, 14d
02026-10-20: 0 posts2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts
Published
2025-01-09

An Improper Authentication vulnerability in the SSLVPN authentication mechanism allows a remote attacker to bypass authentication.

Ask Vigil

AI · answers from this page
Ask about CVE-2024-53704: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Severity, decoded

CVSS 3.1
High · 8.2 / 10

Exploitable over the network, with no privileges and no user interaction, leading to low impact on confidentiality and full loss of availability.

Over the internetNo login neededNo user actionWorks reliablySerious impact
How the score is built8 metrics
  • Attack vectorAn attacker can reach it over the internet; no access to your network needed.
    Network
  • Attack complexityNo special conditions are needed; the attack works reliably.
    Low
  • Privileges requiredNo account or login is needed.
    None
  • User interactionNo one has to click or open anything; the attack works on its own.
    None
  • ScopeThe damage stays within the vulnerable component.
    Unchanged
  • Confidentiality impactAn attacker can read some data, but has no control over what they get.
    Low
  • Integrity impactData cannot be changed by the attacker.
    None
  • Availability impactAn attacker can take the component down completely or keep it from serving anyone.
    High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
CISA's assessmentSSVC, from the CVE record
ExploitationActive

Attackers are exploiting this in the wild.

AutomatableYes

Attackers can script the attack end to end and hit many targets at once.

Technical impactPartial

A successful attack gives limited control over the affected software or limited access to its data.

Public exploits

1 found
0 Metasploit0 Exploit-DB1 Scanner template0 GitHub PoCs

Links are to third-party code: never run it outside an isolated lab.

Timeline

  1. 2025-01-09
    CVE published
    CVE List
  2. 2025-02-18
    Added to CISA KEV
    Confirmed exploitation in the wild
  3. 2025-02-18
    Cloudflare ships a rule
    SonicWall SSLVPN - Auth Bypass - CVE:CVE-2024-53704
  4. 2025-03-11
    F5 ships a rule
    SonicWall SSLVPN Authentication Bypass
  5. 2026-11-02
    Our test: OWASP Core Rule Set let it through
    paranoia level 1, anomaly threshold 5, default CRS settings
  6. 2026-11-02
    Our test: OWASP Core Rule Set let it through
    paranoia level 2, anomaly threshold 5, default CRS settings

Social

2026-10-20: 0 posts2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts

No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.

Vendor statements

Quoted
CloudflareWAF Managed Rules2 quotesBlocks by default

First rule 2025-02-18, 40 days after the CVE was published.

2025-02-18New rule…3b66df22Default: BlockSource
SonicWall SSLVPN - Auth Bypass - CVE:CVE-2024-53704. Previous action: Log. New action: Block. This is a New Detection
2025-02-24New rule…4916911eDefault: BlockSource
SonicWall SSLVPN 2 - Auth Bypass - CVE:CVE-2024-53704. Previous action: Log. New action: Block. This is a New Detection
AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.

Google CloudCloud Armor preconfigured WAF rulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.

FastlyNext-Gen WAF virtual patchesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

F5Attack signatures (Distributed Cloud WAF)1 quoteRule published

First rule 2025-03-11, 61 days after the CVE was published.

2025-03-11New rule200013109Source
Added: signature 200013109 "SonicWall SSLVPN Authentication Bypass" (Authentication/Authorization Attacks, risk High), systems: Other Web Server. References: CVE-2024-53704.
AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.