CVE-2021-20035: Improper neutralization of special elements in the SMA100 management interface allows a remote authenticated attacker to inject arbitrary co
Noroxi assessment
Priority: Plan (action score 57/100)
- CISA has confirmed exploitation in the wild (Apr 16, 2025). Remediation deadline for US federal agencies: May 7, 2025.
- Probability of exploitation in the next 30 days: 4.4% (FIRST EPSS); higher than 91.3% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
Improper neutralization of special elements in the SMA100 management interface allows a remote authenticated attacker to inject arbitrary commands as a 'nobody' user which potentially leads to DoS.
- Published
- Sep 27, 2021
- Updated
- Jun 16, 2026
- EPSS
- 4.4% · 91th percentile
- CWE
- CWE-78
Report tools
Action score
57
Plan
Add it to your regular patch cycle.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 1 / 30 · 4.4%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Apr 16, 2025. That signals real attacks, not theory.
Remediation deadline for US federal agencies: May 7, 2025.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sonicwall | sma 200 firmware | cpe:2.3:o:sonicwall:sma_200_firmware |
| sonicwall | sma 200 | cpe:2.3:h:sonicwall:sma_200 |
| sonicwall | sma 210 firmware | cpe:2.3:o:sonicwall:sma_210_firmware |
| sonicwall | sma 210 | cpe:2.3:h:sonicwall:sma_210 |
| sonicwall | sma 400 firmware | cpe:2.3:o:sonicwall:sma_400_firmware |
| sonicwall | sma 400 | cpe:2.3:h:sonicwall:sma_400 |
| sonicwall | sma 410 firmware | cpe:2.3:o:sonicwall:sma_410_firmware |
| sonicwall | sma 410 | cpe:2.3:h:sonicwall:sma_410 |
| sonicwall | sma 500v | cpe:2.3:a:sonicwall:sma_500v |
Using sma 200 firmware? Add it to your stack and be the first to know about CVEs like this one. (VPN gateway)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sonicwall sma 200 firmwarebefore 9.0.0.11-31sv
- sonicwall sma 200 firmware10.2.0.0 and later · before 10.2.0.8-37sv
- sonicwall sma 200 firmware10.2.1.0 and later · before 10.2.1.1-19sv
- sonicwall sma 210 firmwarebefore 9.0.0.11-31sv
- sonicwall sma 210 firmware10.2.0.0 and later · before 10.2.0.8-37sv
- sonicwall sma 210 firmware10.2.1.0 and later · before 10.2.1.1-19sv
- sonicwall sma 400 firmwarebefore 9.0.0.11-31sv
- sonicwall sma 400 firmware10.2.0.0 and later · before 10.2.0.8-37sv
- sonicwall sma 400 firmware10.2.1.0 and later · before 10.2.1.1-19sv
- sonicwall sma 410 firmwarebefore 9.0.0.11-31sv
- sonicwall sma 410 firmware10.2.0.0 and later · before 10.2.0.8-37sv
- sonicwall sma 410 firmware10.2.1.0 and later · before 10.2.1.1-19sv
- sonicwall sma 500vbefore 9.0.0.11-31sv
- sonicwall sma 500v10.2.0.0 and later · before 10.2.0.8-37sv
- sonicwall sma 500v10.2.1.0 and later · before 10.2.1.1-19sv
Versions reported by the vendor
Affected version ranges reported by the assigning authority (sonicwall). Independent of NVD's CPE analysis and usually ahead of it.
SonicWall SMA100
- 9.0.0.10-28sv and earlier, 10.2.0.7-34sv and earlier, 10.2.1.0-17sv and earlieraffected
Same product
sonicwall: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-20038A Stack-based buffer overflow vulnerability in SMA100 Apache httpd server's mod_cgi module environment variables allows a remote unauthenticKEV99Now
- CVE-2023-44221Improper neutralization of special elements in the SMA100 SSL-VPN management interface allows a remote authenticated attacker with administrKEV81Now
- CVE-2021-20034An improper access control vulnerability in SMA100 allows a remote unauthenticated attacker to bypass the path traversal checks and delete a61This week
Published before and after this one in the same product
- Later →CVE-2021-20039Dec 8, 2021 · Improper neutralization of special elements in the SMA100 management interface '/cgi-bin/viewcert' POST http method allows a remote authenti59Plan
- Later →CVE-2021-20040Dec 8, 2021 · A relative path traversal vulnerability in the SMA100 upload funtion allows a remote unauthenticated attacker to upload crafted web pages or38Monitor
- Later →CVE-2021-20041Dec 8, 2021 · An unauthenticated and remote adversary can consume all of the device's CPU due to crafted HTTP requests sent to SMA100 /fileshare/sonicfile36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- CISA KEV+1296 d
- TodayNov 7, 2026+1867 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;
exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;
if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
execFile("ping", ["-c", "1", host], onResult);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.