CVE-2017-18712
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 D7800 before 1.0.1.28, R6100 before 1.0.1.20, R7500 before 1.0.0.118, R7500v2 before 1.0.3.20, R7800 before 1.0.2.40, R9000 before 1.0.2.52, WNDR4300v2 before 1.0.0.48, and WNDR4500v3 before 1.0.0.48.
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 confidenceArbitrary file read vulnerability in NETGEAR router web management interface allows unauthenticated remote attackers to access any file on the device filesystem. The flaw exists in how the HTTP server handles certain requests, enabling path traversal or improper access controls.
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.40< 1.0.2.52< 1.0.0.118< 1.0.3.20< 1.0.0.48< 1.0.0.48< 1.0.1.20< 1.0.1.28CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:A/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 modelCheck the device label or web interface for the exact model number (R7800, R9000, R7500, Wndr4300, Wndr4500, R6100, or D7800)Affected if The model is one of the affected models listed in the CVE
-
Check firmware versionAccess the router web management interface (typically at 192.168.1.1) and look for the firmware version in the administration or status section, or check via telnet/SSH if enabledAffected if The installed firmware version is below 1.0.2.40 for R7800, below 1.0.2.52 for R9000, below 1.0.0.118 or 1.0.3.20 for R7500, below 1.0.0.48 for Wndr4300/Wndr4500, below 1.0.1.20 for R6100, or below 1.0.1.28 for D7800
-
Verify web management interface is accessibleAttempt to access the router web interface from the network (http://router-ip or https://router-ip)Affected if The HTTP/HTTPS management interface responds and is accessible
-
Check if remote management is enabledIn the router web interface, navigate to Administration > Remote Management or similar section, and check if remote access via WAN is enabledAffected if Remote management over WAN is enabled, allowing unauthenticated attackers from the internet to reach the vulnerable HTTP server
The device is affected if it is one of the listed models AND the firmware version is below the fixed version AND the web management interface is accessible, with remote management enabled posing the highest risk for unauthenticated remote exploitation.
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.481.0.0.1181.0.1.20
Apply vendor firmware updates for affected models. If updates are unavailable, restrict access to the router's web management interface to trusted networks only using firewall rules or disable remote management.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18712 — 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-18712 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