CVE-2017-18791
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 R6050/JR6150 before 1.0.1.7, PR2000 before 1.0.0.17, R6220 before 1.1.0.50, WNDR3700v5 before 1.1.0.48, JNR1010v2 before 1.1.0.40, JWNR2010v5 before 1.1.0.40, WNR1000v4 before 1.1.0.40, WNR2020 before 1.1.0.40, WNR2050 before 1.1.0.40, WNR614 before 1.1.0.40, WNR618 before 1.1.0.40, and D7000 before 1.0.1.50.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in multiple NETGEAR router firmware versions. An attacker could exploit this to trick authenticated administrators into performing unintended configuration changes, potentially compromising router security settings.
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.7< 1.0.1.7< 1.0.0.17< 1.1.0.50< 1.1.0.48< 1.1.0.40< 1.1.0.40< 1.1.0.40CVSS 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 log into the router admin interface and check the status or system information pageAffected if The model is one of: R6050, JR6150, PR2000, R6220, WNDR3700, JNR1010, JWNR2010, or WNR1000
-
Check installed firmware versionLog into the router web interface (typically at 192.168.1.1) and navigate to the Firmware Update, Router Status, or Administration page to view the current firmware versionAffected if The displayed firmware version is below the fixed version for your model (R6050/JR6150: 1.0.1.7, PR2000: 1.0.0.17, R6220: 1.1.0.50, WNDR3700: 1.1.0.48, JNR1010/JWNR2010/WNR1000: 1.1.0.40)
-
Verify admin interface accessibilityConfirm whether the router admin web interface is accessible from the local network or exposed to the internetAffected if The router admin interface is accessible and an attacker could potentially trick a logged-in administrator into clicking a malicious link
-
Review recent configuration changesCheck router logs or configuration backup files for any unexpected or unauthorized changes to settings such as DNS servers, wireless passwords, or port forwarding rulesAffected if Configuration changes exist that were not made by an authorized administrator
Your router is affected if it matches one of the listed models AND runs a firmware version lower than 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.171.0.1.71.1.0.40
Update affected NETGEAR router firmware to the specified fixed versions (R6050/JR6150: 1.0.1.7, PR2000: 1.0.0.17, R6220: 1.1.0.50, WNDR3700v5: 1.1.0.48, others to 1.1.0.40 or 1.0.1.50 as listed). Avoid browsing untrusted links while logged into router admin interfaces.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18791 — 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-18791 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