CVE-2017-18726
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 a stack-based buffer overflow by an unauthenticated attacker. This affects R6020 before 1.0.0.30, R6080 before 1.0.0.30, R6700v2 before 1.1.0.42, R6800 before 1.1.0.42, and R6900v2 before 1.1.0.42.
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 confidenceStack-based buffer overflow vulnerability in multiple NETGEAR router models (R6020, R6080, R6700v2, R6800, R6900v2) allows unauthenticated remote attackers to execute arbitrary code via specially crafted input to affected firmware components.
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.30< 1.1.0.42< 1.1.0.42< 1.1.0.42< 1.0.0.30CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 modelCheck the device label on the router or log into the web admin interface (typically 192.168.1.1) and look for the model number displayed on the main status pageAffected if Model is R6020, R6080, R6700, R6700v2, R6800, R6900, or R6900v2
-
Check installed firmware versionIn the web admin interface, navigate to the Administration or Advanced settings section and look for Firmware Version or Router Status. The version is typically displayed as a number like 1.0.0.x or 1.1.0.xAffected if For R6020/R6080: version is below 1.0.0.30; for R6700v2/R6800/R6900v2: version is below 1.1.0.42
-
Verify remote management is enabledIn the web admin interface, go to Advanced > Remote Management or Administration > Router Update and check if remote access via WAN is enabled. Look for options like Enable Remote Management, Allow WAN Access, or Web GUI Access from WANAffected if Remote management or WAN access to the admin interface is enabled and the router is directly reachable from the internet
-
Check network exposureDetermine if the router's WAN IP is directly accessible from the internet by accessing your public IP address on port 80/443, or use an external port scanner. Alternatively, check if the router has port forwarding or DMZ configured that exposes management portsAffected if The router management interface (HTTP/HTTPS on ports 80/443) is exposed to the WAN/internet without firewall protection
The environment is affected if the router model is one of the affected models AND the installed firmware version is below the threshold AND the management interface is accessible from the network where the attacker would send the specially crafted input.
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.301.1.0.42
Apply vendor firmware updates: upgrade R6020/R6080 to version 1.0.0.30 or later, and R6700v2/R6800/R6900v2 to version 1.1.0.42 or later. If patching is not feasible, isolate affected devices behind a firewall and restrict WAN access.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18726 — 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-18726 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