CVE-2017-18765
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 denial of service. This affects R6300v2 before 1.0.4.8, R6400 before 1.0.1.22, R6400v2 before 1.0.2.32, R6700 before 1.0.1.20, R6900 before 1.0.1.20, WNR3500Lv2 before 1.2.0.44, and WNR2000v2 before 1.2.0.8.
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 confidenceA denial of service vulnerability exists in multiple NETGEAR router models (R6300v2, R6400, R6400v2, R6700, R6900, WNR3500Lv2, WNR2000v2) running firmware versions prior to the specified thresholds. The vulnerability allows an attacker to potentially crash or make the device unavailable, though the specific attack vector and technical details are not provided in this description.
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.4.8< 1.0.1.22< 1.0.2.32< 1.0.1.20< 1.0.1.20< 1.2.0.44< 1.2.0.8CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 router modelLocate the model number on the device label (usually on the bottom or back of the router) or log into the router admin interface and check the status or device info pageAffected if The model is R6300v2, R6400, R6400v2, R6700, R6900, WNR3500Lv2, or WNR2000v2 - otherwise this CVE does not apply
-
Determine the current firmware versionLog into the router web interface (typically at 192.168.1.1) and navigate to Router Status or Administration > Firmware Update section to view the installed firmware versionAffected if The displayed firmware version cannot be read or does not match the NETGEAR firmware versioning format for the identified model
-
Compare firmware version against affected ranges for R6300v2If the model is R6300v2, compare the installed version number to 1.0.4.8Affected if Installed version is earlier than 1.0.4.8 (e.g., 1.0.4.7, 1.0.3.x, etc.)
-
Compare firmware version against affected ranges for R6400If the model is R6400, identify whether it runs the 1.0.1.x or 1.0.2.x firmware branch, then compare to the respective threshold (1.0.1.22 or 1.0.2.32)Affected if Installed version is earlier than 1.0.1.22 (for 1.0.1.x branch) or earlier than 1.0.2.32 (for 1.0.2.x branch)
-
Compare firmware version against affected ranges for R6700 or R6900If the model is R6700 or R6900, compare the installed version to 1.0.1.20Affected if Installed version is earlier than 1.0.1.20 (e.g., 1.0.0.x, 1.0.1.18, etc.)
-
Compare firmware version against affected ranges for WNR3500Lv2 or WNR2000v2If the model is WNR3500Lv2, compare to 1.2.0.44; if WNR2000v2, compare to 1.2.0.8Affected if WNR3500Lv2 version is earlier than 1.2.0.44, or WNR2000v2 version is earlier than 1.2.0.8
The device is affected if it is one of the listed NETGEAR models (R6300v2, R6400, R6400v2, R6700, R6900, WNR3500Lv2, WNR2000v2) AND its current firmware version falls below the version threshold specified 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.1.201.0.1.221.0.2.32
Update affected NETGEAR devices to the specified firmware versions (R6300v2: 1.0.4.8, R6400: 1.0.1.22, R6400v2: 1.0.2.32, R6700/R6900: 1.0.1.20, WNR3500Lv2: 1.2.0.44, WNR2000v2: 1.2.0.8) or later to remediate this vulnerability.
- 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-18765 — 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-18765 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