CVE-2021-29071
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 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, RBR752 before 3.2.17.12, RBR753 before 3.2.17.12, RBR753S before 3.2.17.12, RBR754 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 confidenceCommand injection vulnerability in NETGEAR Orbi mesh WiFi systems (RBK852, RBK853, RBK854, RBR850, RBS850, RBR752, RBR753, RBR753S, RBR754, RBR750, RBS750) allows authenticated users to execute arbitrary commands via insufficient input validation in the web management interface. The vulnerability affects firmware versions prior to 3.2.17.12.
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< 3.2.17.12< 3.2.17.12< 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 on the device label or log into the web management interface and check the device status page for the exact model designation (RBK852, RBK853, RBK854, RBR850, RBS850, RBR752, RBR753, RBR753S, RBR754, RBR750, or RBS750)Affected if The device model matches one of the listed vulnerable models
-
Check the current firmware versionLog into the Orbi web management interface (typically at 192.168.1.1 or orbilogin.com) and navigate to Administration > Firmware Update or the device status section to view the installed firmware versionAffected if The installed firmware version is lower than 3.2.17.12 (for example, 3.2.16.14 or earlier)
-
Verify remote web management is accessibleAttempt to access the Orbi web interface from an external network or check the router port forwarding/settings for HTTP/HTTPS ports (80/443) forwarded to the Orbi deviceAffected if The web management interface is exposed to untrusted networks
-
Confirm administrative access is availableAttempt to log into the Orbi admin interface using the configured administrator credentialsAffected if Valid administrative credentials can be used to access the web management interface
The environment is affected if the device is an Orbi model from the list and runs firmware version 3.2.17.12 or lower, with the web management interface accessible to an authenticated attacker.
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 · scoped3.2.17.12
Update NETGEAR Orbi devices to firmware version 3.2.17.12 or later to remediate the command injection vulnerability. If immediate patching is not possible, restrict administrative access to trusted users only and monitor for suspicious activity.
Firmware version 3.2.17.12 or later for affected Orbi models (RBK852, RBK853, RBK854, RBR850, RBS850, RBR752, RBR753, RBR753S, RBR754, RBR750, RBS750)
- 1. Access the NETGEAR Orbi web management interface by entering the router's IP address in a web browser
- 2. Log in with administrator credentials
- 3. Navigate to the Administration or Settings section
- 4. Look for Firmware Update or Router Update option
- 5. Select Check for Updates or manually upload firmware version 3.2.17.12 or later
- 6. Wait for the firmware upload and installation to complete - do not power off the device during this process
- 7. The device will automatically reboot after the update
- 8. Verify the firmware version has been updated to 3.2.17.12 or later in the administration interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29071 — 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-29071 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