dbcve.org
D3600 FirmwareOperating system · Netgear

CVE-2018-21223

HIGH · 8.8 CVSS v3.1 Published 2020-04-28
Fix available
A fix is available. Upgrade to 1.0.0.50 / 1.0.0.67 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, R6100 before 1.0.1.20, R7500 before 1.0.0.118, R7500v2 before 1.0.3.24, R9000 before 1.0.2.52, WNDR3700v4 before 1.0.2.96, WNDR4300 before 1.0.2.98, WNDR4300v2 before 1.0.0.50, WNDR4500v3 before 1.0.0.50, and WNR2000v5 before 1.0.0.62.

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

Multiple NETGEAR router models contain a buffer overflow vulnerability that can be exploited by an unauthenticated attacker to execute arbitrary code or cause denial of service. The vulnerability exists in the firmware of specific versions of D3600, D6000, D7800, R6100, R7500, R7500v2, R9000, WNDR3700v4, WNDR4300, WNDR4300v2, WNDR4500v3, and WNR2000v5 devices.

MitigationUpdate affected devices to the minimum patched firmware versions specified in the advisory: D3600/D6000 to 1.0.0.67, D7800 to 1.0.1.30, R6100 to 1.0.1.20, R7500 to 1.0.0.118, R7500v2 to 1.0.3.24, R9000 to 1.0.2.52, WNDR3700v4 to 1.0.2.96, WNDR4300 to 1.0.2.98, WNDR4300v2/WNDR4500v3 to 1.0.0.50, and WNR2000v5 to 1.0.0.62.

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
R6100 FirmwareOperating system
Affected:< 1.0.1.20
R7500 FirmwareOperating system
Affected:< 1.0.0.118< 1.0.3.24
R9000 FirmwareOperating system
Affected:< 1.0.2.52
Wndr3700 FirmwareOperating system
Affected:< 1.0.2.96
Wndr4300 FirmwareOperating system
Affected:< 1.0.2.98< 1.0.0.50

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 router model
    Locate the model number on the device label on the bottom or back of the router, or check the web admin interface typically at 192.168.1.1 for the model name
    Affected if The model is one of: D3600, D6000, D7800, R6100, R7500, R7500v2, R9000, WNDR3700v4, WNDR4300, WNDR4300v2, WNDR4500v3, or WNR2000v5
  2. Locate the firmware version
    Access the router web admin interface and navigate to the Administration, Firmware, or Status section to view the current firmware version; alternatively, check the release notes or firmware file name if manually downloaded
    Affected if Unable to determine the installed firmware version from the router interface or documentation
  3. Compare D3600/D6000 version against affected range
    Check if firmware version is less than 1.0.0.67
    Affected if Installed version is below 1.0.0.67 on D3600 or D6000
  4. Compare D7800 version against affected range
    Check if firmware version is less than 1.0.1.30
    Affected if Installed version is below 1.0.1.30 on D7800
  5. Compare R6100, R7500v2, R9000, WNDR3700v4 versions against affected ranges
    Check if R6100 < 1.0.1.20, R7500v2 < 1.0.3.24, R9000 < 1.0.2.52, or WNDR3700v4 < 1.0.2.96
    Affected if Any of these models run firmware below their respective thresholds
  6. Compare R7500 and WNDR4300 series versions against affected ranges
    Check if R7500 < 1.0.0.118, WNDR4300 < 1.0.2.98, or WNDR4300v2/WNDR4500v3 < 1.0.0.50
    Affected if R7500 is below 1.0.0.118, WNDR4300 is below 1.0.2.98, or WNDR4300v2/WNDR4500v3 is below 1.0.0.50

The device is affected if it matches one of the listed models AND its firmware version falls below the specified threshold for that model.

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.50 / 1.0.0.67 / 1.0.0.118 or later
Fixed in 1.0.0.501.0.0.671.0.0.118
Interim mitigation

Update affected devices to the minimum patched firmware versions specified in the advisory: D3600/D6000 to 1.0.0.67, D7800 to 1.0.1.30, R6100 to 1.0.1.20, R7500 to 1.0.0.118, R7500v2 to 1.0.3.24, R9000 to 1.0.2.52, WNDR3700v4 to 1.0.2.96, WNDR4300 to 1.0.2.98, WNDR4300v2/WNDR4500v3 to 1.0.0.50, and WNR2000v5 to 1.0.0.62.

Fix this in D3600 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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