dbcve.org
Sma 200 FirmwareOperating system · Sonicwall

CVE-2021-20043

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 Heap-based buffer overflow vulnerability in SonicWall SMA100 getBookmarks method allows a remote authenticated attacker to potentially execute code as the nobody user 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 · moderate confidence

A heap-based buffer overflow vulnerability exists in the getBookmarks method of SonicWall SMA 100 series appliances (models 200, 210, 400, 410, and 500v). An attacker with valid authentication credentials can trigger the overflow to achieve code execution, though limited to the low-privilege 'nobody' user context.

MitigationApply the vendor-supplied firmware update for affected SMA 100 series appliances. If a patch is unavailable, consider network segmentation to limit exposure and monitor for indicators of compromise.

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 the SMA 100 series model
    Access the appliance web interface and navigate to the dashboard or system status page to confirm the exact model (SMA 200, 210, 400, 410, or 500v). Alternatively, check the physical device label or use the CLI command 'get system info' or similar.
    Affected if The device is one of the following models: SMA 200, SMA 210, SMA 400, SMA 410, or SMA 500v.
  2. Check the installed firmware version
    In the web interface, go to System > Administration or System > Firmware to view the current firmware version. From CLI, use 'show version' or 'firmware show'.
    Affected if The firmware version is exactly 10.2.0.8-37sv or 10.2.1.1-19sv.
  3. Verify the getBookmarks feature is accessible
    The getBookmarks method is accessed via the web interface. Attempt to access the bookmarks or saved connections functionality through the SMA web portal. This is a built-in feature of the SMA 100 series and is present by default.
    Affected if The web interface is accessible and the bookmarks/connections feature is available to authenticated users.
  4. Confirm remote access is enabled
    Check System > Access Settings or similar in the web interface to see if the SMA web interface is exposed to network access. Also verify if VPN or Connect Tunnel features are enabled, as these provide authentication paths.
    Affected if The SMA web interface is network-accessible and accepts authentication, allowing a valid user to reach the getBookmarks function.

You are affected if you have an SMA 200, 210, 400, 410, or 500v device running firmware version 10.2.0.8-37sv or 10.2.1.1-19sv, with the web interface accessible to an authenticated user who can reach the getBookmarks functionality.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware update for affected SMA 100 series appliances. If a patch is unavailable, consider network segmentation to limit exposure and monitor for indicators of compromise.

Fix this in Sma 200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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