CVE-2017-18797
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 R6400 before 1.0.1.24, R7900 before 1.0.1.18, R8000 before 1.0.3.54, and R8500 before 1.0.2.100.
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 confidenceNETGEAR R6400, R7900, R8000, and R8500 routers contain a file disclosure vulnerability allowing unauthenticated attackers to read arbitrary files on the device. This is likely a path traversal or local file inclusion issue in the web interface. The vulnerability affects specific firmware versions prior to R6400v1.0.1.24, R7900v1.0.1.18, R8000v1.0.3.54, and R8500v1.0.2.100.
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.1.24< 1.0.1.18< 1.0.3.54< 1.0.2.100CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/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 modelLocate the model number on the device label or log into the web admin interface and check the status or router info pageAffected if The model is R6400, R7900, R8000, or R8500
-
Check firmware versionIn the router web admin interface, navigate to Advanced > Administration > Router Update or check the status/dashboard page for the firmware version stringAffected if Unable to retrieve firmware version or version is not displayed
-
Compare firmware to affected versionsMatch your firmware version against these thresholds: R6400 < 1.0.1.24, R7900 < 1.0.1.18, R8000 < 1.0.3.54, R8500 < 1.0.2.100Affected if Your installed version falls below the corresponding threshold for your model
-
Verify web interface is accessibleAttempt to access the router login page over HTTP/HTTPS from the network segment you are checkingAffected if The web management interface is reachable (this is the vulnerable component)
If your router model is R6400, R7900, R8000, or R8500 and the firmware version is below the patched threshold for that model, and the web interface is accessible, then your environment is affected by this 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.181.0.1.241.0.2.100
Apply the vendor-supplied firmware update to a patched version as listed in the advisory. If patching is not possible, restrict network access to the router's management interface.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18797 — 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-18797 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