dbcve.org
Rbr20 FirmwareOperating system · Netgear

CVE-2021-45593

MEDIUM · 6.8 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 2.7.2.102 / 2.7.3.22 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 RBR20 before 2.7.3.22, RBR40 before 2.7.3.22, RBR50 before 2.7.2.102, RBS20 before 2.7.3.22, RBS40 before 2.7.3.22, RBR50 before 2.7.2.102, RBK20 before 2.7.3.22, RBK40 before 2.7.3.22, and RBK50 before 2.7.2.102.

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 (RBR, RBS, RBK series) allows authenticated users to execute arbitrary commands via unspecified input vectors. The vulnerability affects multiple firmware versions prior to 2.7.3.22 or 2.7.2.102 depending on model.

MitigationUpdate affected NETGEAR Orbi devices to firmware version 2.7.3.22 or 2.7.2.102 (as applicable) or later. Limit administrative access to trusted users to reduce 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
Rbr20 FirmwareOperating system
Affected:< 2.7.3.22
Rbr40 FirmwareOperating system
Affected:< 2.7.3.22
Rbr50 FirmwareOperating system
Affected:< 2.7.2.102
Rbs20 FirmwareOperating system
Affected:< 2.7.3.22
Rbs40 FirmwareOperating system
Affected:< 2.7.3.22
Rbk20 FirmwareOperating system
Affected:< 2.7.3.22
Rbk40 FirmwareOperating system
Affected:< 2.7.3.22
Rbk50 FirmwareOperating system
Affected:< 2.7.2.102

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 model number
    Locate the model label on the device or access the admin web interface and check the status or settings page for the exact model (RBR20, RBR40, RBR50, RBS20, RBS40, RBK20, RBK40, or RBK50)
    Affected if The model is one of the eight affected models listed in the CVE
  2. Check the installed firmware version
    Log into the Orbi admin web interface (typically at 192.168.1.1 or orbilogin.net), navigate to Administration > Firmware Update or similar, and record the current firmware version displayed
    Affected if Unable to determine the firmware version or the interface is inaccessible
  3. Compare firmware against affected version ranges
    Cross-reference the installed firmware version with the CVE thresholds: models RBR20, RBR40, RBS20, RBS40, RBK20, RBK40 are affected if below 2.7.3.22; models RBR50, RBK50 are affected if below 2.7.2.102
    Affected if The installed firmware version is lower than the threshold for that specific model
  4. Determine if administrative access is possible
    Verify whether the Orbi admin web interface is accessible from the local network or remotely (through port 80/443 forwarding or VPN) and whether valid administrator credentials exist
    Affected if The admin interface is exposed and credentials are known (the vulnerability requires authenticated access to exploit)

A user is affected if they own an affected Orbi model (RBR/RBS/RBK series) running firmware version below the threshold (2.7.3.22 or 2.7.2.102 depending on model) and the administrative interface 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 2.7.2.102 / 2.7.3.22 or later
Fixed in 2.7.2.1022.7.3.22
Interim mitigation

Update affected NETGEAR Orbi devices to firmware version 2.7.3.22 or 2.7.2.102 (as applicable) or later. Limit administrative access to trusted users to reduce attack surface.

Recommended fix High confidence

RBR20/RBR40/RBS20/SBS40/RBK20/RBK40: upgrade to firmware 2.7.3.22 or later; RBR50/RBK50: upgrade to firmware 2.7.2.102 or later

  1. 1. Identify your exact NETGEAR Orbi model number (RBR20, RBR40, RBR50, RBS20, RBS40, RBK20, RBK40, or RBK50)
  2. 2. Download the appropriate firmware version from the official NETGEAR support website (kb.netgear.com)
  3. 3. Access your router's web interface by entering its IP address in a web browser
  4. 4. Log in with administrator credentials
  5. 5. Navigate to the Administration > Firmware Update or similar section
  6. 6. Select the option to manually upload the firmware file
  7. 7. Upload the downloaded firmware file and wait for the upgrade to complete
  8. 8. After the router reboots, verify the firmware version has been updated to the fixed release
Caveat Firmware upgrades on routers are generally safe; ensure stable power during upgrade to avoid rendering the device inoperable

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

Fix this in Rbr20 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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