CVE-2017-18842
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 R7300 before 1.0.0.54, R8500 before 1.0.2.94, DGN2200v1 before 1.0.0.55, and D2200D/D2200DW-1FRNAS before 1.0.0.32.
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 the web management interface of multiple NETGEAR router models (R7300, R8500, DGN2200v1, D2200D/D2200DW-1FRNAS). Attackers can exploit this to perform unauthorized administrative actions by tricking authenticated users into visiting malicious pages.
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.54< 1.0.2.94< 1.0.0.55< 1.0.0.32< 1.0.0.32CVSS 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 modelCheck the product label on the router or log into the web management interface and look for the model number displayed in the admin panelAffected if The model is one of: R7300, R8500, DGN2200v1, D2200D, or D2200DW-1FRNAS
-
Locate firmware version in web interfaceLog into the router admin interface (typically at 192.168.1.1) and navigate to Administration > Firmware Update or Router Status to find the current firmware versionAffected if You can access the web management interface and retrieve the version number
-
Compare firmware version against affected rangesCompare your installed firmware version to the following vulnerable ranges: R7300 < 1.0.0.54, R8500 < 1.0.2.94, DGN2200 < 1.0.0.55, D2200D/D2200DW-1FRNAS < 1.0.0.32Affected if Your firmware version falls below the specified version for your model
-
Verify web management interface accessibilityConfirm the router web admin interface is reachable on the local network (typically HTTP port 80/443)Affected if The web management interface is exposed and reachable
-
Confirm user authentication session behaviorWhen logged into the admin panel, observe if the interface uses anti-CSRF tokens (such as unique tokens per request) in administrative formsAffected if The admin forms lack CSRF token validation and accept requests without token verification
You are affected if you own one of the listed models (R7300, R8500, DGN2200v1, D2200D, D2200DW-1FRNAS) AND your current firmware version is below the specified patched versions (1.0.0.54, 1.0.2.94, 1.0.0.55, or 1.0.0.32 respectively).
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.541.0.0.55
Update router firmware to the specified patched versions (R7300: 1.0.0.54, R8500: 1.0.2.94, DGN2200v1: 1.0.0.55, D2200D/D2200DW-1FRNAS: 1.0.0.32). If updates are unavailable, limit administrative access to trusted networks and avoid browsing untrusted sites while logged into router admin interfaces.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18842 — 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-18842 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