CVE-2017-18711
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, R6400 before 1.01.32, R6400v2 before 1.0.2.44, R6700 before 1.0.1.36, R6900 before 1.0.1.34, R6900P before 1.3.0.8, R7000 before 1.0.9.14, R7000P before 1.3.0.8, R7500v2 before 1.0.3.20, R7800 before 1.0.2.40, R9000 before 1.0.2.52, WNDR4300v2 before 1.0.0.48, and WNDR4500v3 before 1.0.0.48.
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 confidenceMultiple NETGEAR router models (D7800, R6400, R6700, R7000, R7800, R9000, and others) contain an incorrect configuration of security settings, allowing network-adjacent attackers to exploit weak or missing security controls. The specific misconfiguration is not detailed but is rated HIGH severity with CVSS 8.8, indicating potential for unauthorized access or privilege escalation.
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.32< 1.0.2.44< 1.0.3.20< 1.0.2.40< 1.0.2.52< 1.0.0.48< 1.0.0.48< 1.3.0.8CVSS 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 router modelLocate the model number on the device label (usually on the bottom or back of the router) or log into the web admin interface and check the status or about pageAffected if The model is one of: D7800, R6400, R6700, R7000, R7800, R9000, R7500, R7000p, Wndr4300, or Wndr4500
-
Check installed firmware versionLog into the router admin interface (typically at 192.168.1.1) and navigate to Administration > Firmware Update or Advanced > Administration > Router Status to view the current firmware versionAffected if The displayed firmware version is below the threshold for your specific model
-
Compare version to affected rangesReference the following thresholds for your model: D7800 < 1.0.1.28; R6400 < 1.0.1.32 or < 1.0.2.44; R7500 < 1.0.3.20; R7800 < 1.0.2.40; R9000 < 1.0.2.52; Wndr4300 < 1.0.0.48; Wndr4500 < 1.0.0.48; R7000p < 1.3.0.8Affected if Your installed firmware version falls below the listed threshold for your model
-
Verify router admin interface accessibilityCheck if the router web management interface is accessible from outside your local network (WAN side). This can be tested by attempting to access your public IP on port 80/443, or check Port Forwarding/Remote Management settings in the admin interface under Advanced > Administration > Remote ManagementAffected if Remote management is enabled or the admin interface is exposed to the WAN
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.481.0.1.281.0.1.32
Apply the available firmware updates from NETGEAR for each affected model to the specified versions or later. For out-of-support devices, consider replacement with currently supported hardware.
- 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-18711 — 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-18711 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