dbcve.org
Sma 200 FirmwareOperating system · Sonicwall

CVE-2021-20044

HIGH · 8.8 CVSS v3.1 Published 2021-12-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 post-authentication remote command injection vulnerability in SonicWall SMA100 allows a remote authenticated attacker to execute OS system commands in the appliance. This vulnerability affected SMA 200, 210, 400, 410 and 500v appliances.

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 post-authentication remote command injection vulnerability in SonicWall SMA100 series (models 200, 210, 400, 410, 500v) allows an authenticated remote attacker to execute arbitrary OS system commands on the appliance through improper input validation.

MitigationApply vendor-supplied patches for SMA 100 series firmware; restrict SMA admin access to trusted users only and monitor for suspicious administrative activity.

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.0.8-37sv= 10.2.1.1-19sv
Sma 210 FirmwareOperating system
Affected:= 10.2.0.8-37sv= 10.2.1.1-19sv
Sma 410 FirmwareOperating system
Affected:= 10.2.0.8-37sv= 10.2.1.1-19sv
Sma 400 FirmwareOperating system
Affected:= 10.2.0.8-37sv= 10.2.1.1-19sv
Sma 500v FirmwareOperating system
Affected:= 10.2.0.8-37sv= 10.2.1.1-19sv

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 SMA100 model
    Access the SonicWall SMA web interface and navigate to Device > Status or check the device label to confirm the model is one of: 200, 210, 400, 410, or 500v
    Affected if The device model is SMA 200, 210, 400, 410, or 500v
  2. Check installed firmware version
    In the SMA web interface, go to Device > Settings > Firmware or System > Status to view the currently installed firmware version
    Affected if The firmware version is 10.2.0.8-37sv or 10.2.1.1-19sv
  3. Verify admin access is enabled
    Check Device > Administrators or Users > Local Users in the SMA interface to confirm admin accounts exist and the management interface is accessible
    Affected if Administrative accounts are present and the admin interface is reachable over the network
  4. Review admin user accounts for unauthorized entries
    Navigate to Device > Administrators and inspect the list of configured administrator accounts for any unknown or suspicious accounts added by an attacker
    Affected if Unexpected administrator accounts are found that were not created by your organization

You are affected if you have a SonicWall SMA 200, 210, 400, 410, or 500v device running firmware version 10.2.0.8-37sv or 10.2.1.1-19sv with administrative access enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches for SMA 100 series firmware; restrict SMA admin access to trusted users only and monitor for suspicious administrative activity.

Recommended fix Moderate confidence

SMA 100 series firmware version 10.2.1.2 or later (latest stable release from SonicWall)

  1. 1. Identify the specific SMA model (200, 210, 400, 410, or 500v) currently deployed
  2. 2. Log into the SMA administrative interface with administrator credentials
  3. 3. Navigate to the System Maintenance or Firmware Update section
  4. 4. Obtain the latest firmware version from the official SonicWall SMA 100 series firmware downloads page at sonicwall.com
  5. 5. Upload and apply the updated firmware to remediate the command injection vulnerability
  6. 6. Verify the firmware upgrade was successful and the appliance is functioning normally
  7. 7. Confirm the new firmware version is no longer 10.2.0.8-37sv or 10.2.1.1-19sv
  8. 8. Test that the SMA functionality remains operational post-upgrade
Caveat Standard firmware upgrade risks apply - ensure backup of configuration and plan for brief downtime during upgrade process

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 / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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