CVE Intelligence
CISA KEV High Injection

CVE-2023-44221 — SonicWall SMA100 Appliances OS Command Injection Vulnerability

Improper neutralization of special elements in the SMA100 SSL-VPN management interface allows a remote authenticated attacker with administrative privilege to inject arbitrary commands as a 'nobody' user, potentially leading to OS Command Injection Vulnerability.

Published Dec 5, 2023 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: sonicwall

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · May 1, 2025
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 76.3% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed May 1, 2025
EPSS FIRST
76.25%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
Sonicwall
Sma 200 Firmware and 5 more
CVSS base
7.2
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

US federal deadline: May 22, 2025 — passed 511 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Sonicwall Sma 200 Firmware, Sonicwall Sma 210 Firmware, Sonicwall Sma 400 Firmware…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Sonicwall Sma 200 Firmware ≤ 10.2.1.9-57sv Vulnerable NIST National Vulnerability Database
Sonicwall Sma 210 Firmware ≤ 10.2.1.9-57sv Vulnerable NIST National Vulnerability Database
Sonicwall Sma 400 Firmware ≤ 10.2.1.9-57sv Vulnerable NIST National Vulnerability Database
Sonicwall Sma 410 Firmware ≤ 10.2.1.9-57sv Vulnerable NIST National Vulnerability Database
Sonicwall Sma 500v Firmware ≤ 10.2.1.9-57sv Vulnerable NIST National Vulnerability Database
Sonicwall SMA100 version 10.2.1.9-57sv and earlier versions Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.2 CVSS 3.1 High 1.2 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.2 CVSS 3.1 High 1.2 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.2 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.2 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
May 1, 2025
Federal deadline
May 22, 2025
passed 511 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 76.25%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
  • Hunt retroactively in logs from before May 1, 2025 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · sonicwall/sma100
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · sonicwall/sma 200 firmware, sonicwall/sma 210 firmware, sonicwall/sma 400 firmware, sonicwall/sma 410 firmware, sonicwal
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.2
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2025
  • Added to CISA KEV catalog
    Apr 30, 2025 · CISA
  • 2023
  • CVE published
    Dec 5, 2023 · sonicwall

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Sonicwall
every CVE for this vendor
2025-05
what else CISA listed that month
Injection
same class
CWE-78
other pages naming this weakness

Related CVEs (same products)

  • CVE-2025-40603 Insertion of Sensitive Information into Log File in Sonicwall Sma 210 Firmware Oct 31, 2025
  • CVE-2024-38475 Apache HTTP Server Improper Escaping of Output Vulnerability KEV Jul 1, 2024
  • CVE-2021-20038 SonicWall SMA 100 Appliances Stack-Based Buffer Overflow Vulnerability KEV Dec 8, 2021
  • CVE-2021-20035 SonicWall SMA100 Appliances OS Command Injection Vulnerability KEV Sep 27, 2021
  • CVE-2021-20028 SonicWall Secure Remote Access (SRA) SQL Injection Vulnerability KEV Aug 4, 2021
  • CVE-2021-20016 SonicWall SSLVPN SMA100 SQL Injection Vulnerability KEV Feb 4, 2021

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2023-44221 is "SonicWall SMA100 Appliances OS Command Injection Vulnerability", rated High. It affects Sma 200 Firmware (Sonicwall); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.2 describes technical severity. EPSS 76.25% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.