CVE-2017-18747
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 EX3700 before 1.0.0.64, EX3800 before 1.0.0.64, EX6000 before 1.0.0.24, EX6130 before 1.0.0.16, EX6400 before 1.0.1.60, EX7000 before 1.0.0.50, EX7300 before 1.0.1.60, and WN2500RPv2 before 1.0.1.46.
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 an incorrect configuration of security settings on multiple NETGEAR wireless range extender models (EX3700, EX3800, EX6000, EX6130, EX6400, EX7000, EX7300, WN2500RPv2). The specific nature of the misconfiguration is not detailed in the available description, but it is classified as a security setting misconfiguration rather than a code-level flaw.
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.64< 1.0.0.64< 1.0.0.24< 1.0.0.16< 1.0.1.60< 1.0.0.50< 1.0.1.60< 1.0.1.46CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 exact model numberLocate the model number on the device label or in the web management interface (typically at System > Device Information or similar). Confirm it matches one of: EX3700, EX3800, EX6000, EX6130, EX6400, EX7000, EX7300, or WN2500RPv2.Affected if The device is not one of these eight models, the device is not affected by this CVE.
-
Check the installed firmware versionAccess the extender's web interface (usually at 192.168.1.250 or mywifiext.net) and navigate to the firmware version or status page. The location varies by model but is typically under Settings, System, or Device Information.Affected if You cannot determine the firmware version, document this limitation in your assessment.
-
Compare firmware version against affected thresholdsMatch your model and version to the affected thresholds: EX3700/EX3800 < 1.0.0.64, EX6000 < 1.0.0.24, EX6130 < 1.0.0.16, EX6400 < 1.0.1.60, EX7000 < 1.0.0.50, EX7300 < 1.0.1.60, WN2500RP < 1.0.0.46 (note: advisory says 1.0.1.46 but mitigation says 1.0.0.46 - use the lower threshold for detection).Affected if The installed firmware version is below the threshold for your specific model.
Your device is affected if it is one of the eight models listed and its firmware version falls below the corresponding 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.161.0.0.241.0.0.50
Apply the corresponding firmware update to each affected device model before the specified version thresholds (EX3700/EX3800: 1.0.0.64, EX6000: 1.0.0.24, EX6130: 1.0.0.16, EX6400/EX7300: 1.0.1.60, EX7000: 1.0.0.50, WN2500RPv2: 1.0.0.46).
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18747 — 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-18747 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