D3600 FirmwareOperating system · Netgear

CVE-2018-21210

HIGH · 8.8 CVSS v3.1 Published 2020-04-28
Fix available
A fix is available. Upgrade to 1.0.0.67 / 1.0.0.118 or later.
See remediation →
93/100
Remediation priority · Urgent
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 buffer overflow by an unauthenticated attacker. This affects D3600 before 1.0.0.67, D6000 before 1.0.0.67, D7800 before 1.0.1.30, EX2700 before 1.0.1.28, R6100 before 1.0.1.20, R7500 before 1.0.0.118, R7500v2 before 1.0.3.24, R7800 before 1.0.2.40, R9000 before 1.0.2.52, WN2000RPTv3 before 1.0.1.20, WN3000RPv3 before 1.0.2.50, WN3100RPv2 before 1.0.0.56, WNDR3700v4 before 1.0.2.96, WNDR4300 before 1.0.2.98, WNDR4300v2 before 1.0.0.50, and WNDR4500v3 before 1.0.0.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 multiple NETGEAR router models allows unauthenticated remote attackers to execute arbitrary code via specially crafted network requests. The vulnerability exists in the firmware web interface and can be exploited without authentication, potentially giving attackers full control of the affected device.

MitigationApply available firmware updates from NETGEAR for each affected model. If updates are unavailable, consider network segmentation to limit exposure and monitor for indicators of compromise.

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
D3600 FirmwareOperating system
Affected:< 1.0.0.67
D6000 FirmwareOperating system
Affected:< 1.0.0.67
D7800 FirmwareOperating system
Affected:< 1.0.1.30
Ex2700 FirmwareOperating system
Affected:< 1.0.1.28
R6100 FirmwareOperating system
Affected:< 1.0.1.20
R7500 FirmwareOperating system
Affected:< 1.0.0.118< 1.0.3.24
R7800 FirmwareOperating system
Affected:< 1.0.2.40
R900 FirmwareOperating system
Affected:< 1.0.2.52

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the NETGEAR router model
    Locate the model number on the device label or check the router web interface status page
    Affected if The model is D3600, D6000, D7800, Ex2700, R6100, R7500, R7800, or R900
  2. Check the installed firmware version
    Log into the router web interface and navigate to Administration > Firmware Update or Router Status page to view the current firmware version
    Affected if The firmware version is below 1.0.0.67 for D3600/D6000, below 1.0.1.30 for D7800, below 1.0.1.28 for Ex2700, below 1.0.1.20 for R6100, below 1.0.0.118 or 1.0.3.24 for R7500, below 1.0.2.40 for R7800, or below 1.0.2.52 for R900
  3. Verify the router web interface is accessible
    Attempt to reach the router IP address (typically 192.168.1.1) via HTTP/HTTPS from the network
    Affected if The router web interface is reachable and responds to requests - this is the attack surface
  4. Check if remote management is enabled
    In the router web interface, go to Advanced > Remote Management or similar settings to see if remote access to the web interface is enabled from WAN
    Affected if Remote management or WAN access to the web interface is enabled, increasing exposure to unauthenticated attackers

You are affected if you own one of the listed NETGEAR models AND your firmware version is below the specified threshold, since the vulnerability is in the web interface and exploitable without authentication.

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.

From vendor data
Upgrade available Upgrade to 1.0.0.67 / 1.0.0.118 / 1.0.1.20 or later
Fixed in 1.0.0.671.0.0.1181.0.1.20
Interim mitigation

Apply available firmware updates from NETGEAR for each affected model. If updates are unavailable, consider network segmentation to limit exposure and monitor for indicators of compromise.

Fix this in D3600 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-21210 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-21210 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