dbcve.org
D7000 FirmwareOperating system · Netgear

CVE-2018-21169

HIGH · 8.8 CVSS v3.1 Published 2020-04-27
Fix available
A fix is available. Upgrade to 1.0.1.14 / 1.0.1.31 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 incorrect configuration of security settings. This affects D7000 before 2018-03-01, D7800 before 1.0.1.31, D8500 before 1.0.3.36, JNR1010v2 before 1.1.0.46, JR6150 before 1.0.1.14, JWNR2010v5 before 1.1.0.46, PR2000 before 2018-03-01, R6050 before 1.0.1.14, R6220 before 1.1.0.60, R6400 before 1.1.0.26, R6400v2 before 1.0.2.46, R6700v2 before 1.2.0.2, R6800 before 1.2.0.2, R6900v2 before 1.2.0.2, R7300DST before 1.0.0.56, R7500 before 1.0.0.112, R7500v2 before 1.0.3.24, R7800 before 1.0.2.36, R7900P before 1.1.4.6, R8000P before 1.1.4.6, R8300 before 1.0.2.104, R8500 before 1.0.2.104, R9000 before 1.0.2.52, WNDR3700v4 before 1.0.2.94, WNDR3700v5 before 1.1.0.50, WNDR4300 before 1.0.2.96, WNDR4300v2 before 1.0.0.52, WNDR4500v3 before 1.0.0.52, WNR1000v4 before 1.1.0.46, WNR2020 before 1.1.0.46, and WNR2050 before 1.1.0.46.

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

This vulnerability involves incorrect configuration of security settings in multiple NETGEAR router models. The specific security misconfiguration is not detailed in the available information, but it affects numerous router firmware versions prior to the patched releases listed.

MitigationUpdate the NETGEAR router firmware to the version specified in the advisory for each model (e.g., R6400 to version 1.1.0.26 or later).

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
D7000 FirmwareOperating system
Affected:< 2018-03-01
D7800 FirmwareOperating system
Affected:< 1.0.1.31
D8500 FirmwareOperating system
Affected:< 1.0.3.36
Jnr1010 FirmwareOperating system
Affected:< 1.1.0.46
Jr6150 FirmwareOperating system
Affected:< 1.0.1.14
Jwnr2010 FirmwareOperating system
Affected:< 1.1.0.46
Pr2000 FirmwareOperating system
Affected:< 2018-03-01
R6050 FirmwareOperating system
Affected:< 1.0.1.14

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 router model
    Locate the model number on the router device label or log into the router web admin interface (typically at 192.168.1.1) and check the status or dashboard page for the model name
    Affected if Model is D7000, D7800, D8500, Jnr1010, Jr6150, Jwnr2010, PR2000, or R6050
  2. Locate firmware version
    In the router web admin interface, navigate to Router Status, Advanced tab, or Administration section to find the current firmware version displayed
    Affected if Firmware version cannot be determined or is not displayed
  3. Compare D7000 or PR2000 version
    If the router is D7000 or PR2000, check if the firmware version date is earlier than 2018-03-01. The firmware date is usually shown on the status page or in the firmware upgrade section
    Affected if Firmware date is before March 1, 2018
  4. Compare D7800 version
    If the router is D7800, check if the firmware version is less than 1.0.1.31
    Affected if Firmware version is below 1.0.1.31
  5. Compare D8500 version
    If the router is D8500, check if the firmware version is less than 1.0.3.36
    Affected if Firmware version is below 1.0.3.36
  6. Compare Jnr1010, Jr6150, Jwnr2010, or R6050 version
    If the router is Jnr1010, Jr6150, Jwnr2010, or R6050, check the firmware version against the respective threshold: Jnr1010 and Jwnr2010 should be below 1.1.0.46; Jr6150 and R6050 should be below 1.0.1.14
    Affected if Firmware version is below the specified threshold for that model

The environment is affected if the router model matches one of the eight listed models AND the installed firmware version is 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.1.14 / 1.0.1.31 / 1.0.3.36 or later
Fixed in 1.0.1.141.0.1.311.0.3.36
Interim mitigation

Update the NETGEAR router firmware to the version specified in the advisory for each model (e.g., R6400 to version 1.1.0.26 or later).

Fix this in D7000 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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