dbcve.org
Sma 200 FirmwareOperating system · Sonicwall

CVE-2024-53702

MEDIUM · 5.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 →
62/100
Remediation priority · Elevated
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
Use of cryptographically weak pseudo-random number generator (PRNG) vulnerability in the SonicWall SMA100 SSLVPN backup code generator that, in certain cases, can be predicted by an attacker, potentially exposing the generated secret.

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

The SonicWall SMA100 SSLVPN backup code generator uses a cryptographically weak pseudo-random number generator (PRNG). In certain configurations or conditions, an attacker could predict the generated secret codes due to insufficient randomness, potentially gaining unauthorized access or exposing sensitive backup credentials.

MitigationApply available vendor patches for the SMA100 series. If no patch exists, consider using alternative authentication mechanisms for VPN access and monitor for unauthorized access attempts using the backup code feature.

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

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

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 your SMA device model
    Log into the SMA web management interface and check the Dashboard or Status page, or run 'show system-info' via CLI
    Affected if Device is not one of SMA 200, 210, 400, 410, or 500v (these are the only affected models)
  2. Check installed firmware version
    In the SMA web UI, go to Device > Settings > Firmware or run 'version' via CLI. Compare the displayed firmware version against 10.2.1.14-75sv
    Affected if Firmware version is below 10.2.1.14-75sv on an affected model
  3. Verify backup code feature is configured
    In the SMA web UI, navigate to SSL-VPN > Client Settings or Users > Backup Codes. Check if any backup codes have been generated or if the backup code authentication method is enabled
    Affected if Backup codes are generated or the backup code authentication method is active on the device
  4. Check authentication settings for backup code usage
    Go to Users > Local Users or Authentication > Methods and inspect whether 'Backup Code' or 'One Time Password' backup methods are enabled for any user accounts
    Affected if Backup code authentication is enabled for any user accounts on the SMA device

You are affected if your device is an SMA 200, 210, 400, 410, or 500v running firmware below 10.2.1.14-75sv and the backup code feature is configured or active.

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 available vendor patches for the SMA100 series. If no patch exists, consider using alternative authentication mechanisms for VPN access and monitor for unauthorized access attempts using the backup code feature.

Recommended fix High confidence

Firmware 10.2.1.14-75sv or later

  1. 1. Identify the specific SMA device model (200, 210, 400, 410, or 500v) from the affected product list
  2. 2. Access the SMA device management interface via web browser
  3. 3. Navigate to the System Maintenance or Firmware Update section
  4. 4. Download firmware version 10.2.1.14-75sv (or later) from the official SMA vendor support portal
  5. 5. Upload the firmware file to the device and initiate the update
  6. 6. Wait for the device to reboot and apply the new firmware
  7. 7. Verify the firmware version has been updated to 10.2.1.14-75sv or later in the device status
Caveat Review vendor 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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