dbcve.org
Rbk752 FirmwareOperating system · Netgear

CVE-2021-45584

HIGH · 8.4 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 3.2.16.6 or later.
See remediation →
86/100
Remediation priority · High
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

Command injection vulnerability in NETGEAR Orbi mesh WiFi systems (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) allowing authenticated users to execute arbitrary OS commands via unspecified input fields in the web management interface. The vulnerability affects firmware versions prior to 3.2.16.6.

MitigationUpgrade NETGEAR Orbi firmware to version 3.2.16.6 or later for all affected devices (router and satellites). If immediate patching is not possible, restrict administrative interface access to trusted networks only.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:H/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 exact Orbi model number
    Log into the web management interface and check the device status page, or look at the physical device label for the model number (RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850)
    Affected if The model is any of RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850 and the next check shows a vulnerable firmware version
  2. Check the installed firmware version
    In the web management interface, go to Administration > Firmware Update or Advanced > Administration > Router/Satellite Update to view the current firmware version. Compare it to 3.2.16.6
    Affected if The firmware version displayed is less than 3.2.16.6 (for example, 3.2.14.2 or any version before 3.2.16.6)
  3. Verify the web management interface is accessible
    Attempt to reach the router's web interface by entering the router's IP address in a web browser. Confirm the login page loads
    Affected if The web interface is reachable from a network segment where untrusted users could potentially obtain credentials
  4. Confirm authentication is required for the interface
    Try to access the web management interface without logging in. Observe whether you are redirected to a login page or prompted for credentials
    Affected if The interface allows unauthenticated access to command injection fields (note: the CVE requires authentication, but an exposed unauthenticated interface is a compounding risk)

If the device model is any of the six affected Orbi variants AND the firmware version is below 3.2.16.6, the environment is vulnerable to CVE-2021-45584 command injection.

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

Upgrade NETGEAR Orbi firmware to version 3.2.16.6 or later for all affected devices (router and satellites). If immediate patching is not possible, restrict administrative interface access to trusted networks only.

Recommended fix High confidence

Firmware version 3.2.16.6 or later for Rbk752, Rbr750, Rbs750, Rbk852, Rbr850, Rbs850

  1. 1. Access the NETGEAR router web interface by navigating to the device IP address (typically routerlogin.net or 192.168.1.1)
  2. 2. Log in with administrator credentials
  3. 3. Navigate to the Administration or Settings section
  4. 4. Look for Firmware Update or Router Update option
  5. 5. Check for available updates and upgrade to firmware version 3.2.16.6 or later
  6. 6. Alternatively, download the firmware manually from the NETGEAR support website and upload it through the web interface
  7. 7. After upgrade, verify the firmware version reflects 3.2.16.6 or higher

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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