dbcve.org
D1500 FirmwareOperating system · Netgear

CVE-2018-21139

HIGH · 7.5 CVSS v3.1 Published 2020-04-23
Fix available
A fix is available. Upgrade to 1.0.0.27 / 1.0.0.46 or later.
See remediation →
84/100
Remediation priority · High
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 disclosure of sensitive information. This affects D1500 before 1.0.0.27, D500 before 1.0.0.27, D6100 before 1.0.0.58, D6200 before 1.1.00.30, D6220 before 1.0.0.46, D6400 before 1.0.0.82, D7000 before 1.0.1.68, D7000v2 before 1.0.0.51, D7800 before 1.0.1.42, D8500 before 1.0.3.42, DC112A before 1.0.0.40, DGN2200Bv4 before 1.0.0.102, DGN2200v4 before 1.0.0.102, JNR1010v2 before 1.1.0.54, JR6150 before 1.0.1.18, JWNR2010v5 before 1.1.0.54, PR2000 before 1.0.0.24, R6020 before 1.0.0.34, R6050 before 1.0.1.18, R6080 before 1.0.0.34, R6100 before 1.0.1.22, R6120 before 1.0.0.42, R6220 before 1.1.0.68, R6250 before 1.0.4.30, R6300v2 before 1.0.4.32, R6400 before 1.0.1.44, R6400v2 before 1.0.2.60, R6700 before 1.0.1.48, R6700v2 before 1.2.0.24, R6800 before 1.2.0.24, R6900 before 1.0.1.48, R6900P before 1.3.1.44, R6900v2 before 1.2.0.24, R7000 before 1.0.9.34, R7000P before 1.3.1.44, R7100LG before 1.0.0.48, R7300 before 1.0.0.68, R7500 before 1.0.0.124, R7500v2 before 1.0.3.38, R7900 before 1.0.2.16, R7900P before 1.4.1.24, R8000 before 1.0.4.18, R8000P before 1.4.1.24, R8300 before 1.0.2.122, R8500 before 1.0.2.122, WN3000RP before 1.0.0.68, WN3000RPv2 before 1.0.0.68, WNDR3400v3 before 1.0.1.18, WNDR3700v4 before 1.0.2.102, WNDR3700v5 before 1.1.0.54, WNDR4300v1 before 1.0.2.104, WNDR4300v2 before 1.0.0.56, WNDR4500v3 before 1.0.0.56, WNR1000v4 before 1.1.0.54, WNR2020 before 1.1.0.54, WNR2050 before 1.1.0.54, and WNR3500Lv2 before 1.2.0.54.

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 allows disclosure of sensitive information on multiple NETGEAR router and range extender models. The specific attack vector and nature of the exposed information are not detailed in the CVE entry, but the high CVSS score indicates significant risk from the information disclosure.

MitigationUpdate affected NETGEAR devices to the firmware versions specified in the advisory (e.g., D7000 before 1.0.1.68, R7000 before 1.0.9.34). If immediate patching is not possible, restrict network access to management interfaces.

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
D1500 FirmwareOperating system
Affected:< 1.0.0.27
D500 FirmwareOperating system
Affected:< 1.0.0.27
D6100 FirmwareOperating system
Affected:< 1.0.0.58
D6200 FirmwareOperating system
Affected:< 1.1.00.30
D6220 FirmwareOperating system
Affected:< 1.0.0.46
D6400 FirmwareOperating system
Affected:< 1.0.0.82
D7000 FirmwareOperating system
Affected:< 1.0.1.68< 1.0.0.51
D7800 FirmwareOperating system
Affected:< 1.0.1.42

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 device model
    Locate the device label on the router or access the admin interface (typically http://192.168.1.1) and check the device model name displayed in the status or system information page
    Affected if The device is one of the following models: D1500, D500, D6100, D6200, D6220, D6400, D7000, or D7800
  2. Locate the firmware version in the admin interface
    In the router web admin panel, navigate to System Info, Status, or About section. The firmware version is typically displayed as a field such as 'Firmware Version' or 'Software Version'. Record the exact version number shown
    Affected if A firmware version is displayed indicating the device is running the firmware from the affected product line
  3. Check D1500 firmware version
    Compare your installed firmware version against version 1.0.0.27. If your version is lower than 1.0.0.27, the device is affected
    Affected if Installed version is lower than 1.0.0.27 on a D1500 model
  4. Check D500 firmware version
    Compare your installed firmware version against version 1.0.0.27. If your version is lower than 1.0.0.27, the device is affected
    Affected if Installed version is lower than 1.0.0.27 on a D500 model
  5. Check D6100 firmware version
    Compare your installed firmware version against version 1.0.0.58. If your version is lower than 1.0.0.58, the device is affected
    Affected if Installed version is lower than 1.0.0.58 on a D6100 model
  6. Check D6200, D6220, D6400, D7800 firmware versions
    For D6200 compare against 1.1.00.30; for D6220 compare against 1.0.0.46; for D6400 compare against 1.0.0.82; for D7800 compare against 1.0.1.42. If your version is lower than the respective threshold, the device is affected
    Affected if Installed version is lower than the specified threshold for the respective model (D6200 < 1.1.00.30, D6220 < 1.0.0.46, D6400 < 1.0.0.82, D7800 < 1.0.1.42)

A defender is affected if they are running any of the listed NETGEAR models (D1500, D500, D6100, D6200, D6220, D6400, D7000, D7800) with a firmware version below the specific 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.27 / 1.0.0.46 / 1.0.0.51 or later
Fixed in 1.0.0.271.0.0.461.0.0.51
Interim mitigation

Update affected NETGEAR devices to the firmware versions specified in the advisory (e.g., D7000 before 1.0.1.68, R7000 before 1.0.9.34). If immediate patching is not possible, restrict network access to management interfaces.

Fix this in D1500 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-21139 — 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-21139 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