dbcve.org
SonicosOperating system · Sonicwall

CVE-2024-29013

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to 7.0.1-5161 / 7.1.1-7058 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Heap-based buffer overflow vulnerability in the SonicOS SSL-VPN allows an authenticated remote attacker to cause Denial of Service (DoS) via memcpy function.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Heap-based buffer overflow in SonicOS SSL-VPN's memcpy implementation allows authenticated remote attackers to overflow the heap buffer, causing denial of service. The vulnerability stems from insufficient bounds checking before copying data via memcpy.

MitigationApply vendor-provided patches for SonicOS SSL-VPN. If no patch available, restrict SSL-VPN access to trusted users only and monitor for anomalous traffic patterns indicative of exploitation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SonicosOperating system
Affected:< 7.0.1-5161>= 7.1.1, < 7.1.1-7058>= 7.1.2, < 7.1.2-7019

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SonicOS device and version
    Access the Sonicwall management interface or use CLI command 'show version' to identify the device model and installed SonicOS firmware version
    Affected if Version falls into < 7.0.1-5161, >= 7.1.1 but < 7.1.1-7058, or >= 7.1.2 but < 7.1.2-7019
  2. Verify SSL-VPN is configured
    Check the Sonicwall SSL-VPN settings via the management interface under SSL-VPN or Remote Access settings, or use CLI to display SSL-VPN configuration
    Affected if SSL-VPN is enabled and a connection profile exists
  3. Confirm remote access authentication is active
    Review SSL-VPN user authentication settings to confirm local or remote user authentication is enabled for SSL-VPN connections
    Affected if SSL-VPN allows authenticated remote connections (even to limited users)
  4. Audit SSL-VPN connection logs
    Review Sonicwall logs for SSL-VPN connection events, looking for unusual connection patterns or authentication attempts
    Affected if Unexpected SSL-VPN authentication success or connection patterns from unknown sources

Device is affected if it runs a vulnerable SonicOS version AND has SSL-VPN enabled with authentication configured, allowing authenticated remote attackers to trigger the heap overflow via crafted SSL-VPN requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.1-5161 / 7.1.1-7058 / 7.1.2-7019 or later
Fixed in 7.0.1-51617.1.1-70587.1.2-7019
Interim mitigation

Apply vendor-provided patches for SonicOS SSL-VPN. If no patch available, restrict SSL-VPN access to trusted users only and monitor for anomalous traffic patterns indicative of exploitation attempts.

Recommended fix High confidence

Sonicos 7.0.1-5161 or later; Sonicos 7.1.1-7058 or later; Sonicos 7.1.2-7019 or later

  1. 1. Identify the current SonicWall SSL-VPN device firmware version via the management interface
  2. 2. Determine which Sonicos branch is currently running (7.0.x, 7.1.1, or 7.1.2)
  3. 3. For Sonicos 7.0.x: Upgrade to version 7.0.1-5161 or later
  4. 4. For Sonicos 7.1.1: Upgrade to version 7.1.1-7058 or later
  5. 5. For Sonicos 7.1.2: Upgrade to version 7.1.2-7019 or later
  6. 6. Download the appropriate firmware from the official SonicWall support portal
  7. 7. Backup current device configuration before applying the upgrade
  8. 8. Upload and apply the new firmware via the SonicWall management interface
Caveat Firmware upgrades may cause brief service interruption; ensure change window is scheduled

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sonicos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29013 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29013 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data