CVE-2017-18786
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 · uneditedCertain NETGEAR devices are affected by command injection. This affects D6200 before 1.1.00.24, JNR1010v2 before 1.1.0.44, JR6150 before 1.0.1.12, JWNR2010v5 before 1.1.0.44, PR2000 before 1.0.0.20, R6050 before 1.0.1.12, WNR1000v4 before 1.1.0.44, 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 confidenceCommand injection vulnerability in multiple NETGEAR router models (D6200, JNR1010v2, JR6150, JWNR2010v5, PR2000, R6050, WNR1000v4, WNR2020, WNR2050) allowing authenticated attackers to execute arbitrary commands through unspecified input vectors in the web management interface.
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< 1.1.00.24< 1.1.0.44< 1.0.1.12< 1.1.0.44< 1.0.0.20< 1.0.1.12< 1.1.0.44< 1.1.0.44CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLocate the model number on the device label or log into the web management interface and check the status or administration page for the exact model designationAffected if Model is D6200, JNR1010v2, JR6150, JWNR2010v5, PR2000, R6050, WNR1000v4, WNR2020, or WNR2050
-
Check firmware versionIn the web management interface, navigate to Administration > Firmware Update or similar section to view the current firmware version. Alternatively, access the device via telnet or SSH and run 'version' or 'cat /proc/version' if availableAffected if Firmware version is below the threshold for your model (D6200: < 1.1.00.24, JNR1010: < 1.1.0.44, JR6150: < 1.0.1.12, JWNR2010: < 1.1.0.44, PR2000: < 1.0.0.20, R6050: < 1.0.1.12, WNR1000: < 1.1.0.44, WNR2020: < 1.1.0.44)
-
Verify web management interface accessibilityAttempt to access the router web interface from internal and external networks. Check if remote management is enabled under Administration > Remote Management or similar settingsAffected if The web management interface is accessible from untrusted networks or the internet
-
Confirm authentication requirementDetermine if default administrator credentials are still in use or if weak credentials have been configured. Try logging into the web interface with common default credentialsAffected if Attacker can obtain valid administrative credentials through default passwords, weak passwords, or credential compromise
You are affected if your NETGEAR router model matches one of the listed models, your firmware version is below the specified threshold, and an attacker can access the web management interface with valid administrative credentials.
Generated from the published advisory. Verify against your own configuration.
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 data1.0.0.201.0.1.121.1.00.24
Apply vendor-supplied firmware updates to all affected devices; if updates unavailable, restrict administrative access to trusted networks or disable remote management.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18786 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-18786 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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