CVE-2021-29077
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 unauthenticated attacker. This affects RBW30 before 2.6.2.2, RBS40V before 2.6.2.4, RBK852 before 3.2.17.12, RBK853 before 3.2.17.12, RBK854 before 3.2.17.12, RBR850 before 3.2.17.12, RBS850 before 3.2.17.12, RBK752 before 3.2.17.12, RBK753 before 3.2.17.12, RBK753S before 3.2.17.12, RBK754 before 3.2.17.12, RBR750 before 3.2.17.12, and RBS750 before 3.2.17.12.
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 confidenceUnauthenticated command injection vulnerability in NETGEAR Orbi mesh WiFi systems (RBW30, RBS40V, RBK852, RBK853, RBK854, RBR850, RBS850, RBK752, RBK753, RBK753S, RBK754, RBR750, RBS750) allows remote attackers to execute arbitrary operating system commands via unspecified vectors.
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.2.2< 2.6.2.4< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12CVSS 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/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 Orbi device modelLocate the model number label on the device or access the router admin UI and check the device info page. The affected models are: RBW30, RBS40V, RBK852, RBK853, RBK854, RBR850, RBS850, RBK752, RBK753, RBK753S, RBR750, RBS750.Affected if The device model matches one of the listed affected models.
-
Determine the installed firmware versionAccess the Orbi web admin interface (typically at 192.168.1.1 or orbilogin.com). Navigate to Administration > Firmware Update or Advanced > Administration > Firmware version. Alternatively, use the Orbi app and check the device settings for firmware information.Affected if Unable to confirm firmware version or version is below the threshold.
-
Compare firmware version against affected rangesMatch your identified model and firmware version against: RBW30 < 2.6.2.2, RBS40V < 2.6.2.4, RBK852/RBK853/RBK854/RBR850/RBS850/RBK752 < 3.2.17.12. For RBK753, RBK753S, RBK754, RBR750, RBS750, treat any version below 3.2.17.12 as potentially affected since no specific fix version was listed in the advisory.Affected if Installed firmware version is below the corresponding threshold for your model.
-
Verify network exposureDetermine if the Orbi device management interface is accessible from the internet (check port forwarding rules, WAN-facing IP exposure, or exposed management ports).Affected if The device admin interface is reachable from untrusted networks, increasing the likelihood of remote exploitation.
A defender is affected if they run any of the listed Orbi models (RBW30, RBS40V, RBK852, RBK853, RBK854, RBR850, RBS850, RBK752, RBK753, RBK753S, RBR750, RBS750) with firmware versions below 2.6.2.2 (RBW30), 2.6.2.4 (RBS40V), or 3.2.17.12 (all other models).
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.
dbcve · scoped2.6.2.22.6.2.43.2.17.12
Apply vendor-supplied firmware updates (2.6.2.2 for RBW30, 2.6.2.4 for RBS40V, 3.2.17.12 for all other affected models). If immediate patching is not feasible, isolate affected devices from untrusted networks to reduce exposure.
RBW30: 2.6.2.2 | RBS40V: 2.6.2.4 | All others (RBK852/853/854, RBR850, RBS850, RBK752/753/753S/754, RBR750, RBS750): 3.2.17.12
- 1. Identify the exact NETGEAR device model from the affected list (RBW30, RBS40V, RBK852, RBK853, RBK854, RBR850, RBS850, RBK752, RBK753, RBK753S, RBK754, RBR750, or RBS750)
- 2. Access the device admin interface or NETGEAR Nighthawk/Orbi app
- 3. Navigate to Settings > Administration > Firmware Update, or check for updates automatically
- 4. Download and install the appropriate firmware version for your device model
- 5. For RBW30, upgrade to firmware version 2.6.2.2 or later
- 6. For RBS40V, upgrade to firmware version 2.6.2.4 or later
- 7. For all other affected models (RBK852, RBK853, RBK854, RBR850, S850, RBK752, RBK753, RBK753S, RBK754, RBR750, RBS750), upgrade to firmware version 3.2.17.12 or later
- 8. After upgrade, verify the device is functioning normally and confirm the firmware version was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29077 — 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-2021-29077 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