CVE-2020-35791
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 · uneditedCertain NETGEAR devices are affected by command injection by an authenticated user. This affects R7800 before 1.0.2.68, R8900 before 1.0.5.2, and R9000 before 1.0.5.2.
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 confidenceAuthenticated command injection vulnerability in NETGEAR R7800, R8900, and R9000 routers allows an authenticated attacker to execute arbitrary commands on the underlying operating system due to insufficient input validation in the web interface.
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.0.2.68< 1.0.5.2< 1.0.5.2CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify router modelAccess the router web interface and navigate to the Administration or Settings section to view the model number, or check the device label on the router itselfAffected if Router is not a Netgear R7800, R8900, or R9000 model (these are the only affected models)
-
Determine firmware versionIn the router web interface, go to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware versionAffected if Unable to determine firmware version from router interface
-
Compare R7800 firmware to affected rangeIf model is R7800, compare installed version against 1.0.2.68 - any version lower than 1.0.2.68 is affectedAffected if R7800 firmware version is below 1.0.2.68
-
Compare R8900 firmware to affected rangeIf model is R8900, compare installed version against 1.0.5.2 - any version lower than 1.0.5.2 is affectedAffected if R8900 firmware version is below 1.0.5.2
-
Compare R9000 firmware to affected rangeIf model is R9000, compare installed version against 1.0.5.2 - any version lower than 1.0.5.2 is affectedAffected if R9000 firmware version is below 1.0.5.2
Environment is affected if the router model is R7800, R8900, or R9000 AND the installed firmware version is lower than 1.0.2.68 (R7800) or 1.0.5.2 (R8900/R9000).
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.0.2.681.0.5.2
Update NETGEAR router firmware to version 1.0.2.68 or later (R7800) or 1.0.5.2 or later (R8900/R9000). Restrict administrative access to trusted users and networks.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35791 — 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-35791 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