CVE-2017-18705
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 incorrect configuration of security settings. This affects D7800 before 1.0.1.28, R6100 before 1.0.1.20, R7500 before 1.0.0.118, R7500v2 before 1.0.3.20, R7800 before 1.0.2.40, R9000 before 1.0.2.52, WNDR3700v4 before 1.0.2.88, WNDR4300 before 1.0.2.90, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, and WNR2000v5 before 1.0.0.62.
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 · moderate confidenceThis vulnerability involves incorrect configuration of security settings on multiple NETGEAR router models, including D7800, R6100, R7500, R7500v2, R7800, R9000, WNDR3700v4, WNDR4300, WNDR4300v2, WNDR4500v3, and WNR2000v5. The improper security settings configuration could allow unauthorized access or bypass of security controls, resulting in a HIGH severity vulnerability with CVSS score of 8.8.
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.1.28< 1.0.1.20< 1.0.0.118< 1.0.3.20< 1.0.2.40< 1.0.2.52< 1.0.2.88< 1.0.2.90< 1.0.0.48< 1.0.0.48CVSS 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 router device label or check the router web interface (typically at 192.168.1.1) under the Administration or Status sectionAffected if The model is one of: D7800, R6100, R7500, R7500v2, R7800, R9000, WNDR3700v4, WNDR4300, WNDR4300v2, WNDR4500v3, or WNR2000v5
-
Check the installed firmware versionLog into the router web interface and navigate to Administration > Router Update or Status page to view the current firmware version. Alternatively, access the router via CLI and run 'nvram get firmware_version' or check the firmware file name displayed in the interfaceAffected if The displayed firmware version cannot be verified or is lower than the fixed version thresholds
-
Compare against affected version rangesReference the specific affected version ranges: D7800 < 1.0.1.28, R6100 < 1.0.1.20, R7500 < 1.0.0.118 (or < 1.0.3.20 for v2), R7800 < 1.0.2.40, R9000 < 1.0.2.52, WNDR3700v4 < 1.0.2.88, WNDR4300 < 1.0.2.90 (or < 1.0.0.48 for v2), WNDR4500v3 < 1.0.0.48, WNR2000v5 < 1.0.0.62Affected if The installed firmware version falls below the specified threshold for that model
-
Verify remote management exposureCheck if the router's web management interface is accessible from the WAN (internet) side by attempting to access the router's external IP on ports 80/443, or review the router's Remote Management settings under Advanced > Administration > Remote ManagementAffected if Remote management is enabled and the router firmware is below the fixed version, increasing exposure to exploitation
The router is affected if it is one of the listed models AND its current firmware version is below the fixed version threshold for that model.
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.481.0.0.1181.0.1.20
Update the router firmware to the fixed versions specified: D7800 to 1.0.1.28, R6100 to 1.0.1.20, R7500 to 1.0.0.118, R7500v2 to 1.0.3.20, R7800 to 1.0.2.40, R9000 to 1.0.2.52, WNDR3700v4 to 1.0.2.88, WNDR4300 to 1.0.2.90, WNDR4300v2 to 1.0.0.48, WNDR4500v3 to 1.0.0.48, and WNR2000v5 to 1.0.0.62.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18705 — 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-18705 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