CVE-2020-35792
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 R7500v2 before 1.0.3.48, R8900 before 1.0.5.2, R9000 before 1.0.5.2, and R7800 before 1.0.2.68.
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 router web interfaces (R7500v2, R8900, R9000, R7800). An authenticated attacker can inject arbitrary OS commands through the management interface due to insufficient input sanitization.
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.3.48< 1.0.5.2< 1.0.5.2< 1.0.2.68CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 modelLocate the model number on the router device label or log into the web management interface and check the status or administration page for the exact model designation (R7500v2, R7800, R8900, or R9000).Affected if Model is one of R7500v2, R7800, R8900, or R9000.
-
Check firmware versionLog into the router web interface, navigate to the Administration or Firmware Upgrade section, and locate the currently installed firmware version displayed on the status or router information page.Affected if Firmware version is below 1.0.3.48 for R7500v2, below 1.0.5.2 for R8900/R9000, or below 1.0.2.68 for R7800.
-
Verify web management interface is enabledCheck the router's remote management settings (typically under Advanced > Administration > Remote Management) to determine if the web management interface is enabled, and note whether it is accessible from the WAN/internet or LAN only.Affected if The web management interface is enabled and accessible, particularly from WAN.
-
Confirm authentication statusDetermine whether valid admin credentials exist for the router (default credentials may still be in use or credentials may have been changed). The vulnerability requires valid authentication to exploit.Affected if Admin credentials are configured and known, enabling authenticated access to the management interface.
A user is affected if they own an R7500v2, R7800, R8900, or R9000 router running firmware below the respective fixed version and have the web management interface accessible with valid credentials.
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.3.481.0.5.2
Update router firmware to versions 1.0.3.48 (R7500v2), 1.0.5.2 (R8900/R9000), or 1.0.2.68 (R7800) or later to patch the command injection vulnerability.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35792 — 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-35792 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