CVE-2017-18762
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 D3600 before 1.0.0.68, D6000 before 1.0.0.68, D6100 before 1.0.0.57, R6100 before 1.0.1.16, R6900P before 1.2.0.22, R7000 before 1.0.9.10, R7000P before 1.2.0.22, R7100LG before 1.0.0.40, WNDR3700v4 before 1.0.2.88, WNDR4300v1 before 1.0.2.90, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, and WNR2000v5 before 1.0.0.58.
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 (D3600, D6000, D6100, R6100, R6900P, R7000, R7000P, R7100LG, WNDR3700v4, WNDR4300v1/v2, WNDR4500v3, WNR2000v5) allows unauthenticated remote attackers to execute arbitrary commands on the underlying operating system via specially crafted input to vulnerable parameters.
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.0.0.68< 1.0.0.68< 1.0.0.57< 1.0.1.16< 1.2.0.22< 1.0.9.10< 1.2.0.22< 1.0.0.40CVSS 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 modelLocate the model number on the device label (usually on the bottom or back of the router) or log into the router admin interface and check the status page for the exact model designation (e.g., R7000, D3600, WNDR4300v1)Affected if The model matches one of the affected models: D3600, D6000, D6100, R6100, R6900P, R7000, R7000P, R7100LG, WNDR3700v4, WNDR4300v1/v2, WNDR4500v3, or WNR2000v5
-
Check the installed firmware versionLog into the router web interface (typically at 192.168.1.1 or 192.168.0.1) using admin credentials, then navigate to Administration > Router Update or Advanced > Administration > Firmware Update to view the current firmware versionAffected if The firmware version is below the threshold for your model: D3600/D6000 < 1.0.0.68, D6100 < 1.0.0.57, R6100 < 1.0.1.16, R6900P/R7000P < 1.2.0.22, R7000 < 1.0.9.10, R7100LG < 1.0.0.40, or WNDR3700v4/WNDR4300v1/v2/WNDR4500v3/WNR2000v5 with any version prior to patch (verify via NETGEAR support)
-
Verify if remote management is enabledIn the router admin interface, check under Advanced > Remote Management or Administration > Remote Management to see if remote access from the internet is enabledAffected if Remote management or remote access from WAN is enabled, making the device directly reachable from the internet on the configured port (typically 8443 or 8080)
You are affected if your router model matches one of the listed models AND the installed firmware version is below the specified threshold for that model, especially if remote management is accessible from the internet.
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.401.0.0.571.0.0.68
Upgrade affected NETGEAR devices to the specified firmware versions or later. If immediate patching is not possible, disable remote management interfaces and restrict network access to trusted users to reduce attack surface.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18762 — 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-18762 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