CVE-2020-5146
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 · uneditedA vulnerability in SonicWall SMA100 appliance allow an authenticated management-user to perform OS command injection using HTTP POST parameters. This vulnerability affected SMA100 Appliance version 10.2.0.2-20sv and earlier.
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 confidenceOS command injection vulnerability in SonicWall SMA100 appliance management interface allows authenticated management users to execute arbitrary operating system commands via specially crafted HTTP POST parameters. The vulnerability affects firmware version 10.2.0.2-20sv and all earlier versions.
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<= 10.2.0.2-20svCVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed SMA100 firmware versionAccess the SMA100 appliance management interface and navigate to System > Status or use the CLI command 'version' to display the current firmware version.Affected if The installed version is 10.2.0.2-20sv or any version number lower than 10.2.0.2-20sv.
-
Confirm management interface accessibilityVerify whether the SMA100 web management interface (typically ports 443 or 8443) is reachable from network segments that contain untrusted users.Affected if The management interface is exposed to untrusted or external networks.
-
Review management user authentication logsInspect the SMA100 logs under Diagnostics > Logs or the system log files for authentication events to the management interface, looking for unexpected or unauthorized management user logins.Affected if There are management user login events that you do not recognize or that originate from unexpected sources.
-
Check for anomalous system processes or command executionExamine the appliance for unexpected processes or commands executed by the web server user (typically 'admin' or 'www-data') by reviewing system logs or running process monitoring if accessible via CLI.Affected if There are unusual processes running or commands logged that were not initiated by legitimate administrator activities.
A user is affected if their SonicWall SMA100 appliance runs firmware version 10.2.0.2-20sv or earlier AND has an exposed management interface that could accept the malicious HTTP POST requests.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade SonicWall SMA100 appliance firmware to a version beyond 10.2.0.2-20sv that includes the security patch. Until patched, restrict management interface access to trusted IP addresses and monitor for suspicious activity.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-5146 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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