CVE-2017-18742
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 CSRF. This affects JR6150 before 1.0.1.10, R6050 before 1.0.1.10, R6250 before 1.0.4.12, R6300v2 before 1.0.4.8, R6700 before 1.0.1.16, R6900 before 1.0.1.16, R7300DST before 1.0.0.54, R7900 before 1.0.1.12, R8000 before 1.0.3.32, and R8500 before 1.0.2.74.
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 confidenceCSRF vulnerability in NETGEAR router firmware allows remote attackers to inject malicious requests through authenticated user sessions, potentially modifying router settings or executing administrative actions without user consent.
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.1.10< 1.0.1.10< 1.0.4.12< 1.0.4.8< 1.0.1.16< 1.0.1.16< 1.0.0.54< 1.0.1.12CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 router modelLocate the model number on the router device label or check the web interface login page for the model identifierAffected if The model is one of: Jr6150, R6050, R6250, R6300, R6700, R6900, R7300dst, or R7900
-
Check installed firmware versionLog into the router web interface and navigate to the Administration or Router Status page to view the current firmware version. Alternatively, access the router via telnet and run the 'version' or 'nvram get firmwareVersion' command if available.Affected if The firmware version is lower than the fixed version for your model: Jr6150/R6050 < 1.0.1.10, R6250 < 1.0.4.12, R6300 < 1.0.4.8, R6700/R6900 < 1.0.1.16, R7300dst < 1.0.0.54, R7900 < 1.0.1.12
-
Check WAN remote management settingsIn the router web interface, go to Advanced > Administration > Remote Management and verify if remote management is enabled, which allows CSRF attacks from outside the local network.Affected if Remote management is enabled and the router is directly accessible from the internet on WAN port
You are affected if your NETGEAR router model matches one of the listed models and your current firmware version is below the specified fixed version 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.541.0.1.101.0.1.12
Update affected NETGEAR router models to the specified firmware versions: JR6150/R6050 to 1.0.1.10, R6250 to 1.0.4.12, R6300v2 to 1.0.4.8, R6700/R6900 to 1.0.1.16, R7300DST to 1.0.0.54, R7900 to 1.0.1.12, R8000 to 1.0.3.32, and R8500 to 1.0.2.74.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18742 — 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-18742 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