CVE-2020-35789
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 · uneditedNETGEAR NMS300 devices before 1.6.0.27 are affected by command injection by an authenticated user.
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 confidenceNETGEAR NMS300 (Network Management System 300) devices before version 1.6.0.27 contain a command injection vulnerability that allows authenticated users to execute arbitrary operating system commands on the underlying device, likely through insufficient input validation in web interface parameters.
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< 1.6.0.27CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm NMS300 is deployedCheck for NETGEAR NMS300 Network Management System installation in your environment - look for the application process, service, or associated directories on the deviceAffected if NMS300 is not installed or not in use, the vulnerability does not apply
-
Identify firmware versionAccess the NMS300 web interface admin console and navigate to the system information or about page, or check the system version through the administration interface to determine the installed firmware versionAffected if Installed version is less than 1.6.0.27 - the command injection vulnerability is present
-
Verify web interface accessibilityConfirm the NMS300 web management interface (typically on ports 80/443 or custom ports) is accessible on the deviceAffected if The web interface must be accessible for the vulnerable parameters to be exploitable; if disabled, the attack surface is reduced but the flaw still exists in the code
-
Check authentication statusReview user authentication settings in the NMS300 administration panel to determine if authentication is required for web interface access and identify valid user accountsAffected if Authenticated access to the web interface is required to exploit this command injection flaw - the vulnerability affects authenticated users
Your environment is affected if NETGEAR NMS300 is deployed with a firmware version earlier than 1.6.0.27 and the web interface is accessible to authenticated users.
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 data1.6.0.27
Upgrade NETGEAR NMS300 to version 1.6.0.27 or later to patch the command injection vulnerability. Additionally, review user accounts and restrict administrative access to minimize the impact of credential compromise.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35789 — 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-35789 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