CVE-2017-18847
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 an attacker's ability to read arbitrary files. This affects R6400v2 before 1.0.2.32, R7000P/R6900P before 1.0.0.56, R7900 before 1.0.1.18, R8300 before 1.0.2.100_1.0.82, R8500 before 1.0.2.100_1.0.82, and D8500 before 1.0.3.29.
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 is a file disclosure vulnerability in NETGEAR routers allowing authenticated attackers to read arbitrary files on the device, likely due to a path traversal flaw in the web interface. The vulnerability affects multiple router models (R6400v2, R7000P, R6900P, R7900, R8300, R8500, D8500) running firmware versions prior to the patched releases.
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.2.32< 1.0.0.56< 1.0.0.56< 1.0.1.18< 1.0.2.100_1.0.82< 1.0.2.100_1.0.82< 1.0.3.29CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 modelAccess the router web interface or check the device label to confirm the exact model (R6400v2, R7000P, R6900P, R7900, R8300, R8500, or D8500)Affected if The router model matches one of the affected models listed in the CVE
-
Check installed firmware versionLog into the router web interface and navigate to the Firmware Update or Administration page to view the current firmware version, or use the router's status pageAffected if The firmware version is lower than: R6400 < 1.0.2.32, R7000P/R6900P < 1.0.0.56, R7900 < 1.0.1.18, R8300/R8500 < 1.0.2.100_1.0.82, or D8500 < 1.0.3.29
-
Verify web interface accessibilityConfirm the router's web management interface is reachable on the local network or remotely (typically on port 80 or 443)Affected if The web interface is accessible and authentication can be attempted
-
Confirm authentication is possibleAttempt to log into the router web interface using the admin credentials (default credentials are often admin/password)Affected if Valid authentication credentials can be obtained or default credentials are still in use, which would allow exploitation of the path traversal flaw
The router is affected if it is one of the listed models running a firmware version below the specified threshold and its web interface with valid credentials is accessible to an attacker.
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.561.0.1.181.0.2.32
Apply the appropriate firmware update for each affected router model: R6400v2 to 1.0.2.32+, R7000P/R6900P to 1.0.0.56+, R7900 to 1.0.1.18+, R8300/R8500 to 1.0.2.100_1.0.82+, and D8500 to 1.0.3.29+. If devices cannot be updated, consider network segmentation or replacement.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18847 — 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-18847 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