dbcve.org
R6900p FirmwareOperating system · Netgear

CVE-2021-45499

HIGH · 8.8 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 1.0.3.106 / 1.3.3.140 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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 R6900P before 1.3.3.140, R7000P before 1.3.3.140, R7900P before 1.4.2.84, R7960P before 1.4.2.84, R8000P before 1.4.2.84, RAX75 before 1.0.3.106, and RAX80 before 1.0.3.106.

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

A detailed technical summary for this CVE is being prepared.

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
R6900p FirmwareOperating system
Affected:< 1.3.3.140
R7000p FirmwareOperating system
Affected:< 1.3.3.140
R7900p FirmwareOperating system
Affected:< 1.4.2.84
R7960p FirmwareOperating system
Affected:< 1.4.2.84
R8000p FirmwareOperating system
Affected:< 1.4.2.84
Rax75 FirmwareOperating system
Affected:< 1.0.3.106
Rax80 FirmwareOperating system
Affected:< 1.0.3.106

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 1.0.3.106 / 1.3.3.140 / 1.4.2.84 or later
Fixed in 1.0.3.1061.3.3.1401.4.2.84
Vendor patch kb.netgear.com →
Recommended fix High confidence

R6900p/R7000p: firmware 1.3.3.140 | R7900p/R7960p/R8000p: firmware 1.4.2.84 | Rax75/Rax80: firmware 1.0.3.106 (or later stable releases)

  1. Identify the exact NETGEAR router model (R6900p, R7000p, R7900p, R7960p, R8000p, Rax75, or Rax80)
  2. Access the router's web interface and navigate to Administration > Firmware Update or similar section
  3. Check the current firmware version under the router status or advanced settings
  4. Download the appropriate fixed firmware from the official NETGEAR support website for your specific model: R6900p/R7000p upgrade to 1.3.3.140 or later; R7900p/R7960p/R8000p upgrade to 1.4.2.84 or later; Rax75/Rax80 upgrade to 1.0.3.106 or later
  5. Upload the firmware file through the router's web interface and initiate the update
  6. Wait for the firmware upload and installation to complete (do not power off the router during this process)
  7. After the router reboots, verify the new firmware version is installed correctly
  8. Log into the router and confirm the administration interface is accessible
Caveat Firmware updates on routers typically carry low risk but may reset some custom configurations; backup router settings before upgrading if possible

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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