dbcve.org
Sma 200 FirmwareOperating system · Sonicwall

CVE-2024-45319

MEDIUM · 6.3 CVSS v3.1 Published 2024-12-05
Fix available
A fix is available. Upgrade to 10.2.1.14-75sv or later.
See remediation →
69/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
A vulnerability in the SonicWall SMA100 SSLVPN firmware 10.2.1.13-72sv and earlier versions allows a remote authenticated attacker can circumvent the certificate requirement during authentication.

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 vulnerability in SonicWall SMA100 SSLVPN firmware versions 10.2.1.13-72sv and earlier allows an authenticated remote attacker to bypass the certificate validation requirement during the authentication process, potentially enabling unauthorized VPN access through circumventing intended security controls.

MitigationUpdate the SonicWall SMA100 firmware to a version newer than 10.2.1.13-72sv that addresses this vulnerability, and verify that certificate-based authentication is now properly enforced.

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

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

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. Check the installed firmware version
    Log into the SMA web management console and navigate to System > Status, or run 'get system status' via CLI to view the firmware version string (for example, 10.2.1.13-72sv)
    Affected if The firmware version shown is earlier than 10.2.1.14-75sv (for example, 10.2.1.13-72sv, 10.2.0.x, or any version with a build number lower than 75sv)
  2. Confirm the SMA hardware model
    Identify the specific SMA model (200, 210, 400, 410, or 500v) from the device label or the System > Status page in the web interface
    Affected if The device is one of the SMA 200, 210, 400, 410, or 500v models and the firmware version is below 10.2.1.14-75sv
  3. Verify if certificate-based authentication is enabled
    In the SMA web console, go to Users > Settings > Authentication Methods, or check the SSL-VPN settings to see if certificate authentication is configured as a required or optional authentication factor
    Affected if Certificate-based authentication is enabled on the VPN configuration and the firmware version is vulnerable (below 10.2.1.14-75sv)

You are affected if your SonicWall SMA 200/210/400/410/500v device runs firmware version 10.2.1.13-72sv or any earlier version, particularly if certificate-based VPN authentication is configured.

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

Update the SonicWall SMA100 firmware to a version newer than 10.2.1.13-72sv that addresses this vulnerability, and verify that certificate-based authentication is now properly enforced.

Recommended fix Moderate confidence

SMA 200/210/400/410/500v Firmware 10.2.1.14-75sv or later

  1. 1. Log into the SonicWall SMA appliance administrative interface.
  2. 2. Navigate to the System > Firmware or System > Settings section.
  3. 3. Verify the current firmware version is below 10.2.1.14-75sv.
  4. 4. Download the firmware version 10.2.1.14-75sv or later from the official SonicWall support portal (psirt.global.sonicwall.com or support.sonicwall.com).
  5. 5. In the firmware management section, select the option to upload and install the new firmware image.
  6. 6. Follow the on-screen prompts to complete the firmware upgrade process.
  7. 7. After the system reboots, verify the new firmware version is 10.2.1.14-75sv or higher.
  8. 8. Test SSLVPN functionality to ensure the certificate authentication bypass vulnerability is remediated.
Caveat Firmware upgrades may temporarily disrupt VPN connectivity; review release notes for any configuration or feature changes 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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