CVE-2017-18772
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 authentication bypass. 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, R8500 before 1.0.2.74, and WNR2000v2 before 1.2.0.8.
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 confidenceAuthentication bypass vulnerability in multiple NETGEAR wireless router and range extender models allows unauthenticated attackers to gain administrative access to affected devices by exploiting a flaw in the authentication mechanism.
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
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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.
-
Identify the NETGEAR device modelLog into the router web interface (typically 192.168.1.1) and navigate to the Administration or Router Status page to locate the model number, or check the physical device labelAffected if The device model is one of: Ex3700, Ex3800, Ex6120, Ex6130, R6300, R6700, R6900, or R7000
-
Determine the current firmware versionIn the router web interface, go to Administration > Firmware Update or Router Status page and locate the firmware version number displayedAffected if The firmware version is lower than the affected threshold 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)
-
Verify if remote administration is enabledIn the router web interface, go to Advanced > Remote Management or Administration > Remote Management and check if the Enable Remote Management option is checkedAffected if Remote management is enabled and the device is exposed to network access from outside the local network
You are affected if you own one of the listed models and your firmware version is below the specified threshold for that model.
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
Update affected NETGEAR devices to the specified firmware versions (EX3700/EX3800: 1.0.0.64, EX6120: 1.0.0.32, EX6130: 1.0.0.16, R6300v2: 1.0.4.12, R6700: 1.0.1.26, R6900: 1.0.1.22, R7000: 1.0.9.6, R7300DST: 1.0.0.52, R7900: 1.0.1.12, R8000: 1.0.3.24, R8500: 1.0.2.74, WNR2000v2: 1.2.0.8) or later. If firmware updates are unavailable, disable remote administration and restrict network access.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18772 — 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-18772 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