dbcve.org
Rbk752 FirmwareOperating system · Netgear

CVE-2021-45567

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 system commands due to insufficient input validation in the web management interface.

MitigationUpgrade affected devices to firmware version 3.2.16.6 or later. Until patched, limit administrative access to trusted personnel only and monitor for unauthorized access.

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 web management interface or check the device label to confirm the exact model number (RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850)
    Affected if The device is one of the six affected models listed in the CVE
  2. Check the installed firmware version
    Log into the Orbi web management interface and navigate to the Administration or Settings section to view the current firmware version
    Affected if The firmware version is less than 3.2.16.6
  3. Verify web management interface is enabled
    Confirm the web management interface is accessible (typically at http://192.168.1.1 or http://orbilogin.net)
    Affected if The web interface is exposed and accessible on the network
  4. Review administrative access accounts
    Check the list of user accounts with administrative privileges in the web management interface under User Management or Administration settings
    Affected if There are user accounts configured with admin access (the vulnerability requires authenticated credentials)

The environment is affected if the device is one of the six listed models running firmware version 3.2.16.6 or lower, and the web management interface with administrative accounts is 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

Upgrade affected devices to firmware version 3.2.16.6 or later. Until patched, limit administrative access to trusted personnel only and monitor for unauthorized access.

Recommended fix High confidence

3.2.16.6 (or any later stable release for the same model)

  1. Identify the exact model of your NETGEAR Orbi mesh system (e.g., RBK752, RBR750, RBS750, RBK852, RBR850, RBS850).
  2. Open a web browser and log into the router’s web management interface using an admin account.
  3. Navigate to the ‘Administration’ or ‘Settings’ section and locate the ‘Firmware Update’ or ‘Router Update’ page.
  4. Check the current firmware version under the ‘Router Status’ or ‘About’ page to confirm it is below 3.2.16.6.
  5. Download the latest firmware version 3.2.16.6 (or later) from the official NETGEAR support site (e.g., https://www.netgear.com/support/). Ensure the file matches your exact model number.
  6. Backup the current router configuration through the ‘Backup Settings’ option if the UI provides it.
  7. On the firmware update page, choose the ‘Manual Update’ or ‘Upload’ option and select the downloaded .img file.
  8. Wait for the upload to complete; do not power off the device. The router will automatically reboot.
Caveat Firmware upgrades may temporarily interrupt connectivity; after the upgrade, verify that all settings and port forwards are intact, and consider a factory reset if issues arise.

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