dbcve.org
Rbk752 FirmwareOperating system · Netgear

CVE-2021-45559

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). An attacker with valid admin credentials can execute arbitrary system commands on the affected devices due to improper input sanitization in the firmware's web management interface.

MitigationUpdate NETGEAR Orbi firmware to version 3.2.16.6 or later to remediate this vulnerability. If updating is not immediately possible, limit administrative access to trusted users and monitor for suspicious administrative activity.

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 web interface or use the NETGEAR Orbi app to view the device model information. The model number is typically listed on the device label or in the system overview page.
    Affected if The device model is RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.
  2. Check the installed firmware version
    Log into the Orbi web management interface (typically at 192.168.1.1 or orbilogin.com). Navigate to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware version.
    Affected if The firmware version is below 3.2.16.6.
  3. Verify the web management interface is accessible
    Attempt to reach the Orbi web interface at http://192.168.1.1 or http://orbilogin.com from a connected device. Confirm the login page loads.
    Affected if The web management interface is accessible and responds to requests.
  4. Confirm admin credentials are configured
    Check if an admin user account exists on the device. This can be verified by attempting to log into the web interface or reviewing the user account settings under Administration > Setup > Wireless Setup or similar admin sections.
    Affected if An admin account is enabled or configured on the device.

The device is affected if it is one of the listed Orbi models (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) running firmware version 3.2.16.6 or lower, with the web management interface accessible and admin credentials configured.

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 NETGEAR Orbi firmware to version 3.2.16.6 or later to remediate this vulnerability. If updating is not immediately possible, limit administrative access to trusted users and monitor for suspicious administrative activity.

Recommended fix High confidence

3.2.16.6

  1. Log in to the NETGEAR router web interface (typically at routerlogin.net or routerlogin.com)
  2. Navigate to Administration > Firmware Update or Settings > Advanced > Firmware Update
  3. Click 'Check for Updates' or manually download firmware version 3.2.16.6 from the official NETGEAR support site (kb.netgear.com)
  4. If manually updating, select the appropriate .chk file for your specific model (RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850)
  5. Upload the firmware file and wait for the update to complete - do not power off the router during the update process
  6. After the router reboots, log back into the web interface and verify the firmware version shows 3.2.16.6 or later

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-45559 — 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-45559 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