CVE-2017-18709
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 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 · moderate confidenceNETGEAR R8300 and R8500 routers contain an incorrect configuration of security settings before firmware version 1.0.2.94, leading to a high-severity security vulnerability. The specific security settings misconfigured are not detailed in the available description, but the flaw allows attackers to potentially compromise the device or bypass security controls.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 modelLog into the router web interface (typically http://routerlogin.net or http://192.168.1.1) and navigate to the Administration or Router Status page to confirm the exact model number is R8300 or R8500Affected if Model is Netgear R8300 or R8500
-
Check firmware versionIn the router web interface, locate the firmware version information, usually found under Administration > Firmware Update or Router Status > Internet Port sectionAffected if Firmware version displayed is lower than 1.0.2.94 or version cannot be confirmed
-
Verify version via alternate method if neededIf unable to access web interface, check the firmware file name if firmware was previously downloaded, or access via telnet/SSH if enabled and run 'version' or 'get firmversion' commandAffected if Firmware version cannot be determined or is confirmed below 1.0.2.94
-
Cross-reference with NETGEAR support databaseVisit the official NETGEAR support page for your model and confirm the latest stable firmware version listed matches 1.0.2.94 or higherAffected if NETGEAR lists a version higher than your current installed version
Your router is affected if it is an R8300 or R8500 model running firmware version lower than 1.0.2.94, regardless of specific security setting configuration details.
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
Update NETGEAR R8300 and R8500 firmware to version 1.0.2.94 or later to remediate the security misconfiguration.
- 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-18709 — 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-18709 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