dbcve.org
Sws12 10fpoe FirmwareOperating system · Sonicwall

CVE-2022-2323

HIGH · 8.8 CVSS v3.1 Published 2022-07-29
Fix available
A fix is available. Upgrade to 1.2.0.0-3 or later.
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
Improper neutralization of special elements used in a user input allows an authenticated malicious user to perform remote code execution in the host system. This vulnerability impacts SonicWall Switch 1.1.1.0-2s and earlier versions

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

Command injection vulnerability in SonicWall Switch firmware allowing authenticated users to execute arbitrary system commands through unsanitized user input. The improper neutralization of special elements in user-supplied data enables remote code execution on the affected device.

MitigationUpdate SonicWall Switch firmware to a version beyond 1.1.1.0-2s that addresses this vulnerability. Limit administrative access to trusted, authenticated users only 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
Sws12 10fpoe FirmwareOperating system
Affected:< 1.2.0.0-3
Sws12 8 FirmwareOperating system
Affected:< 1.2.0.0-3
Sws12 8poe FirmwareOperating system
Affected:< 1.2.0.0-3
Sws14 24 FirmwareOperating system
Affected:< 1.2.0.0-3
Sws14 24fpoe FirmwareOperating system
Affected:< 1.2.0.0-3
Sws14 48 FirmwareOperating system
Affected:< 1.2.0.0-3
Sws14 48fpoe FirmwareOperating system
Affected:< 1.2.0.0-3

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 your SonicWall Switch model
    Log into the switch web interface or CLI and locate the model number. Look for SWS12 or SWS14 series identifiers such as 8, 8poe, 10fpoe, 24, 24fpoe, 48, or 48fpoe in the device information or system status page.
    Affected if The model matches any of the following: Sws12 10fpoe, Sws12 8, Sws12 8poe, Sws14 24, Sws14 24fpoe, Sws14 48, or Sws14 48fpoe
  2. Locate the firmware version information
    In the switch web interface, navigate to System > About or System > Firmware. In CLI, use the 'show version' or 'show system-info' command.
    Affected if You are unable to retrieve firmware version information from the device
  3. Compare installed firmware version to affected range
    Note the exact firmware version displayed. Compare it numerically against version 1.2.0.0-3. Versions follow the format major.minor.patch-build (for example, 1.1.1.0-2s or 1.2.0.0-3).
    Affected if The firmware version is less than 1.2.0.0-3 (for example, 1.1.1.0-2s, 1.0.0.0-1, or any version starting with 1.1.x)

You are affected if you have a SonicWall SWS12 or SWS14 series switch running firmware version lower than 1.2.0.0-3 and the device management interface is accessible to authenticated users.

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 1.2.0.0-3 or later
Fixed in 1.2.0.0-3
Interim mitigation

Update SonicWall Switch firmware to a version beyond 1.1.1.0-2s that addresses this vulnerability. Limit administrative access to trusted, authenticated users only to reduce attack surface.

Recommended fix High confidence

Firmware version 1.2.0.0-3 or later for Sws12 and Sws14 switch models

  1. 1. Identify the specific Sws12 or Sws14 switch model in your environment
  2. 2. Document the current firmware version by accessing the switch management interface or using CLI commands
  3. 3. Download the firmware version 1.2.0.0-3 or later from the official SonicWall support portal (psirt.global.sonicwall.com)
  4. 4. Review the SonicWall firmware upgrade guide for the specific switch model
  5. 5. Upload the new firmware file through the switch web interface or TFTP/FTP method
  6. 6. Verify the firmware upgrade completed successfully and the switch is operational
  7. 7. Confirm the running firmware version is 1.2.0.0-3 or later
Caveat Standard firmware upgrade risks apply - ensure backup of configuration and plan for brief downtime

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

Fix this in Sws12 10fpoe Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
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,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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