dbcve.org
D1500 FirmwareOperating system · Netgear

CVE-2018-21231

MEDIUM · 5.4 CVSS v3.1 Published 2020-04-24
Fix available
A fix is available. Upgrade to 1.0.0.27 / 1.0.0.40 or later.
See remediation →
59/100
Remediation priority · Elevated
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 D1500 before 1.0.0.27, D500 before 1.0.0.27, D6100 before 1.0.0.57, D6220 before 1.0.0.40, D6400 before 1.0.0.74, D7000 before 1.0.1.60, D7800 before 1.0.1.34, D8500 before 1.0.3.39, DGN2200v4 before 1.0.0.94, DGN2200Bv4 before 1.0.0.94, EX2700 before 1.0.1.42, EX3700 before 1.0.0.64, EX3800 before 1.0.0.64, EX6000 before 1.0.0.24, EX6100 before 1.0.2.18, EX6120 before 1.0.0.32, EX6130 before 1.0.0.22, EX6150 before 1.0.0.34_1.0.70, EX6200 before 1.0.3.82_1.1.117, EX6400 before 1.0.1.78, EX7000 before 1.0.0.56, EX7300 before 1.0.1.78, JNR1010v2 before 1.1.0.42, JR6150 before 1.0.1.10, JWNR2010v5 before 1.1.0.42, PR2000 before 1.0.0.22, R6050 before 1.0.1.10, R6100 before 1.0.1.16, R6220 before 1.1.0.50, R6250 before 1.0.4.14, R6300v2 before 1.0.4.12, R6400v2 before 1.0.2.34, R6700 before 1.0.1.26, R6900 before 1.0.1.26, R6900P before 1.2.0.22, R7000 before 1.0.9.6, R7000P before 1.2.0.22, R7100LG before 1.0.0.40, R7300DST before 1.0.0.54, R7500 before 1.0.0.110, R7500v2 before 1.0.3.26, R7800 before 1.0.2.44, R7900 before 1.0.1.26, R8000 before 1.0.3.48, R8300 before 1.0.2.104, R8500 before 1.0.2.104, R9000 before 1.0.3.10, WN2000RPTv3 before 1.0.1.26, WN2500RPv2 before 1.0.1.46, WN3000RPv3 before 1.0.2.66, WN3100RPv2 before 1.0.0.56, WNDR3400v3 before 1.0.1.14, WNDR3700v4 before 1.0.2.96, WNDR3700v5 before 1.1.0.54, WNDR4300 before 1.0.2.98, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, WNR1000v4 before 1.1.0.42, WNR2000v5 before 1.0.0.64, WNR2020 before 1.1.0.42, and WNR2050 before 1.1.0.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 · moderate confidence

Multiple NETGEAR router and range extender models contain an incorrect configuration of security settings in their firmware. The vulnerability exists across a wide range of device models (D, R, EX, JNR, JR, JWNR, PR, WNDR, WNR series) running firmware versions below the specified thresholds, allowing potential security bypass or exposure due to improper security settings.

MitigationUpdate affected NETGEAR devices to the firmware versions specified in the advisory (e.g., D1500 to 1.0.0.27, R7000 to 1.0.9.6) or later to remediate the security misconfiguration.

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.57
D6220 FirmwareOperating system
Affected:< 1.0.0.40
D6400 FirmwareOperating system
Affected:< 1.0.0.74
D7000 FirmwareOperating system
Affected:< 1.0.1.60
D7800 FirmwareOperating system
Affected:< 1.0.1.34
D8500 FirmwareOperating system
Affected:< 1.0.3.39

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 NETGEAR device model
    Check the device label on the router or access the web administration interface (typically at 192.168.1.1) to view the model name (such as D1500, D500, D6100, D6220, D6400, D7000, D7800, or D8500)
    Affected if The device model is one of the D-series models listed in the affected products
  2. Locate firmware version in web interface
    Log into the router admin panel, navigate to the Firmware Update or Administration section, and locate the current firmware version displayed
    Affected if The displayed firmware version is visible and can be compared against thresholds
  3. Compare firmware version to affected threshold
    Match your device model to its threshold: D1500/D500 < 1.0.0.27, D6100 < 1.0.0.57, D6220 < 1.0.0.40, D6400 < 1.0.0.74, D7000 < 1.0.1.60, D7800 < 1.0.1.34, D8500 < 1.0.3.39
    Affected if The installed firmware version is lower than the threshold for your specific model
  4. Verify security settings accessibility
    Check if the router web interface allows access to security configuration pages (such as firewall, access control, or wireless security settings) without proper authentication prompts or with weakened security options exposed
    Affected if Security settings are accessible without proper authentication or display misconfigured options

You are affected if your NETGEAR device model matches one of the D-series models and its firmware version is below the specified threshold, indicating the security misconfiguration is present.

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.40 / 1.0.0.57 or later
Fixed in 1.0.0.271.0.0.401.0.0.57
Interim mitigation

Update affected NETGEAR devices to the firmware versions specified in the advisory (e.g., D1500 to 1.0.0.27, R7000 to 1.0.9.6) or later to remediate the security misconfiguration.

Fix this in D1500 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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