CVE-2017-18768
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 CSRF. This affects EX6100 before 1.0.2.16_1.1.130, EX6100v2 before 1.0.1.70, EX6150v2 before 1.0.1.54, EX6200v2 before 1.0.1.50, EX6400 before 1.0.1.60, EX7300 before 1.0.1.60, and WN3000RPv3 before 1.0.2.44.
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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in multiple NETGEAR wireless range extenders (EX6100, EX6100v2, EX6150v2, EX6200v2, EX6400, EX7300, WN3000RPv3) allows remote attackers to perform unauthorized administrative actions by tricking authenticated users into visiting malicious web pages.
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.2.16_1.1.130< 1.0.1.70< 1.0.1.54< 1.0.1.50< 1.0.1.60< 1.0.1.60< 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 range extender model on your networkLocate the device physically or check your network devices list for models EX6100, EX6100v2, EX6150v2, EX6200v2, EX6400, EX7300, or WN3000RPv3Affected if The device is one of these seven models and is present on your network
-
Check the installed firmware versionAccess the device admin interface (typically http://www.mywifiext.com or http://192.168.1.250) and navigate to Settings > Firmware Update, or check the web interface footer for the version numberAffected if The firmware version is lower than 1.0.2.16 for EX6100, lower than 1.0.1.54 for EX6150, lower than 1.0.1.50 for EX6200, lower than 1.0.1.60 for EX6400 or EX7300, or lower than 1.0.2.44 for WN3000RP
-
Verify the web admin interface is accessibleAttempt to reach the device admin page via a browser on the same network segmentAffected if The web interface is reachable and responds, meaning an authenticated session could potentially be exploited via CSRF
-
Confirm remote management is enabled (if applicable)In the device web interface, check Settings > Remote Management or Administration > Remote Management settingsAffected if Remote management is enabled and the interface is accessible from outside the local network, increasing the attack surface
You are affected if you have any of the listed NETGEAR range extender models running firmware versions below the specified thresholds and the web admin interface is accessible on your network.
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.1.501.0.1.541.0.1.60
Update affected devices to the latest firmware versions provided by NETGEAR. If updates are unavailable, avoid browsing untrusted sites while logged into the device admin interface and consider network segmentation.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18768 — 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-18768 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