dbcve.org
Rbk752 FirmwareOperating system · Netgear

CVE-2021-45589

MEDIUM · 6.8 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 3.2.16.6 or later.
See remediation →
70/100
Remediation priority · Elevated
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 authenticated user. This affects RBK752 before 3.2.16.6, RBR750 before 3.2.16.6, RBS750 before 3.2.16.6, RBK852 before 3.2.16.6, RBR850 before 3.2.16.6, and RBS850 before 3.2.16.6.

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

Authenticated command injection vulnerability in NETGEAR Orbi mesh WiFi systems (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) affecting firmware versions prior to 3.2.16.6. An authenticated attacker can execute arbitrary shell commands on the device through the web management interface.

MitigationUpdate affected NETGEAR Orbi devices to firmware version 3.2.16.6 or later to remediate the command injection vulnerability.

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
Rbk752 FirmwareOperating system
Affected:< 3.2.16.6
Rbr750 FirmwareOperating system
Affected:< 3.2.16.6
Rbs750 FirmwareOperating system
Affected:< 3.2.16.6
Rbk852 FirmwareOperating system
Affected:< 3.2.16.6
Rbr850 FirmwareOperating system
Affected:< 3.2.16.6
Rbs850 FirmwareOperating system
Affected:< 3.2.16.6

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

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

  1. Identify Orbi device model
    Check the label on the bottom of the Orbi router or satellite unit, or log into the web management interface and look for the model number displayed on the dashboard or status page. Common model numbers include RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.
    Affected if The model number matches RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.
  2. Check installed firmware version
    Log into the Orbi web management interface (typically at http://192.168.1.1 or http://orbilogin.net). Navigate to the Administration or Advanced settings section and look for Firmware Version or Router Update. Record the exact firmware version number displayed.
    Affected if The firmware version is below 3.2.16.6 (for example, 3.2.14.2, 3.2.15.1, etc.).
  3. Verify web management interface is enabled
    In the Orbi web interface, go to Advanced > Administration > Remote Management or similar. Check if the web management interface is enabled for local or remote access. This is typically controlled by a setting like 'Enable Web Management Interface' or 'Router Access' settings.
    Affected if The web management interface is enabled and accessible (this is the attack surface for the command injection).
  4. Confirm authentication status
    Check whether default administrator credentials are still in use or if the web interface is accessible without authentication. Try accessing the login page and determine if authentication is required.
    Affected if An attacker can obtain valid authentication credentials to access the web management interface, as this vulnerability requires authenticated access.

You are affected if you own an Orbi model RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850 and your firmware version is earlier than 3.2.16.6, with the web management interface enabled and 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.16.6 or later
Fixed in 3.2.16.6
Interim mitigation

Update affected NETGEAR Orbi devices to firmware version 3.2.16.6 or later to remediate the command injection vulnerability.

Recommended fix High confidence

Firmware version 3.2.16.6 for RBK752, RBR750, RBS750, RBK852, RBR850, and RBS850

  1. 1. Identify the exact NETGEAR Orbi model (RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850) that needs remediation.
  2. 2. Navigate to the official NETGEAR support page at kb.netgear.com and locate the firmware download section for your specific model.
  3. 3. Download firmware version 3.2.16.6 (or the latest available version) for your device model.
  4. 4. Access the router's web management interface by entering the router's IP address in a web browser.
  5. 5. Log in with administrative credentials.
  6. 6. Navigate to the Advanced tab, then select Administration > Firmware Update (or similar path depending on the UI).
  7. 7. Click the 'Upload' or 'Browse' button and select the downloaded firmware file (.img or .bin).
  8. 8. Wait for the upload to complete - do not power off the device during this process.
Caveat Firmware upgrades carry inherent risk; ensure stable power during the update process to avoid device corruption

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

Fix this in Rbk752 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-45589 — 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-45589 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