dbcve.org
D6220 FirmwareOperating system · Netgear

CVE-2017-18850

HIGH · 8.4 CVSS v3.1 Published 2020-04-20
Fix available
A fix is available. Upgrade to 1.0.0.26 / 1.0.0.56 or later.
See remediation →
89/100
Remediation priority · High
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 authentication bypass. This affects D6220 before 1.0.0.26, D6400 before 1.0.0.60, D8500 before 1.0.3.29, R6250 before 1.0.4.12, R6400 before 1.01.24, R6400v2 before 1.0.2.30, R6700 before 1.0.1.22, R6900 before 1.0.1.22, R6900P before 1.0.0.56, R7000 before 1.0.9.4, R7000P before 1.0.0.56, R7100LG before 1.0.0.32, R7300DST before 1.0.0.54, R7900 before 1.0.1.18, R8000 before 1.0.3.44, R8300 before 1.0.2.100_1.0.82, and R8500 before 1.0.2.100_1.0.82.

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

Authentication bypass vulnerability in multiple NETGEAR router models (D6220, D6400, D8500, R6250, R6400, R6400v2, R6700, R6900, R6900P, R7000, R7000P, R7100LG, R7300DST, R7900, R8000, R8300, R8500) allows unauthenticated attackers to circumvent login mechanisms and gain administrative access to affected devices.

MitigationUpdate affected NETGEAR devices to the specified firmware versions (or later): D6220 to 1.0.0.26, D6400 to 1.0.0.60, D8500 to 1.0.3.29, R6250 to 1.0.4.12, R6400 to 1.0.1.24, R6400v2 to 1.0.2.30, R6700/R6900 to 1.0.1.22, R6900P/R7000P to 1.0.0.56, R7000 to 1.0.9.4, R7100LG to 1.0.0.32, R7300DST to 1.0.0.54, R7900 to 1.0.1.18, R8000 to 1.0.3.44, R8300/R8500 to 1.0.2.100_1.0.82. Restrict WAN access to router management interfaces if patching is delayed.

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
D6220 FirmwareOperating system
Affected:< 1.0.0.26
D6400 FirmwareOperating system
Affected:< 1.0.0.60
D8500 FirmwareOperating system
Affected:< 1.0.3.29
R6250 FirmwareOperating system
Affected:< 1.0.4.12
R6400 FirmwareOperating system
Affected:< 1.01.24< 1.0.2.30
R6700 FirmwareOperating system
Affected:< 1.0.1.22
R6900 FirmwareOperating system
Affected:< 1.0.1.22
R6900p FirmwareOperating system
Affected:< 1.0.0.56

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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 device label or access the router web interface (typically at 192.168.1.1) and check the status or administration page for the exact model designation
    Affected if Model is one of: D6220, D6400, D8500, R6250, R6400, R6400v2, R6700, R6900, R6900P, R7000, R7000P, R7100LG, R7300DST, R7900, R8000, R8300, R8500
  2. Check firmware version
    Access the router web interface, navigate to the Administration or Firmware Upgrade page, and locate the current firmware version number displayed
    Affected if Firmware version cannot be determined or is visible on the status page
  3. Compare D6220 version
    If model is D6220, compare your firmware version against 1.0.0.26
    Affected if Installed version is below 1.0.0.26
  4. Compare D6400 version
    If model is D6400, compare your firmware version against 1.0.0.60
    Affected if Installed version is below 1.0.0.60
  5. Compare D8500 version
    If model is D8500, compare your firmware version against 1.0.3.29
    Affected if Installed version is below 1.0.3.29
  6. Compare R6250 version
    If model is R6250, compare your firmware version against 1.0.4.12
    Affected if Installed version is below 1.0.4.12

Your device is affected if it is one of the listed NETGEAR models and its firmware version falls below the specified fixed version 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.26 / 1.0.0.56 / 1.0.0.60 or later
Fixed in 1.0.0.261.0.0.561.0.0.60
Interim mitigation

Update affected NETGEAR devices to the specified firmware versions (or later): D6220 to 1.0.0.26, D6400 to 1.0.0.60, D8500 to 1.0.3.29, R6250 to 1.0.4.12, R6400 to 1.0.1.24, R6400v2 to 1.0.2.30, R6700/R6900 to 1.0.1.22, R6900P/R7000P to 1.0.0.56, R7000 to 1.0.9.4, R7100LG to 1.0.0.32, R7300DST to 1.0.0.54, R7900 to 1.0.1.18, R8000 to 1.0.3.44, R8300/R8500 to 1.0.2.100_1.0.82. Restrict WAN access to router management interfaces if patching is delayed.

Fix this in D6220 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-2017-18850 — 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-2017-18850 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