dbcve.org
Sma 200 FirmwareOperating system · Sonicwall

CVE-2024-53703

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 firmware 10.2.1.13-72sv and earlier versions mod_httprp library loaded by the Apache web server 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 · high confidence

A stack-based buffer overflow vulnerability exists in the mod_httprp library of the Apache web server bundled with SonicWall SMA100 SSLVPN firmware versions 10.2.1.13-72sv and earlier. This memory corruption flaw can potentially allow remote attackers to execute arbitrary code on the affected appliance.

MitigationApply the vendor-supplied firmware patch to upgrade to a version beyond 10.2.1.13-72sv. If immediate patching is not feasible, restrict SSLVPN access to trusted IP ranges via firewall rules to reduce attack surface.

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
    Log into the SonicWall SMA web management interface and locate the Device > Status page, or use the CLI command 'show system info' to confirm the hardware model (SMA 200, 210, 400, 410, or 500v).
    Affected if The device is one of the five affected models (SMA 200, 210, 400, 410, or 500v).
  2. Check the installed firmware version
    In the web interface, go to Device > Status and locate the Firmware Version field, or run the CLI command 'show version' to retrieve the exact firmware build number.
    Affected if The firmware version is 10.2.1.13-72sv or any earlier version (versions below 10.2.1.14-75sv).
  3. Verify the Apache mod_httprp module is active
    Access the SMA CLI and run 'httpd -M 2>/dev/null | grep httprp' or check the Apache configuration files in /etc/httpd/conf.d/ for the mod_httprp module being loaded.
    Affected if The mod_httprp module is loaded and the firmware version is in the vulnerable range.

A user is affected if their SMA device model is one of the five listed and the installed firmware version is less than 10.2.1.14-75sv.

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 firmware patch to upgrade to a version beyond 10.2.1.13-72sv. If immediate patching is not feasible, restrict SSLVPN access to trusted IP ranges via firewall rules to reduce attack surface.

Recommended fix Moderate confidence

Firmware version 10.2.1.14-75sv for SMA 200, 210, 400, 410, and 500v

  1. Obtain the fixed firmware version 10.2.1.14-75sv from the official SonicWall support portal or the psirt.global.sonicwall.com reference source
  2. Review the SMA 100 Series firmware upgrade guide for your specific model (200, 210, 400, 410, or 500v)
  3. Create a backup of the current configuration before proceeding with the upgrade
  4. Upload the firmware file 10.2.1.14-75sv through the SMA web management interface or appropriate update mechanism
  5. Verify the upgrade was successful and confirm the new firmware version is running
  6. Test that SSLVPN functionality and all dependent services are operating normally after the upgrade
Caveat Firmware upgrades carry inherent risk; ensure backup and test in staging environment before production deployment if possible

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

Fix this in Sma 200 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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