dbcve.org
Sma 200 FirmwareOperating system · Sonicwall

CVE-2024-45318

HIGH · 8.1 CVSS v3.1 Published 2024-12-05
Fix available
A fix is available. Upgrade to 10.2.1.14-75sv or later.
See remediation →
90/100
Remediation priority · Urgent
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
A vulnerability in the SonicWall SMA100 SSLVPN web management interface allows remote attackers to cause Stack-based buffer overflow and potentially lead to code execution.

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

CVE-2024-45318 is a stack-based buffer overflow vulnerability in the SonicWall SMA100 series SSLVPN web management interface. Remote attackers can exploit this flaw to potentially execute arbitrary code on affected devices. The vulnerability carries a CVSS score of 8.1 (HIGH), indicating significant risk to organizations using this SSLVPN solution.

MitigationApply the vendor-supplied patch for CVE-2024-45318 to all affected SonicWall SMA100 devices. Additionally, restrict access to the SSLVPN web management interface to trusted networks or administrative hosts only until patching can be completed.

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
Sma 200 FirmwareOperating system
Affected:< 10.2.1.14-75sv
Sma 210 FirmwareOperating system
Affected:< 10.2.1.14-75sv
Sma 400 FirmwareOperating system
Affected:< 10.2.1.14-75sv
Sma 410 FirmwareOperating system
Affected:< 10.2.1.14-75sv
Sma 500v FirmwareOperating system
Affected:< 10.2.1.14-75sv

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 SMA device model
    Access the device web interface or check the physical label/console to confirm the model is one of: SMA 200, SMA 210, SMA 400, SMA 410, or SMA 500v
    Affected if The device is NOT one of these five models, as they are the only products listed as affected
  2. Check the installed firmware version
    Log into the SMA web management interface and navigate to System > Status or use the CLI command 'version' to retrieve the current firmware build number
    Affected if The firmware version is earlier than 10.2.1.14-75sv (for example, 10.2.1.10-62sv or older)
  3. Verify the SSLVPN web management interface is enabled
    In the web interface, go to Users > Settings or SSL-VPN > Settings and confirm the SSLVPN service is turned on and accessible
    Affected if SSLVPN is enabled and the management interface is exposed to network-accessible interfaces
  4. Confirm remote access configuration
    Check the firewall or access rules under Network > Interfaces and verify whether the WAN or external interface allows inbound HTTPS traffic to the SSL-VPN portal
    Affected if The SSLVPN web interface is reachable from untrusted networks (such as the internet) without network restrictions

You are affected if you have a SonicWall SMA 200, 210, 400, 410, or 500v device running firmware versions earlier than 10.2.1.14-75sv with the SSLVPN web management interface enabled and accessible.

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 10.2.1.14-75sv or later
Fixed in 10.2.1.14-75sv
Interim mitigation

Apply the vendor-supplied patch for CVE-2024-45318 to all affected SonicWall SMA100 devices. Additionally, restrict access to the SSLVPN web management interface to trusted networks or administrative hosts only until patching can be completed.

Recommended fix High confidence

SMA 100 series firmware 10.2.1.14-75sv or later

  1. Identify the specific SMA100 model in use (200, 210, 400, 410, or 500v)
  2. Access the SMA device management interface or CLI
  3. Navigate to the firmware update section
  4. Download firmware version 10.2.1.14-75sv or later from the official SonicWall support portal
  5. Upload and apply the firmware update
  6. After reboot, verify the running firmware version meets the minimum requirement of 10.2.1.14-75sv
  7. Verify that SSLVPN and web management functionality operate normally post-upgrade
Caveat Review SonicWall release notes for 10.2.1.14-75sv for any functionality changes or migration requirements before upgrading

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

Fix this in Sma 200 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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