CVE-2021-45502
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 · uneditedCertain NETGEAR devices are affected by authentication bypass. This affects CBR750 before 4.6.3.6, RBK752 before 3.2.17.12, 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 confidenceAuthentication bypass vulnerability in NETGEAR Orbi mesh WiFi systems (CBR750, RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) allowing unauthorized access to administrative interfaces. The vulnerability affects firmware versions prior to 4.6.3.6 (CBR750) and 3.2.17.12 (other models).
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< 4.6.3.6< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify your NETGEAR Orbi device modelCheck the product label on the bottom or side of the router or satellite unit, or log into the web interface and look for the model number displayed on the dashboard or status page.Affected if The device is one of: CBR750, RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.
-
Check the installed firmware versionAccess the Orbi web interface by entering the router's IP address in a browser. Navigate to Settings > Administration > Firmware Update or similar. The current firmware version is displayed on the dashboard or in the router status information.Affected if The displayed firmware version is not yet determined.
-
Compare firmware version to affected rangesFor CBR750 models: verify if version is below 4.6.3.6. For RBK752, RBR750, RBS750, RBK852, RBR850, RBS850 models: verify if version is below 3.2.17.12.Affected if Firmware version is less than 4.6.3.6 (CBR750) or less than 3.2.17.12 (all other models).
-
Verify remote administration interface accessibilityFrom an external network (outside your local network), attempt to access the Orbi router web interface using its public IP address on port 80/443. If the administrative login page loads without requiring authentication, the authentication bypass vulnerability may be present.Affected if The administrative interface loads without prompting for credentials from an unauthorized network location.
You are affected if your Orbi device model matches one of the listed models AND your installed firmware version is below 4.6.3.6 (for CBR750) or below 3.2.17.12 (for all other models).
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.2.17.124.6.3.6
Update affected NETGEAR devices to firmware version 4.6.3.6 or later for CBR750, and 3.2.17.12 or later for RBK/RBR/RBS models. Apply firmware updates immediately given the high CVSS score and authentication bypass nature.
CBR750: 4.6.3.6 or later | RBK752/RBR750/RBS750/RBK852/RBR850/RBS850: 3.2.17.12 or later
- 1. Identify the exact NETGEAR device model (CBR750, RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850)
- 2. Access the device web interface or NETGEAR Nighthawk/Orbi app
- 3. Navigate to Settings > Administration > Firmware Update (or similar)
- 4. Check current firmware version under the device status
- 5. Download the latest firmware from the official NETGEAR support page (kb.netgear.com) for your specific model
- 6. Upload the firmware file and wait for the update to complete - do not power off the device during this process
- 7. After reboot, verify the firmware version has been updated to the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-45502 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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