CVE-2017-18844
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 · moderate 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 enabling further network compromise.
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.
-
Access router administration interfaceLog into the router's web interface using the default or configured IP address (typically 192.168.1.1) and navigate to the firmware version or status pageAffected if The router is accessible over the network and displays a firmware version
-
Locate firmware version displayFind the firmware version displayed on the router status or administration page, typically labeled as 'Firmware Version' or 'Router Version'Affected if The displayed version cannot be verified against the fixed versions
-
Compare installed version to affected rangesNote the exact firmware version string shown on the router interface and compare it to: R6700 < 1.1.0.38, R6800 < 1.1.0.38, D7000 < 1.0.1.50Affected if The installed firmware version falls below the specified version for your model
-
Confirm router modelIdentify the exact router model number (R6700v2, R6800, or D7000) from the router label or admin interfaceAffected if The router is not one of the three affected models
If the router is a R6700v2, R6800, or D7000 model and the displayed firmware version is below 1.1.0.38 (for R6700v2/R6800) or below 1.0.1.50 (for D7000), the device is affected by this credential disclosure vulnerability.
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 router firmware to version 1.1.0.38 or later for R6700v2/R6800, and 1.0.1.50 or later for D7000. If updates are unavailable, restrict administrative interface access to trusted networks only.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18844 — 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-18844 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