CVE-2017-18752
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 EX3700 before 1.0.0.64, EX3800 before 1.0.0.64, EX6120 before 1.0.0.32, EX6130 before 1.0.0.16, R6300v2 before 1.0.4.12, R6700 before 1.0.1.26, R6900 before 1.0.1.22, R7000 before 1.0.9.6, R7300DST before 1.0.0.52, R7900 before 1.0.1.12, R8000 before 1.0.3.24, and R8500 before 1.0.2.94.
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 an arbitrary file read vulnerability (likely path traversal or local file inclusion) affecting multiple NETGEAR router models. An authenticated attacker can read any file on the device's filesystem, potentially exposing sensitive configuration files, credentials, and other system data. The vulnerability affects specific firmware versions before the patches listed.
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.0.64< 1.0.0.64< 1.0.0.32< 1.0.0.16< 1.0.4.12< 1.0.1.26< 1.0.1.22< 1.0.9.6CVSS 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 the NETGEAR router modelLocate the model number on the device label or log into the router admin interface and check the status or settings page for the exact model designationAffected if The model is one of: Ex3700, Ex3800, Ex6120, Ex6130, R6300, R6700, R6900, or R7000
-
Check the installed firmware versionIn the router admin interface, navigate to the Firmware Update, Status, or About page and note the exact firmware version number displayedAffected if The firmware version is lower than the patched version for your model (Ex3700/Ex3800: < 1.0.0.64, Ex6120: < 1.0.0.32, Ex6130: < 1.0.0.16, R6300: < 1.0.4.12, R6700: < 1.0.1.26, R6900: < 1.0.1.22, R7000: < 1.0.9.6)
-
Confirm remote administrative access is enabledIn the router admin interface, check the Remote Management, Remote Access, or WAN Access settings to see if the web interface is accessible from outside the local networkAffected if Remote management is enabled and the router admin port is exposed to WAN, allowing an external authenticated attacker to reach the vulnerable endpoint
-
Verify the web server is running and accessibleAttempt to access the router login page from the network segment where the router is deployed; confirm the HTTP/HTTPS service is respondingAffected if The router web interface is reachable and accepts authentication, which is required to exploit this arbitrary file read vulnerability
You are affected if your NETGEAR router model matches one of the listed products AND your firmware version is below the specified patched version AND the router admin interface is accessible to an attacker (either locally or remotely).
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.161.0.0.321.0.0.64
Apply the available firmware updates from NETGEAR for each affected model to the specified version or later. If firmware updates are unavailable, restrict administrative interface access to trusted networks only.
- 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-18752 — 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-18752 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