CVE-2017-18733
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 D6220 before 1.0.0.28, D6400 before 1.0.0.60, D8500 before 1.0.3.29, R6250 before 1.0.4.8, R6400 before 1.0.1.22, R6400v2 before 1.0.2.32, R7100LG before 1.0.0.32, R7300DST before 1.0.0.52, R8300 before 1.0.2.94, 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 · moderate confidenceAuthentication bypass vulnerability in multiple NETGEAR router models (D6220, D6400, D8500, R6250, R6400, R6400v2, R7100LG, R7300DST, R8300, R8500) allows remote attackers to bypass authentication mechanisms. The vulnerability affects firmware versions prior to the specified patched versions for each model.
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.28< 1.0.0.60< 1.0.3.29< 1.0.4.8< 1.0.1.22< 1.0.2.32< 1.0.0.32< 1.0.0.52< 1.0.2.94CVSS 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 your NETGEAR router modelLocate the model number on the router device label or log into the router admin interface and check the status or maintenance page for the exact model numberAffected if The model is D6220, D6400, D8500, R6250, R6400, R6400v2, R7100LG, R7300DST, R8300, or R8500
-
Find the installed firmware versionLog into the router admin web interface (typically at 192.168.1.1) and navigate to Router Status, Maintenance, or Advanced settings to locate the Firmware Version fieldAffected if The displayed firmware version is below the patched version for your specific model
-
Compare your version against affected rangesMatch your model and firmware version to the affected list: D6220 < 1.0.0.28, D6400 < 1.0.0.60, D8500 < 1.0.3.29, R6250 < 1.0.4.8, R6400 < 1.0.1.22 (or < 1.0.2.32 for R6400v2), R7100LG < 1.0.0.32, R7300DST < 1.0.0.52, R8300 < 1.0.2.94, R8500 < 1.0.2.100Affected if Your firmware version falls below the patched version for your model in the list
-
Check if remote administration is enabledIn the router admin interface, go to Advanced > Remote Management or similar settings and verify if remote access via WAN is enabledAffected if Remote management is enabled and your firmware version is below the patched version - this exposes the authentication bypass vulnerability to attackers on the internet
You are affected if your NETGEAR router model matches one of the listed models and your installed firmware version is below the patched version for that model, especially if remote administration is enabled.
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.281.0.0.321.0.0.52
Update affected NETGEAR router firmware to the patched versions (D6220: 1.0.0.28, D6400: 1.0.0.60, D8500: 1.0.3.29, R6250: 1.0.4.8, R6400: 1.0.1.22, R6400v2: 1.0.2.32, R7100LG: 1.0.0.32, R7300DST: 1.0.0.52, R8300: 1.0.2.94, R8500: 1.0.2.100). If updating is not possible, restrict WAN access to administrative interfaces and monitor for unauthorized access.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18733 — 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-18733 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