dbcve.org
R6900p FirmwareOperating system · Netgear

CVE-2021-45679

HIGH · 7.2 CVSS v3.1 Published 2021-12-26
Fix available
A fix is available. Upgrade to 1.0.11.126 / 1.3.3.140 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 privilege escalation. This affects R6900P before 1.3.3.140, R7000 before 1.0.11.126, R7000P before 1.3.3.140, and RS400 before 1.5.1.80.

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 · moderate confidence

NETGEAR R6900P, R7000, R7000P, and RS400 routers contain a privilege escalation vulnerability in firmware versions prior to the specified patched releases. An attacker with low-privileged access could potentially escalate to administrative privileges on affected devices.

MitigationUpdate NETGEAR router firmware to version 1.3.3.140 or later for R6900P/R7000P, 1.0.11.126 or later for R7000, and 1.5.1.80 or later for RS400. Restrict administrative interface access to trusted networks until patches are applied.

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
R6900p FirmwareOperating system
Affected:< 1.3.3.140
R7000 FirmwareOperating system
Affected:< 1.0.11.126
R7000p FirmwareOperating system
Affected:< 1.3.3.140
Rs400 FirmwareOperating system
Affected:< 1.5.1.80

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

CVSS:3.1/AV:N/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 router model
    Locate the model number printed on the router device label or access the web interface and look for the model name in the status or dashboard page
    Affected if Model is R6900P, R7000, R7000P, or RS400
  2. Access router web interface
    Open a browser and navigate to routerlogin.net or 192.168.1.1, then log in with any valid credential
    Affected if Login is successful with any user account
  3. Locate firmware version in web interface
    Navigate to Administration > Router Update or Advanced > Administration > Firmware Version on the web interface
    Affected if Displayed firmware version is visible
  4. Compare firmware version to affected ranges
    Compare the installed version against: R6900P < 1.3.3.140, R7000 < 1.0.11.126, R7000P < 1.3.3.140, RS400 < 1.5.1.80
    Affected if Installed version is lower than the corresponding patched version for your model

You are affected if your router model is R6900P, R7000, R7000P, or RS400 and the installed firmware version is below 1.3.3.140 (R6900P/R7000P), 1.0.11.126 (R7000), or 1.5.1.80 (RS400).

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 1.0.11.126 / 1.3.3.140 / 1.5.1.80 or later
Fixed in 1.0.11.1261.3.3.1401.5.1.80
Interim mitigation

Update NETGEAR router firmware to version 1.3.3.140 or later for R6900P/R7000P, 1.0.11.126 or later for R7000, and 1.5.1.80 or later for RS400. Restrict administrative interface access to trusted networks until patches are applied.

Recommended fix High confidence

R6900P: 1.3.3.140 | R7000: 1.0.11.126 | R7000P: 1.3.3.140 | RS400: 1.5.1.80

  1. 1. Identify your exact router model (R6900P, R7000, R7000P, or RS400)
  2. 2. Visit the NETGEAR support website (support.netgear.com) or kb.netgear.com
  3. 3. Enter your router model number to find the firmware download page
  4. 4. Download the specific fixed firmware version for your model: R6900P requires 1.3.3.140, R7000 requires 1.0.11.126, R7000P requires 1.3.3.140, RS400 requires 1.5.1.80
  5. 5. Access your router's web interface by navigating to routerlogin.net or 192.168.1.1
  6. 6. Log in with your router admin credentials
  7. 7. Navigate to Advanced > Administration > Firmware Update (or similar path depending on UI)
  8. 8. Click 'Check for Updates' or select 'Upload' to manually upload the downloaded firmware file
Caveat Firmware updates typically preserve settings; however, always backup configuration before upgrading and note that some settings may reset to defaults

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

Fix this in R6900p 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-45679 — 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-45679 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