CVE-2017-18708
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 R8300 before 1.0.2.94 and R8500 before 1.0.2.94.
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 NETGEAR R8300 and R8500 routers allows attackers to induce authenticated users to perform unintended administrative actions via crafted requests. The vulnerability exists in firmware versions prior to 1.0.2.94.
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.94< 1.0.2.94CVSS 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.
-
Access router web administration interfaceOpen a browser and navigate to the router's default IP address (typically 192.168.1.1). Log in with administrator credentials.Affected if You are able to access the router login page and authenticate
-
Locate firmware version informationIn the router web interface, look for a 'Firmware Version' or 'Router Info' section, typically found under 'Advanced', 'Administration', or 'Settings' menus.Affected if The displayed firmware version is lower than 1.0.2.94 (for example, 1.0.2.90, 1.0.2.88, etc.)
-
Check remote management settingIn the router web interface, navigate to 'Advanced' > 'Administration' > 'Remote Management' or similar. Verify whether remote access over WAN is enabled.Affected if Remote management is enabled and the router is accessible from the internet, increasing exposure to CSRF attacks from external networks
-
Confirm device modelVerify the exact model number displayed in the router interface or on the physical device label matches R8300 or R8500.Affected if The device is a NETGEAR R8300 or R8500 router
You are affected if your NETGEAR R8300 or R8500 router is running firmware version 1.0.2.94 or lower, and you access the admin interface either locally or remotely.
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.2.94
Upgrade NETGEAR R8300 and R8500 devices to firmware version 1.0.2.94 or later to remediate the CSRF vulnerability. Avoid accessing the router admin panel from untrusted networks until the update is applied.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18708 — 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-18708 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