CVE-2017-18843
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 disclosure of administrative credentials. This affects R6700v2 before 1.1.0.38, R6800 before 1.1.0.38, and D7000 before 1.0.1.50.
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 confidenceThis vulnerability allows disclosure of administrative credentials on affected NETGEAR router models (R6700v2, R6800, D7000). An attacker who obtains these credentials can gain full administrative access to the device, potentially allowing configuration changes, network monitoring, or pivoting to connected networks.
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.0.38< 1.1.0.38< 1.0.1.50CVSS 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 192.168.1.1) and navigate to the Status or Router Information page to confirm the exact model number (R6700, R6800, or D7000)Affected if Model is R6700, R6800, or D7000
-
Check installed firmware versionIn the router web interface, locate the firmware version displayed on the Status or Router Information page. Note the full version number exactly as shown.Affected if Version number is visible and can be compared
-
For R6700 or R6800 models, compare your installed firmware version against 1.1.0.38. If your version is less than 1.1.0.38 (e.g., 1.1.0.36, 1.0.x.x), the device is vulnerable.Affected if Firmware version is below 1.1.0.38 on R6700 or R6800
-
For D7000 models, compare your installed firmware version against 1.0.1.50. If your version is less than 1.0.1.50 (e.g., 1.0.0.x), the device is vulnerable.Affected if Firmware version is below 1.0.1.50 on D7000
A device is affected if it is a Netgear R6700, R6800, or D7000 router running firmware version lower than 1.1.0.38 (R6700/R6800) or 1.0.1.50 (D7000).
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.501.1.0.38
Update firmware to R6700v2/R6800 version 1.1.0.38 or later, or D7000 version 1.0.1.50 or later. If credentials may have been compromised, change the administrative password immediately and review device configuration for unauthorized changes.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18843 — 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-18843 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