dbcve.org
Rbk752 FirmwareOperating system · Netgear

CVE-2021-45563

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

Command injection vulnerability in NETGEAR Orbi mesh WiFi systems (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) allows authenticated users to execute arbitrary commands via unsanitized input in the web interface or API, likely through a parameter passed to a system shell call.

MitigationUpdate affected devices to firmware version 3.2.16.6 or later. Until patched, restrict administrative access to trusted users only to reduce 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 Orbi device model
    Check the label on the bottom of the Orbi router or satellite unit for the model number (RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850). Alternatively, log into the web interface and check the status or administration page for the model identifier.
    Affected if The model is one of: RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.
  2. Check installed firmware version
    Log into the Orbi web interface (typically at 192.168.1.1 or orbilogin.com). Navigate to Administration > Firmware Update or Advanced > Administration > Firmware version. Record the displayed firmware version number.
    Affected if The firmware version is lower than 3.2.16.6 (for example, 3.2.16.5, 3.2.14.10, etc.).
  3. Confirm web interface accessibility
    Attempt to reach the Orbi router login page from a browser. Verify that the administrative web interface is accessible on the local network.
    Affected if The web interface is reachable and accepts authentication credentials.
  4. Verify administrative credentials
    Test that valid administrative credentials can be used to log into the Orbi web interface or API endpoint.
    Affected if Authentication succeeds with valid admin credentials, indicating the device allows authenticated administrative access.

You are affected if your Orbi device is one of the listed models (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) and the installed firmware version is below 3.2.16.6, because the command injection flaw exists in the web interface for all authenticated users on vulnerable firmware versions.

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 devices to firmware version 3.2.16.6 or later. Until patched, restrict administrative access to trusted users only to reduce the attack surface.

Recommended fix High confidence

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

  1. 1. Identify the exact model number of your NETGEAR device (Rbk752, Rbr750, Rbs750, Rbk852, Rbr850, or Rbs850)
  2. 2. Visit the NETGEAR support website (kb.netgear.com) or download center
  3. 3. Locate the firmware download section for your specific model
  4. 4. Download firmware version 3.2.16.6 or later for your device
  5. 5. Access the router's web management interface using a browser
  6. 6. Navigate to the Administration or Firmware Update section
  7. 7. Upload the downloaded firmware file and initiate the update
  8. 8. Wait for the firmware to flash and the device to reboot automatically
Caveat Standard firmware update; back up configuration before upgrading as a precaution

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

Fix this in Rbk752 Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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