CVE-2017-18737
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 by an unauthenticated attacker. This affects 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, R6220 before 1.1.0.50, R6700v2 before 1.2.0.4, R6800 before 1.2.0.4, R6900v2 before 1.2.0.4, WNDR3700v5 before 1.1.0.48, 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 confidenceUnauthenticated command injection vulnerability in multiple NETGEAR router models. An attacker can execute arbitrary operating system commands on the affected devices by sending specially crafted HTTP requests to the web management interface, potentially gaining full control of the device.
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.0.44< 1.0.1.10< 1.1.0.44< 1.0.0.18< 1.0.1.10< 1.1.0.50< 1.2.0.4< 1.2.0.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the NETGEAR router modelCheck the device label on the router chassis, or log into the web management interface and look for the model number usually displayed on the status or administration page, or identify it from network inventory or DHCP tablesAffected if The model matches one of the following: Jnr1010, Jr6150, Jwnr2010, Pr2000, R6050, R6220, R6700, or R6800
-
Determine the current firmware versionLog into the router web interface and navigate to the Administration or Firmware Upgrade section to view the installed firmware version. Alternatively, check the release notes or firmware download page for the deviceAffected if The installed firmware version is below the fixed version for your model (Jnr1010/Jwnr2010: 1.1.0.44, Jr6150/R6050: 1.0.1.10, Pr2000: 1.0.0.18, R6220: 1.1.0.50, R6700/R6800: 1.2.0.4)
-
Confirm the web management interface is accessibleAttempt to reach the router's HTTP or HTTPS management interface from the network segment where the device is deployedAffected if The web management interface (HTTP/HTTPS on ports 80 or 443 or custom ports) is reachable from an untrusted network segment
A user is affected if they have a NETGEAR router model from the affected list running a firmware version lower than the specified fix for that model, and the web management interface is accessible to potential attackers.
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.181.0.1.101.1.0.44
Update affected NETGEAR devices to the specified firmware versions. If firmware updates are unavailable, restrict network access to the device management interfaces (HTTP/HTTPS) to prevent unauthenticated attackers from reaching the web interface.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18737 — 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-18737 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