IRONSMITHINTEL
CRITICALCVSS9.8
|
Actively Exploited
|CISA KEV|CVE-2021-20028|Auth: none — unauthenticated|Reboot: required|Manual only

SonicWall Secure Remote Access (SRA) SQL Injection Vulnerability (CVE-2021-20028)

SonicWall Secure Remote Access (SRA) products contain an improper neutralization of a SQL Command leading to SQL injection.

Published Aug 4, 2021 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. CISA has confirmed use of this vulnerability in known ransomware campaigns — treat as high priority for remediation. Federal agencies are required to remediate by 2022-04-18 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a SQL Injection (CWE-89) vulnerability in SonicWall Secure Remote Access (SRA). Improper neutralization of a SQL Command leading to SQL Injection vulnerability impacting end-of-life Secure Remote Access (SRA) products, specifically the SRA appliances running all 8.x firmware and 9.0.0.9-26sv or earlier Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

→

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

●IT Security
●Running sma 210 firmware: 8.0.0.0 ≤ v < 9.0.0.10-28sv; sma 410 firmware: 8.0.0.0 ≤ v < 9.0.0.10-28sv; sma 500v firmware: 8.0.0.0 ≤ v < 9.0.0.10-28sv; sra 4600 firmware: 8.0.0.0 ≤ v < 9.0.0.10-28sv; sra 1600 firmware: 8.0.0.0 ≤ v < 9.0.0.10-28sv; sra va firmware: 8.0.0.0 ≤ v < 9.0.0.10-28sv
Real-world incidentsWhat we've seen

CISA confirms this CVE has been used in known ransomware campaigns. Added to the KEV catalog on 2022-03-28; federal agencies required to remediate by 2022-04-18.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for network-security installs in scope.
2
Apply the vendor security update referenced in CVE-2021-20028's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2021-20028↗ MSRC Advisory↗ NVD↗ Vendor Advisory