dbcve.org
Rbk752 FirmwareOperating system · Netgear

CVE-2021-45577

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 execute arbitrary commands on the affected devices through the web management interface by injecting OS commands into input fields.

MitigationUpdate the NETGEAR Orbi firmware to version 3.2.16.6 or later to remediate this vulnerability.

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
    Locate the model number on the device label or access the web management interface and check the device information page. Common locations are the bottom of the router or the 'About' or 'Device Info' section in the admin panel.
    Affected if The device model is one of: RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.
  2. Check the installed firmware version
    Access the web management interface (typically at 192.168.1.1 or orbilogin.com) and navigate to the 'Administration' or 'Firmware Update' section. The current firmware version is displayed on the main status or 'About' page.
    Affected if The firmware version is lower than 3.2.16.6 (for example, 3.2.14.4, 3.2.10.5, etc.). Compare your version against the affected range: any version < 3.2.16.6.
  3. Confirm web management interface accessibility
    Verify that the Orbi web management interface is reachable from the network. Attempt to access the admin panel at the device's IP address or hostname.
    Affected if The web management interface is accessible and responds to authentication requests. The vulnerability requires the web interface to be reachable, as exploitation occurs through HTTP requests to this interface.
  4. Verify authentication to the web interface
    Determine whether valid credentials exist for the web management interface. The vulnerability is exploitable by an authenticated attacker, meaning valid admin credentials are required.
    Affected if You can log in to the Orbi admin panel or default credentials are still in use. An unauthenticated attacker cannot exploit this specific flaw, but any valid user account would be able to inject commands.

You are affected if your Orbi device is model RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850 and the firmware version is less than 3.2.16.6, with the web management interface accessible using 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 NETGEAR Orbi firmware to version 3.2.16.6 or later to remediate this vulnerability.

Recommended fix High confidence

Firmware version 3.2.16.6 or later for the respective model (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850)

  1. 1. Identify the exact NETGEAR Orbi model number (RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850) from the device label
  2. 2. Visit the NETGEAR support website (kb.netgear.com) and search for your specific model
  3. 3. Navigate to the Downloads/Firmware section for your model
  4. 4. Download firmware version 3.2.16.6 or later (the latest available version recommended)
  5. 5. Log into the Orbi router's web interface by entering the router's IP address in a browser
  6. 6. Navigate to the Administration > Firmware Update or similar menu option
  7. 7. Click 'Upload' or 'Check for Updates' and select the downloaded firmware file
  8. 8. Wait for the firmware upload and installation to complete - do not power off the device
Caveat Firmware updates typically do not cause breaking changes but may briefly disrupt network connectivity during the update process

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