dbcve.org
SonicosOperating system · Sonicwall

CVE-2024-40764

HIGH · 7.5 CVSS v3.1 Published 2024-07-18
Fix available
A fix is available. Upgrade to 6.5.4.v-21s-rc2457 / 7.0.1-5161 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 IPSec VPN allows an unauthenticated remote attacker to cause Denial of Service (DoS).

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

A heap-based buffer overflow vulnerability exists in the SonicOS IPSec VPN component. An unauthenticated remote attacker can exploit this memory corruption issue to crash the VPN service, resulting in a Denial of Service condition.

MitigationApply the vendor-supplied patch for SonicOS when available. Until then, restrict IPSec VPN access to trusted IP ranges via firewall rules and monitor for indicators of exploitation.

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:< 6.5.4.v-21s-rc2457< 7.0.1-5161>= 7.1.1-7040, < 7.1.1-7058

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed SonicOS version
    Access the SonicWall management interface (web UI or CLI) and locate the system firmware version information, typically found under System > Status or via the 'show version' command in CLI
    Affected if The version number is lower than 6.5.4.v-21s-rc2457, or lower than 7.0.1-5161, or falls within the range 7.1.1-7040 through 7.1.1-7057
  2. Determine if IPSec VPN is configured or enabled
    Review the SonicWall VPN configuration settings in the web interface under VPN > Settings, or check the running configuration via CLI to see if any IPSec VPN tunnels or policies are active
    Affected if IPSec VPN tunnels or policies are enabled on the device
  3. Verify network accessibility of the VPN service
    Check firewall rules and NAT settings to determine if the IPSec VPN ports (UDP 500, UDP 4500, and ESP protocol 50) are exposed to untrusted networks or the public internet
    Affected if The IPSec VPN service is reachable from untrusted or external IP addresses without restriction
  4. Confirm the specific firmware build variant
    Locate the full firmware build string in the SonicWall status page, which includes both the version number and the build suffix (for example, the 'v-21s-rc2457' portion in 6.5.4.v-21s-rc2457)
    Affected if The build identifier is earlier than the fixed builds for the respective version branch

A system is affected if it runs a SonicOS version that matches the vulnerable ranges AND has IPSec VPN enabled and accessible, making it susceptible to the heap-based buffer overflow crash.

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 6.5.4.v-21s-rc2457 / 7.0.1-5161 / 7.1.1-7058 or later
Fixed in 6.5.4.v-21s-rc24577.0.1-51617.1.1-7058
Interim mitigation

Apply the vendor-supplied patch for SonicOS when available. Until then, restrict IPSec VPN access to trusted IP ranges via firewall rules and monitor for indicators of exploitation.

Recommended fix High confidence

6.5.4.v-21s-rc2457 (6.5.x) / 7.0.1-5161 (7.0.x) / 7.1.1-7058 (7.1.x) - choose the appropriate version for your hardware platform

  1. 1. Identify the current SonicOS version by navigating to the SonicWall management interface > System > Status
  2. 2. Based on your current version branch, upgrade to the minimum fixed version: For 6.5.x branch, upgrade to 6.5.4.v-21s-rc2457 or later; For 7.0.x branch, upgrade to 7.0.1-5161 or later; For 7.1.x branch (versions 7040-7057), upgrade to 7.1.1-7058 or later
  3. 3. Download the firmware from the official SonicWall support portal (https://www.sonicwall.com/support/)
  4. 4. Navigate to System > Firmware Update in the management interface
  5. 5. Upload and apply the new firmware, ensuring to backup configuration before upgrade
  6. 6. After reboot, verify the new version is installed and the IPSec VPN service is operational
  7. 7. Test IPSec VPN connectivity to confirm the fix does not impact legitimate traffic
Caveat Review release notes for your specific SonicWall appliance model for any configuration or feature changes between versions

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

Fix this in Sonicos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40764 — 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-40764 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