dbcve.org
R6700 FirmwareOperating system · Netgear

CVE-2018-21134

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-23
Fix available
A fix is available. Upgrade to 1.0.1.44 / 1.0.1.48 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 a stack-based buffer overflow by an unauthenticated attacker. This affects R6700 before 1.0.1.48, R7900 before 1.0.2.16, R6900 before 1.0.1.48, R7000P before 1.3.1.44, R6900P before 1.3.1.44, R6250 before 1.0.4.30, R6300v2 before 1.0.4.32, R6400 before 1.0.1.44, R6400v2 before 1.0.2.60, R7000 before 1.0.9.34, R7100LG before 1.0.0.48, R7300 before 1.0.0.68, R8000 before 1.0.4.18, R8000P before 1.4.1.24, R7900P before 1.4.1.24, R8500 before 1.0.2.122, R8300 before 1.0.2.122, WN2500RPv2 before 1.0.1.54, EX3700 before 1.0.0.72, EX3800 before 1.0.0.72, EX6000 before 1.0.0.32, EX6100 before 1.0.2.24, EX6120 before 1.0.0.42, EX6130 before 1.0.0.24, EX6150v1 before 1.0.0.42, EX6200 before 1.0.3.88, EX7000 before 1.0.0.66, D7000v2 before 1.0.0.51, D6220 before 1.0.0.46, D6400 before 1.0.0.82, and D8500 before 1.0.3.42.

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

Stack-based buffer overflow vulnerability in multiple NETGEAR router and range extender models allowing unauthenticated remote code execution. The vulnerability exists in the firmware of affected devices and can be exploited over the network without any authentication, earning a critical CVSS score of 9.8.

MitigationUpdate firmware to the versions specified in the advisory for each device model. If updates are unavailable, restrict network access to device management interfaces and implement network segmentation to reduce exposure.

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.1.48
R7900 FirmwareOperating system
Affected:< 1.0.2.16
R6900 FirmwareOperating system
Affected:< 1.0.1.48
R7000p FirmwareOperating system
Affected:< 1.3.1.44
R6900p FirmwareOperating system
Affected:< 1.3.1.44
R6250 FirmwareOperating system
Affected:< 1.0.4.30
R6300 FirmwareOperating system
Affected:< 1.0.4.32
R6400 FirmwareOperating system
Affected:< 1.0.1.44< 1.0.2.60

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

CVSS:3.1/AV:N/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 NETGEAR device model
    Access the router web administration interface or inspect the device label. Confirm the exact model number from R6700, R7900, R6900, R7000p, R6900p, R6250, R6300, or R6400.
    Affected if The device matches one of these eight models.
  2. Check installed firmware version
    Log into the router web interface and navigate to the Administration, Firmware Update, or Status section. Locate the displayed firmware version number.
    Affected if Firmware version is below: R6700 < 1.0.1.48, R7900 < 1.0.2.16, R6900 < 1.0.1.48, R7000p < 1.3.1.44, R6900p < 1.3.1.44, R6250 < 1.0.4.30, R6300 < 1.0.4.32, or R6400 < 1.0.1.44 (or < 1.0.2.60 for certain hardware revisions).
  3. Determine network exposure of management interface
    Check the router settings for Remote Management or Access Control. Verify if the web administration interface is accessible from WAN/internet (outside the local network).
    Affected if Remote management is enabled and the router is reachable from external networks.

The device is affected if it is one of the eight models AND its firmware version is below the specified threshold AND the management 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.44 / 1.0.1.48 / 1.0.2.16 or later
Fixed in 1.0.1.441.0.1.481.0.2.16
Interim mitigation

Update firmware to the versions specified in the advisory for each device model. If updates are unavailable, restrict network access to device management interfaces and implement network segmentation to reduce exposure.

Recommended fix High confidence

Device-specific firmware version at or above: R6700 (1.0.1.48), R7900 (1.0.2.16), R6900 (1.0.1.48), R7000P (1.3.1.44), R6900P (1.3.1.44), R6250 (1.0.4.30), R6300v2 (1.0.4.32), R6400 (1.0.1.44), R6400v2 (1.0.2.60), R7000 (1.0.9.34), and respective versions for all other affected models as listed in t

  1. 1. Identify the exact NETGEAR router or extender model from the affected device list.
  2. 2. Visit the NETGEAR support website (support.netgear.com) or use the model-specific download page.
  3. 3. Locate the firmware download section for your specific model.
  4. 4. Download the firmware version equal to or newer than the fixed version for your device: R6700: 1.0.1.48, R7900: 1.0.2.16, R6900: 1.0.1.48, R7000P: 1.3.1.44, R6900P: 1.3.1.44, R6250: 1.0.4.30, R6300v2: 1.0.4.32, R6400: 1.0.1.44, R6400v2: 1.0.2.60, R7000: 1.0.9.34, R7100LG: 1.0.0.48, R7300: 1.0.0.68, R8000: 1.0.4.18, R8000P: 1.4.1.24, R7900P: 1.4.1.24, R8500: 1.0.2.122, R8300: 1.0.2.122, WN2500RP
  5. 5. Access the router's web interface via a browser at routerlogin.net or 192.168.1.1.
  6. 6. Navigate to Administration > Firmware Update > Upload new firmware, or similar path depending on model.
  7. 7. Upload the downloaded firmware file and wait for the update process to complete.
  8. 8. After reboot, verify the firmware version in the router admin interface to confirm the update was successful.
Caveat Standard firmware update; ensure stable power during upload to avoid bricking; backup configuration if possible

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-2018-21134 — 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-2018-21134 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