dbcve.org
Sma 6200 FirmwareOperating system · Sonicwall

CVE-2022-22282

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
SonicWall SMA1000 series firmware 12.4.0, 12.4.1-02965 and earlier versions incorrectly restricts access to a resource using HTTP connections from an unauthorized actor leading to Improper Access Control vulnerability.

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

The SonicWall SMA1000 series appliances running firmware 12.4.0 through 12.4.1-02965 contain an improper access control vulnerability where HTTP connections from unauthorized actors can access protected resources. This allows remote attackers to bypass authentication and access sensitive functionality without proper authorization.

MitigationUpdate SonicWall SMA1000 firmware to version 12.4.2 or later. If immediate patching is not feasible, restrict network access to the management interface and implement additional network segmentation to limit exposure to untrusted networks.

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 6200 FirmwareOperating system
Affected:= 12.4.0= 12.4.1
Sma 6210 FirmwareOperating system
Affected:= 12.4.0= 12.4.1
Sma 7200 FirmwareOperating system
Affected:= 12.4.0= 12.4.1
Sma 7210 FirmwareOperating system
Affected:= 12.4.0= 12.4.1
Sma 8000v FirmwareOperating system
Affected:= 12.4.0= 12.4.1

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

CVSS:3.1/AV:N/AC:L/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 SMA100 appliance model
    Log into the SonicWall SMA web management interface and navigate to System > Status or check the device label/hardware model to confirm it is one of: SMA 6200, SMA 6210, SMA 7200, SMA 7210, or SMA 8000v.
    Affected if model is one of the five listed SMA1000 series appliances
  2. Check the installed firmware version
    In the SMA web interface, go to System > Status or About page to view the current firmware version. Alternatively, access the device via SSH and run the command 'version' or 'show version' to retrieve the firmware build number.
    Affected if firmware version displayed is 12.4.0 or 12.4.1 (including any 12.4.1-xxxxx subversions up to 12.4.1-02965)
  3. Verify HTTP management interface is accessible
    Confirm that the SMA web management interface is reachable via HTTP (port 80) or HTTPS (port 443) from the network segment being assessed. The vulnerability permits unauthorized HTTP access to protected resources without authentication.
    Affected if the management interface is exposed on any network accessible to untrusted actors

The environment is affected if the SonicWall SMA1000 model is a 6200, 6210, 7200, 7210, or 8000v running firmware version 12.4.0 or 12.4.1, and the HTTP management interface is network-accessible.

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

Update SonicWall SMA1000 firmware to version 12.4.2 or later. If immediate patching is not feasible, restrict network access to the management interface and implement additional network segmentation to limit exposure to untrusted networks.

Recommended fix Moderate confidence

Latest available firmware version after 12.4.1-02965 (check SonicWall PSIRT for exact fixed release)

  1. 1. Navigate to the SonicWall SMA 100 series support page at psirt.global.sonicwall.com
  2. 2. Locate the security advisory for CVE-2022-22282
  3. 3. Download the latest available firmware version for your specific SMA model (6200, 6210, 7200, 7210, or 8000v)
  4. 4. Review the firmware release notes to confirm it includes the fix for CVE-2022-22282
  5. 5. Back up the current SMA appliance configuration
  6. 6. Upload and apply the new firmware through the SMA administrative web interface or via CLI
  7. 7. Verify the firmware upgrade was successful and the appliance is operational
  8. 8. Confirm the firmware version matches the patched release
Caveat Review release notes for any configuration changes or feature modifications between versions; test in non-production environment first

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

Fix this in Sma 6200 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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