CVE-2017-18724
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 · high confidenceA stack-based buffer overflow vulnerability in NETGEAR router models D6200, R6700v2, R6800, and R6900v2 allows unauthenticated remote attackers to potentially execute arbitrary code or cause a denial of service. The vulnerability exists in the firmware versions prior to the specified patches.
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 modelLog into the router web admin interface (typically http://routerlogin.net or http://192.168.1.1) and navigate to the Status or Router Information page to locate the model numberAffected if Model is D6200, R6700v2, R6800, or R6900v2
-
Identify installed firmware versionIn the same router admin interface, locate the firmware version field on the Status or Administration pageAffected if Firmware version is displayed and can be compared
-
Compare D6200 firmware versionIf model is D6200, compare installed version against 1.1.00.24Affected if Installed version is less than 1.1.00.24
-
Compare R6700/R6800/R6900 firmware versionIf model is R6700v2, R6800, or R6900v2, compare installed version against 1.1.0.42Affected if Installed version is less than 1.1.0.42
The router is affected if it is a D6200 with firmware below 1.1.00.24, or an R6700v2/R6800/R6900v2 with firmware below 1.1.0.42.
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
Update affected NETGEAR router firmware to version 1.1.00.24 or later for D6200, and version 1.1.0.42 or later for R6700v2/R6800/R6900v2. If patching is not possible, restrict network access to trusted users or disable the vulnerable service.
- Consultation3.0 h
- Implementation4.0 h
- Testing5.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18724 — 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-18724 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