dbcve.org
Rbk852 FirmwareOperating system · Netgear

CVE-2021-29078

CRITICAL · 9.6 CVSS v3.1 Published 2021-03-23
Fix available
A fix is available. Upgrade to 3.2.17.12 or later.
See remediation →
100/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
Certain NETGEAR devices are affected by command injection by an unauthenticated attacker. 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, 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 confidence

Unauthenticated command injection vulnerability in NETGEAR Orbi mesh WiFi systems (multiple models RBK752-RBK854, RBR750-RBR850, RBS750-S850) allowing remote attackers to execute arbitrary operating system commands via the web interface prior to firmware version 3.2.17.12.

MitigationApply NETGEAR firmware version 3.2.17.12 or later to all affected Orbi devices. If patching is not immediately possible, restrict network access to the management interface using firewall rules or VLAN isolation.

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
Rbk852 FirmwareOperating system
Affected:< 3.2.17.12
Rbk853 FirmwareOperating system
Affected:< 3.2.17.12
Rbk854 FirmwareOperating system
Affected:< 3.2.17.12
Rbr850 FirmwareOperating system
Affected:< 3.2.17.12
Rbs850 FirmwareOperating system
Affected:< 3.2.17.12
Rbk752 FirmwareOperating system
Affected:< 3.2.17.12
Rbk753 FirmwareOperating system
Affected:< 3.2.17.12
Rbk753s FirmwareOperating system
Affected:< 3.2.17.12

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Orbi model
    Log into the Orbi web admin interface (typically 192.168.1.1 or orbilogin.com) and locate the model number in the device status or administration section. Alternatively, check the physical device label on the router or satellite unit.
    Affected if The model is one of: RBK752, RBK753, RBK753S, RBK852, RBK853, RBK854, RBR850, or RBS850.
  2. Check the installed firmware version
    In the Orbi web admin interface, navigate to the Administration or Settings section and locate the firmware version information. Note the exact version number displayed.
    Affected if The firmware version is lower than 3.2.17.12 (for example, 3.2.16.14 or earlier).
  3. Verify web management interface is accessible
    Attempt to access the Orbi web admin interface from the network. Confirm the login page loads at the device IP address (commonly 192.168.1.1) or orbilogin.com.
    Affected if The web interface is reachable on the network without authentication restrictions, indicating the attack surface is exposed.

The device is affected if it is an Orbi model from the listed series AND is running firmware version 3.2.17.11 or lower, with the web management interface network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.2.17.12 or later
Fixed in 3.2.17.12
Interim mitigation

Apply NETGEAR firmware version 3.2.17.12 or later to all affected Orbi devices. If patching is not immediately possible, restrict network access to the management interface using firewall rules or VLAN isolation.

Recommended fix High confidence

Upgrade to firmware version 3.2.17.12 or later

  1. 1. Identify your exact NETGEAR Orbi model number (RBR850, RBS850, RBK852, RBK853, RBK854, RBK752, RBK753, RBK753S, RBK754, RBR750, or RBS750)
  2. 2. Access the Orbi web interface or mobile app
  3. 3. Navigate to Settings > Administration > Firmware Update
  4. 4. Check the current firmware version under the Router Info section
  5. 5. If the firmware version is lower than 3.2.17.12, select Check for Update or manually download the firmware from the NETGEAR support website
  6. 6. Apply the firmware update and wait for the device to reboot
  7. 7. After reboot, verify the firmware version is now 3.2.17.12 or later
Caveat Firmware updates may temporarily interrupt network connectivity; ensure stable power during the update process

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rbk852 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-29078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-29078 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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