CVE-2024-53704
An Improper Authentication vulnerability in the SSLVPN authentication mechanism allows a remote attacker to bypass authentication.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Cloudflare publishes WAF rules written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.
Cloudflare · 2 rules (Block) · since 18 Feb 2025
- SonicWall SSLVPN - Auth Bypass - CVE:CVE-2024-53704 · Cloudflare Managed Ruleset
- SonicWall SSLVPN 2 - Auth Bypass - CVE:CVE-2024-53704 · Cloudflare Managed Ruleset
Also consider: patch · enable the vendor rule in block mode · add auth middleware
Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-53704 being exploited?
Yes. CVE-2024-53704 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-53704?
CVE-2024-53704 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-53704?
Yes. A fix has been recorded for CVE-2024-53704. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-53704 affect?
CVE-2024-53704 affects sonicwall:sonicos. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected7.1.1-7058 and older versions
- affected7.1.2-7019
- affected8.0.0-8035
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 3 GitHub proofs of concept · 1 Nuclei template
- SSL VPN Session Hijacking · detection template · critical
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- partial
Assessed by CISA 18 Feb 2025 (SSVC 2.0.3).
timeline
- 9 Jan 2025Published
- 22 Jan 2025First proof-of-concept repository on GitHub (unvetted) · 13 days later
- 18 Feb 2025Added to CISA KEV (exploited in the wild) · 27 days later
- 18 Feb 2025CISA SSVC assessment: exploitation active · same day later
- 11 Mar 2025CISA remediation due date (US federal agencies) · 21 days later
- 4 Aug 2026CVE record last updated · 511 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 91 days (about 3 months) later
- Advisorypsirt.global.sonicwall.com /vuln-detail/SNWLID-2025-0003
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-53704
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.