CVE-2017-18867
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 D6100 before 1.0.0.55, D7800 before V1.0.1.24, R7100LG before V1.0.0.32, WNDR4300v1 before 1.0.2.90, 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 confidenceThis vulnerability involves incorrect security settings configuration in multiple NETGEAR router firmware versions. Affected devices include D6100, D7800, R7100LG, WNDR4300v1, and WNDR4500v3 running firmware versions before the patched releases. The specific security misconfiguration is not detailed, but the CVSS 6.8 indicates a moderate-severity configuration weakness that could be exploited.
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.55< 1.0.1.24< 1.0.0.32< 1.0.2.90< 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 router device label or log into the router web interface and check the status page for the model identifierAffected if Model is D6100, D7800, R7100LG, WNDR4300, or WNDR4500v3
-
Access router firmware versionLog into the router web interface (typically 192.168.1.1) and navigate to Administration > Router Status or Settings > Firmware Version to view the currently installed firmwareAffected if Router firmware version cannot be retrieved or is visible
-
Compare firmware version against affected rangesCheck the installed firmware version against the affected version thresholds: D6100 < 1.0.0.55, D7800 < 1.0.1.24, R7100LG < 1.0.0.32, WNDR4300 < 1.0.2.90, WNDR4500 < 1.0.0.48Affected if Installed version is lower than the patched version for that specific model
-
Verify firmware version sourceConfirm the firmware was obtained from official NETGEAR support pages, as third-party firmware may have different version numberingAffected if Firmware is from an unofficial source or modified
The environment is affected if the router model matches one of the affected models and the installed firmware version is below the patched threshold for that specific device.
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.481.0.0.55
Update the router firmware to the patched versions: D6100 to 1.0.0.55, D7800 to V1.0.1.24, R7100LG to V1.0.0.32, WNDR4300v1 to 1.0.2.90, and WNDR4500v3 to 1.0.0.48 or later. If updating is not possible, review and harden the router's security settings manually.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18867 — 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-18867 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