CVE-2017-18756
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 D6220 before 1.0.0.32, D6400 before 1.0.0.66, D8500 before 1.0.3.35, DGN2200Bv4 before 1.0.0.94, DGN2200v4 before 1.0.0.94, R6250 before 1.0.4.14, R6300v2 before 1.0.4.18, R6400 before 1.01.32, R6400v2 before 1.0.2.44, R6700 before 1.0.1.36, R6900 before 1.0.1.30, R6900P before 1.3.0.8, R7000 before 1.0.9.14, R7000P before 1.3.0.8, R7100LG before 1.0.0.34, R7900 before 1.0.2.4, R8000 before 1.0.4.2, WN2500RPv2 before 1.0.1.50, WNDR3400v3 before 1.0.1.14, and WNDR4000 before 1.0.2.10.
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 in multiple NETGEAR router models (D6220, D6400, D8500, DGN2200Bv4, DGN2200v4, R6250, R6300v2, R6400, R6400v2, R6700, R6900, R6900P, R7000, R7000P, R7100LG, R7900, R8000, WN2500RPv2, WNDR3400v3, WNDR4000). The specific nature of the misconfiguration is not detailed in the advisory, but it allows attackers to potentially bypass security controls or gain unauthorized access.
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.32< 1.0.0.66< 1.0.3.35< 1.0.0.94< 1.0.0.94< 1.0.4.14< 1.0.4.18< 1.01.32< 1.0.2.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
- 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 NETGEAR router modelLocate the model number on the router device label or in the admin interface under 'Router Info' or 'Administration' > 'Router Status'Affected if Router model is D6220, D6400, D8500, DGN2200Bv4, DGN2200v4, R6250, R6300v2, R6400, R6400v2, R6700, R6900, R6900P, R7000, R7000P, R7100LG, R7900, R8000, WN2500RPv2, WNDR3400v3, or WNDR4000
-
Check installed firmware versionAccess router web interface, log in, and navigate to 'Administration' > 'Router Update' or 'Router Status' to view the current firmware versionAffected if Firmware version cannot be determined or is older than the patched version
-
Compare version against affected rangesMatch your router model and firmware version against the specific thresholds: D6220 < 1.0.0.32, D6400 < 1.0.0.66, D8500 < 1.0.3.35, DGN2200B/DGN2200 < 1.0.0.94, R6250 < 1.0.4.14, R6300 < 1.0.4.18, R6400 < 1.0.1.32 or < 1.0.2.44 (depending on hardware revision)Affected if Installed firmware version falls below the threshold listed for your specific model
You are affected if your NETGEAR router model matches one of the listed models AND your current firmware version is below the specified 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.321.0.0.661.0.0.94
Update router firmware to the versions specified in the advisory (e.g., R7000 to 1.0.9.14, R6400 to 1.0.1.32) or later to remediate the security misconfiguration.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18756 — 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-18756 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