dbcve.org
D6100 FirmwareOperating system · Netgear

CVE-2017-18764

HIGH · 8.8 CVSS v3.1 Published 2020-04-22
Fix available
A fix is available. Upgrade to 1.0.0.18 / 1.0.0.55 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 command injection by an unauthenticated attacker. This affects D6100 before 1.0.0.55, D7000 before 1.0.1.50, D7800 before 1.0.1.28, JNR1010v2 before 1.1.0.44, JR6150 before 1.0.1.10, JWNR2010v5 before 1.1.0.44, PR2000 before 1.0.0.18, R6050 before 1.0.1.10, R6100 before 1.0.1.14, R6120 before 1.0.0.30, R6220 before 1.1.0.50, R6700v2 before 1.2.0.4, R6800 before 1.2.0.4, R6900v2 before 1.2.0.4, R7500 before 1.0.0.110, R7500v2 before 1.0.3.20, R7800 before 1.0.2.36, R9000 before 1.0.2.52, WN3000RPv3 before 1.0.2.50, WNDR3700v4 before 1.0.2.88, WNDR3700v5 before 1.1.0.48, WNDR4300v1 before 1.0.2.90, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, WNR1000v4 before 1.1.0.44, WNR2000v5 before 1.0.0.58, WNR2020 before 1.1.0.44, and WNR2050 before 1.1.0.44.

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 pre-authentication command injection vulnerability allowing unauthenticated attackers to execute arbitrary operating system commands via the web interface. This critical flaw affects 28 different NETGEAR device models across multiple product lines.

MitigationApply the vendor-supplied firmware updates to each affected device model before the specified version thresholds. There are no practical workarounds for this unauthenticated command injection vulnerability.

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
D6100 FirmwareOperating system
Affected:< 1.0.0.55
D7000 FirmwareOperating system
Affected:< 1.0.1.50
D7800 FirmwareOperating system
Affected:< 1.0.1.28
Jnr1010 FirmwareOperating system
Affected:< 1.1.0.44
Jr6150 FirmwareOperating system
Affected:< 1.0.1.10
Jwnr2010 FirmwareOperating system
Affected:< 1.1.0.44
Pr2000 FirmwareOperating system
Affected:< 1.0.0.18
R6050 FirmwareOperating system
Affected:< 1.0.1.10

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 NETGEAR device model
    Check the device label on the router bottom or the web interface status page for the exact model number (e.g., D6100, D7000, D7800, Jnr1010, Jr6150, Jwnr2010, PR2000, R6050)
    Affected if The model matches any of the eight affected models listed in the CVE: D6100, D7000, D7800, Jnr1010, Jr6150, Jwnr2010, PR2000, or R6050
  2. Locate the firmware version
    Access the router web interface and navigate to the Administration or Firmware Upgrade section to find the current firmware version, or check the version displayed on the device status page
    Affected if The firmware version cannot be determined or is not displayed (may indicate the device is inaccessible or compromised)
  3. Compare firmware version against thresholds
    Match your installed firmware version to the specific threshold for your model: D6100 < 1.0.0.55, D7000 < 1.0.1.50, D7800 < 1.0.1.28, Jnr1010 < 1.1.0.44, Jr6150 < 1.0.1.10, Jwnr2010 < 1.1.0.44, PR2000 < 1.0.0.18, R6050 < 1.0.1.10
    Affected if Your firmware version is lower than the version threshold for your specific model (the device is vulnerable)
  4. Confirm web interface is accessible
    Verify the router web management interface is reachable on the local network (typically at http://192.168.1.1 or similar)
    Affected if The web interface is accessible - this confirms the attack surface exists (though the vulnerability is pre-authentication, so accessibility does not change the affected status)

You are affected if you own one of the eight listed NETGEAR models (D6100, D7000, D7800, Jnr1010, Jr6150, Jwnr2010, PR2000, R6050) and your current firmware version is below the threshold specified 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.18 / 1.0.0.55 / 1.0.1.10 or later
Fixed in 1.0.0.181.0.0.551.0.1.10
Interim mitigation

Apply the vendor-supplied firmware updates to each affected device model before the specified version thresholds. There are no practical workarounds for this unauthenticated command injection vulnerability.

Fix this in D6100 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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