dbcve.org
Rbk752 FirmwareOperating system · Netgear

CVE-2021-45560

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

This is an authenticated command injection vulnerability in NETGEAR Orbi mesh WiFi systems (models RBK752, RBR750, RBS750, RBK852, RBR850, RBS850). An authenticated attacker can inject and execute arbitrary operating system commands through unsanitized input, potentially gaining full control of the affected device.

MitigationUpdate the firmware on all affected NETGEAR Orbi devices to version 3.2.16.6 or later. Additionally, restrict administrative access to trusted users only and use strong, unique credentials to limit the attack surface.

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 the Orbi device model
    Access the router admin web interface and navigate to Settings > About or check the product label on the device. Alternatively, log into the router via telnet or SSH and run 'cat /proc/cpuinfo' or 'nvram get model' to retrieve the model number.
    Affected if The model is one of: RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.
  2. Check the firmware version
    In the router admin web interface, go to Settings > Administration > Firmware Update or the About page. The current firmware version is displayed there. Compare this version number to 3.2.16.6.
    Affected if The installed firmware version is lower than 3.2.16.6 (for example, 3.2.14.2, 3.2.15.1, etc.).
  3. Verify remote administration access settings
    In the router admin web interface, go to Settings > Administration > Remote Management or Access Control. Check if remote access from the internet or external networks is enabled, and review which IP addresses or ranges are permitted to access the admin interface.
    Affected if Remote administration is enabled and accessible from untrusted networks, allowing unauthenticated or low-privilege attackers to reach the login page.

A device is affected if it is one of the listed Orbi models (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) running firmware version lower than 3.2.16.6 and has its admin interface accessible to attackers who can obtain valid credentials.

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 the firmware on all affected NETGEAR Orbi devices to version 3.2.16.6 or later. Additionally, restrict administrative access to trusted users only and use strong, unique credentials to limit the attack surface.

Recommended fix High confidence

Firmware version 3.2.16.6 or later

  1. 1. Log in to the NETGEAR router web interface (http://routerlogin.net or http://192.168.1.1)
  2. 2. Navigate to Administration > Router Update or Settings > Advanced > Administration > Router Update
  3. 3. Check the current firmware version under 'Current Version'
  4. 4. If the firmware version is earlier than 3.2.16.6, click 'Check for Updates' or manually download firmware 3.2.16.6 from the NETGEAR support website (kb.netgear.com) for your specific model (RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850)
  5. 5. Upload the firmware file and wait for the update process to complete - do not power off the router during this process
  6. 6. After the router restarts, verify the firmware version is now 3.2.16.6 or later
Caveat Firmware upgrade may cause temporary connectivity interruption; ensure stable power during update process

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

Fix this in Rbk752 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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