dbcve.org
Cbr750 FirmwareOperating system · Netgear

CVE-2021-45505

HIGH · 8.8 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 3.2.17.12 / 4.6.3.6 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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 authentication bypass. This affects CBR750 before 4.6.3.6, RBK752 before 3.2.17.12, RBR750 before 3.2.17.12, RBS750 before 3.2.17.12, RBK852 before 3.2.17.12, RBR850 before 3.2.17.12, and RBS850 before 3.2.17.12.

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

NETGEAR Orbi mesh router systems (CBR750, RBK752/RBR750/RBS750, RBK852/RBR850/RBS850) contain an authentication bypass vulnerability allowing unauthenticated attackers to access the device management interface. The vulnerability affects firmware versions prior to 4.6.3.6 (CBR750) and 3.2.17.12 (others).

MitigationApply NETGEAR firmware updates: upgrade CBR750 to version 4.6.3.6 or later, and RBK752/RBR750/RBS750/RBK852/RBR850/RBS850 to version 3.2.17.12 or later.

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
Cbr750 FirmwareOperating system
Affected:< 4.6.3.6
Rbk752 FirmwareOperating system
Affected:< 3.2.17.12
Rbr750 FirmwareOperating system
Affected:< 3.2.17.12
Rbs750 FirmwareOperating system
Affected:< 3.2.17.12
Rbk852 FirmwareOperating system
Affected:< 3.2.17.12
Rbr850 FirmwareOperating system
Affected:< 3.2.17.12
Rbs850 FirmwareOperating system
Affected:< 3.2.17.12

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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 exact Orbi model variant
    Locate the model number on the device label or check the web management interface (typically at http://orbilogin.net) under the firmware or status page. Confirm whether the device is a CBR750 or one of the RBK/RBR/RBS 750/850 series.
    Affected if The model is any of CBR750, RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.
  2. Determine the installed firmware version
    In the Orbi web interface, navigate to the Administration or Firmware Update section to view the current firmware version. Alternatively, use the NETGEAR Orbi mobile app to check the firmware version under device settings.
    Affected if A firmware version is displayed on the device.
  3. Compare firmware version against affected thresholds
    If the model is CBR750, verify whether the installed version is lower than 4.6.3.6. For all other models (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850), verify whether the installed version is lower than 3.2.17.12.
    Affected if The installed firmware version is below 4.6.3.6 (CBR750) or below 3.2.17.12 (all other listed models).

A user is affected if they are running any of the listed Orbi models with firmware versions below the specified thresholds, as those versions allow unauthenticated access to the management interface.

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.17.12 / 4.6.3.6 or later
Fixed in 3.2.17.124.6.3.6
Interim mitigation

Apply NETGEAR firmware updates: upgrade CBR750 to version 4.6.3.6 or later, and RBK752/RBR750/RBS750/RBK852/RBR850/RBS850 to version 3.2.17.12 or later.

Recommended fix High confidence

CBR750: firmware 4.6.3.6 or later; RBK752/RBR750/RBS750/RBK852/RBR850/RBS850: firmware 3.2.17.12 or later

  1. 1. Identify the exact NETGEAR Orbi model (CBR750, RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850) that needs remediation
  2. 2. Visit the NETGEAR support website at kb.netgear.com and search for the specific model
  3. 3. Download the latest firmware version for the model: CBR750 upgrade to 4.6.3.6 or later; RBK752, RBR750, RBS750, RBK852, RBR850, RBS850 upgrade to 3.2.17.12 or later
  4. 4. Access the Orbi web interface or Orbi app
  5. 5. Navigate to Settings > Administration > Firmware Update (or similar path depending on model)
  6. 6. Upload and apply the downloaded firmware
  7. 7. Wait for the device to reboot and verify the firmware version has been updated
Caveat Firmware updates typically do not cause breaking changes but may reset some custom settings; backup configuration if possible before updating

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

Fix this in Cbr750 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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