CVE-2020-35794
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 RBS40V before 2.6.1.4, RBK752 before 3.2.15.25, RBR750 before 3.2.15.25, RBS750 before 3.2.15.25, RBK852 before 3.2.15.25, RBR850 before 3.2.15.25, and RBS850 before 3.2.15.25.
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 Orbi mesh WiFi systems (RBS40V, RBK752, RBR750, RBS750, RBK852, RBR850, RBS850). An attacker with valid admin credentials can inject arbitrary OS commands through insufficiently sanitized input fields in the device's web management 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< 2.6.1.4< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25CVSS 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 the NETGEAR Orbi modelAccess the router's web management interface and look for the model number in the administration settings, or check the device label on the unit itselfAffected if The device model is RBS40V, RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850
-
Check the installed firmware versionLog into the web management interface and navigate to the Administration or Advanced settings section to view the current firmware versionAffected if The firmware version is below 2.6.1.4 for RBS40V, or below 3.2.15.25 for the 750/850 series models
-
Verify web management interface accessibilityConfirm whether the router's web admin interface is accessible from the network by attempting to reach the management IPAffected if The web management interface is exposed and reachable on the network
-
Review admin account configurationCheck the router's admin user accounts in the web interface settings and look for any unauthorized or unexpected accountsAffected if There are unauthorized admin accounts or suspicious session activity present
If the device model matches one of the affected Orbi variants AND the firmware version is below the specified thresholds, the device is vulnerable to authenticated command injection via the web management interface
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 data2.6.1.43.2.15.25
Update firmware to version 2.6.1.4 (RBS40V) or 3.2.15.25 (750/850 series). If immediate patching is not feasible, restrict administrative access to the web interface to trusted IP addresses only and monitor for unauthorized administrative sessions.
- Consultation3.0 h
- Implementation4.0 h
- Testing5.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,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35794 — 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-35794 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