CVE-2017-18718
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 D6200 before 1.1.00.24, 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 · moderate confidenceStack-based buffer overflow vulnerability in multiple NETGEAR router models (D6200, R6700v2, R6800, R6900v2) allows unauthenticated remote attackers to execute arbitrary code via the vulnerable network service. The overflow occurs in firmware versions prior to the fixed releases (D6200 < 1.1.00.24, R6700v2/R6800/R6900v2 < 1.1.0.42).
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.1.00.24< 1.1.0.42< 1.1.0.42< 1.1.0.42CVSS 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 or access the router web interface (typically at 192.168.1.1) to confirm the exact model number (D6200, R6700, R6800, or R6900)Affected if Model is any of D6200, R6700, R6800, or R6900
-
Check firmware versionAccess the router web interface, navigate to the Administration or Firmware Update section, and record the installed firmware version numberAffected if Version cannot be determined or is not visible
-
Compare D6200 firmware versionIf model is D6200, compare the installed version against 1.1.00.24. Versions like 1.1.00.22, 1.1.00.18, or earlier are affectedAffected if Installed version is lower than 1.1.00.24 (e.g., 1.1.00.22 or earlier)
-
Compare R6700/R6800/R6900 firmware versionsIf model is R6700, R6800, or R6900, compare the installed version against 1.1.0.42. Versions like 1.1.0.38, 1.1.0.28, or earlier are affectedAffected if Installed version is lower than 1.1.0.42 (e.g., 1.1.0.38 or earlier)
-
Check remote management exposureVerify if the router web interface is accessible from the WAN/internet side (not just LAN). Check router settings under Remote Management or Web Service Access, or test connectivity by accessing your public IP from outside the local networkAffected if Remote management is enabled and accessible from WAN, increasing exposure to unauthenticated attackers
The device is affected if it is a D6200 with firmware below 1.1.00.24, or an R6700/R6800/R6900 with firmware below 1.1.0.42, and the router management interface is network-accessible.
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.1.00.241.1.0.42
Apply available firmware updates from NETGEAR to all affected devices. If updates are unavailable, restrict network access to router management interfaces and monitor for indicators of compromise.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18718 — 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-18718 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