CVE-2017-18741
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 incorrect configuration of security settings. This affects R6250 before 1.0.4.8, R6300v2 before 1.0.4.8, R6700 before 1.0.1.20, R7000 before 1.0.7.10, R7000P before 1.0.0.58, R6900P before 1.0.0.58, R7100LG before 1.0.0.32, R7900 before 1.0.1.14, R8000 before 1.0.3.22, 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 · moderate confidenceMultiple NETGEAR router models (R6250, R6300v2, R6700, R7000, R7000P, R6900P, R7100LG, R7900, R8000, R8500) are affected by an incorrect configuration of security settings in their firmware. The specific security settings misconfigured are not detailed in the CVE description. The vulnerability is fixed in specific firmware 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.4.8< 1.0.4.8< 1.0.1.20< 1.0.7.10< 1.0.0.58< 1.0.0.58< 1.0.0.32< 1.0.1.14CVSS 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 modelLocate the model number on the device label or check via the router web interface under Administration or System settingsAffected if Model is one of: R6250, R6300v2, R6700, R7000, R7000P, R6900P, R7100LG, R7900, R8000, or R8500
-
Check current firmware versionLog into the router web interface and navigate to Administration or Router Status to view the installed firmware version. Alternatively, check the device label or use the NETGEAR mobile appAffected if Firmware version cannot be determined or is below the threshold for the identified model
-
Compare firmware version against affected thresholdsDocument the exact firmware version and compare against: R6250/R6300 < 1.0.4.8, R6700 < 1.0.1.20, R7000 < 1.0.7.10, R7000P/R6900P < 1.0.0.58, R7100LG < 1.0.0.32, R7900 < 1.0.1.14Affected if Installed firmware version is lower than the specified threshold for that model (exact version numbers vary by model)
-
Verify security settings configurationSince the specific misconfigured settings are not detailed in the CVE, review general security settings in the router web interface including firewall rules, remote management access, and WPS/UPnP settings. Document any non-default security configurationsAffected if Unable to verify specific security settings due to limited CVE details; general security review recommended
The environment is affected if the router model matches one of the listed models AND the installed firmware version is below the version threshold specified 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.321.0.0.581.0.1.14
Apply the corresponding firmware update for each affected device model to address the security misconfiguration. If updates are unavailable, consider network segmentation or replacement of affected devices.
- 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-18741 — 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-18741 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