dbcve.org
R6700 FirmwareOperating system · Netgear

CVE-2021-29068

HIGH · 8.8 CVSS v3.1 Published 2021-03-23
Fix available
A fix is available. Upgrade to 1.0.1.62 / 1.0.2.16 or later.
See remediation →
94/100
Remediation priority · Urgent
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 a buffer overflow by an authenticated user. This affects R6700v3 before 1.0.4.98, R6400v2 before 1.0.4.98, R7000 before 1.0.11.106, R6900P before 1.3.2.124, R7000P before 1.3.2.124, R7900 before 1.0.4.26, R7850 before 1.0.5.60, R8000 before 1.0.4.58, RS400 before 1.5.0.48, R6400 before 1.0.1.62, R6700 before 1.0.2.16, R6900 before 1.0.2.16, MK60 before 1.0.5.102, MR60 before 1.0.5.102, MS60 before 1.0.5.102, CBR40 before 2.5.0.10, R8000P before 1.4.1.62, R7960P before 1.4.1.62, R7900P before 1.4.1.62, RAX15 before 1.0.1.64, RAX20 before 1.0.1.64, RAX75 before 1.0.3.102, RAX80 before 1.0.3.102, RAX200 before 1.0.2.102, RAX45 before 1.0.2.64, RAX50 before 1.0.2.64, EX7500 before 1.0.0.68, EAX80 before 1.0.1.62, EAX20 before 1.0.0.36, RBK752 before 3.2.16.6, RBK753 before 3.2.16.6, RBK753S before 3.2.16.6, RBK754 before 3.2.16.6, RBR750 before 3.2.16.6, RBS750 before 3.2.16.6, RBK852 before 3.2.16.6, RBK853 before 3.2.16.6, RBK854 before 3.2.16.6, RBR850 before 3.2.16.6, RBS850 before 3.2.16.6, RBR840 before 3.2.16.6, RBS840 before 3.2.16.6, R6120 before 1.0.0.70, R6220 before 1.1.0.100, R6230 before 1.1.0.100, R6260 before 1.1.0.76, R6850 before 1.1.0.76, R6350 before 1.1.0.76, R6330 before 1.1.0.76, D7800 before 1.0.1.58, RBK50 before 2.6.1.40, RBR50 before 2.6.1.40, RBS50 before 2.6.1.40, RBK40 before 2.6.1.36, RBR40 before 2.6.1.36, RBS40 before 2.6.1.38, RBK23 before 2.6.1.36, RBR20 before 2.6.1.38, RBS20 before 2.6.1.38, RBK12 before 2.6.1.44, RBK13 before 2.6.1.44, RBK14 before 2.6.1.44, RBK15 before 2.6.1.44, RBR10 before 2.6.1.44, RBS10 before 2.6.1.44, R6800 before 1.2.0.72, R6900v2 before 1.2.0.72, R6700v2 before 1.2.0.72, R7200 before 1.2.0.72, R7350 before 1.2.0.72, R7400 before 1.2.0.72, R7450 before 1.2.0.72, AC2100 before 1.2.0.72, AC2400 before 1.2.0.72, AC2600 before 1.2.0.72, R7800 before 1.0.2.74, R8900 before 1.0.5.24, R9000 before 1.0.5.24, RAX120 before 1.0.1.136, XR450 before 2.3.2.66, XR500 before 2.3.2.66, XR700 before 1.0.1.34, and XR300 before 1.0.3.50.

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

Buffer overflow vulnerability in NETGEAR router and mesh system firmware allows authenticated users to potentially execute arbitrary code or cause denial of service due to improper bounds checking in certain administrative functions.

MitigationUpdate affected devices to the firmware versions specified in the advisory, or enforce strict access controls on the administrative interface 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
R6700 FirmwareOperating system
Affected:< 1.0.4.98< 1.0.2.16< 1.2.0.72
R6400 FirmwareOperating system
Affected:< 1.0.4.98< 1.0.1.62
R7000 FirmwareOperating system
Affected:< 1.0.11.106
R6900p FirmwareOperating system
Affected:< 1.3.2.124
R7000p FirmwareOperating system
Affected:< 1.3.2.124
R7900 FirmwareOperating system
Affected:< 1.0.4.26
R7850 FirmwareOperating system
Affected:< 1.0.5.60
R8000 FirmwareOperating system
Affected:< 1.0.4.58

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

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 router model number
    Locate the model number on the device label or check it in the router administrative web interface under a status or management page
    Affected if The device is one of the following models: R6700, R6400, R7000, R6900p, R7000p, R7900, R7850, or R8000
  2. Determine the current firmware version
    Access the router administrative web interface and navigate to the firmware version or status section, or use the router's diagnostic tools to retrieve the installed firmware version
    Affected if The installed firmware version cannot be determined or is below the secure version for that model
  3. Compare installed version against affected ranges for your model
    Reference the specific version thresholds for your model from the advisory: R6700 requires 1.0.4.98, 1.0.2.16, or 1.2.0.72 or higher; R6400 requires 1.0.4.98 or 1.0.1.62 or higher; R7000 requires 1.0.11.106 or higher; R6900p and R7000p require 1.3.2.124 or higher; R7900 requires 1.0.4.26 or higher; R7850 requires 1.0.5.60 or higher; R8000 requires 1.0.4.58 or higher
    Affected if Your installed firmware version is lower than the required secure version for your specific router model
  4. Verify administrative interface accessibility
    Confirm whether the router's web-based administrative interface is accessible from the network
    Affected if The administrative interface is exposed to untrusted networks, as exploitation requires authenticated access to these administrative functions

You are affected if you have one of the listed router models and your current firmware version is below the minimum secure version for that model, particularly if the administrative interface is network-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 1.0.1.62 / 1.0.2.16 / 1.0.4.26 or later
Fixed in 1.0.1.621.0.2.161.0.4.26
Interim mitigation

Update affected devices to the firmware versions specified in the advisory, or enforce strict access controls on the administrative interface to reduce attack surface.

Recommended fix High confidence

Upgrade to firmware version 1.0.2.16 or higher for R6700; 1.0.1.62 or higher for R6400; 1.0.11.106 or higher for R7000; 1.3.2.124 or higher for R6900P/R7000P; 1.0.4.26 or higher for R7900; 1.0.5.60 or higher for R7850; 1.0.4.58 or higher for R8000; or the latest available firmware from NETGEAR suppo

  1. 1. Identify the exact NETGEAR device model number (e.g., R6700, R7000, R7900) from the product label
  2. 2. Check the current firmware version by logging into the router web interface and navigating to Administration > Firmware Update or similar
  3. 3. Visit the NETGEAR support page (kb.netgear.com) and locate the firmware download section for your specific model
  4. 4. Download the latest firmware version that meets or exceeds the fixed version for your model (e.g., R6700: 1.0.2.16 or higher, R7000: 1.0.11.106 or higher, R7900: 1.0.4.26 or higher)
  5. 5. In the router web interface, navigate to the firmware update section and upload the downloaded firmware file
  6. 6. Wait for the firmware upload and installation to complete - do not power off the router during this process
  7. 7. After the router restarts, log back into the web interface and verify the new firmware version is installed
  8. 8. Consider performing a factory reset and reconfiguring the router to ensure a clean state
Caveat Firmware updates may reset router configuration to defaults; backup current settings before upgrading and reconfigure after upgrade; some older features may be deprecated in newer firmware versions

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

Fix this in R6700 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,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 $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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