CVE-2017-18787
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 allows unauthenticated attackers to execute arbitrary commands on the affected device via unspecified input vectors. The vulnerability affects the web management interface of these routers.
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 modelAccess the router web management interface (typically at 192.168.1.1) and check the status or device information page to confirm the exact model number. Alternatively, check the physical device label.Affected if Model is D6200, Jnr1010, Jr6150, Jwnr2010, Pr2000, R6050, Wnr1000, or Wnr2020
-
Locate firmware versionIn the router web management interface, navigate to the Status or Administration section to view the current firmware version. This is typically displayed as a version number such as '1.0.0.18' or similar.Affected if Firmware version cannot be determined or is not displayed
-
Compare version against affected rangesCross-reference the identified model and firmware version against the following thresholds: 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.44Affected if Firmware version is lower than the threshold for that specific model
If the router model matches one of the eight affected models and the installed firmware version is below the corresponding threshold, the device is vulnerable to unauthenticated command injection via the web interface.
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 the vendor-supplied firmware update to the patched version for each specific model. If updates are unavailable, restrict network access to the router management interface or consider replacement.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2017-18787 — 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-18787 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