CVE-2017-18770
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 a buffer overflow by an authenticated user. This affects R7800 before 1.0.2.36, PLW1000v2 before 1.0.0.14, and PLW1010v2 before 1.0.0.14.
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 confidenceBuffer overflow vulnerability in certain NETGEAR router firmware (R7800, PLW1000v2, PLW1010v2) allows authenticated users to overflow a buffer, potentially leading to arbitrary code execution or device compromise.
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.2.36< 1.0.0.14< 1.0.0.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/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 router modelLog into the router web interface and check the device or status page for the exact model number (R7800, PLW1000v2, or PLW1010v2).Affected if Model is NOT R7800, PLW1000v2, or PLW1010v2 (other models are not affected by this CVE).
-
Check firmware version via web interfaceNavigate to Administration > Firmware Update or a Status/Device Info page in the router web UI to view the current firmware version.Affected if Unable to access router administrative interface.
-
Compare firmware to affected versionsCompare your installed firmware version against: R7800 < 1.0.2.36, PLW1000 < 1.0.0.14, PLW1010 < 1.0.0.14.Affected if Firmware version is lower than the patched version for your specific model.
-
Verify administrative access exposureDetermine if the router admin interface is accessible from the WAN/internet or only from the LAN. Check remote management settings under Administration > Remote Management.Affected if Remote administrative access is enabled and the router has a public IP, increasing exposure to authenticated attackers.
-
Check for unauthorized configuration changesReview router configuration for unexpected port forwards, VPN settings, or user accounts that may indicate exploitation.Affected if Unexpected changes found that were not made by the administrator.
Your router is affected if it is an R7800, PLW1000v2, or PLW1010v2 model running firmware version below 1.0.2.36 or 1.0.0.14 respectively, AND you have allowed authenticated users or remote admin access.
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.141.0.2.36
Upgrade firmware to patched versions: R7800 to 1.0.2.36+, PLW1000v2/PLW1010v2 to 1.0.0.14+. Restrict administrative access to trusted users to reduce attack surface.
- 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-18770 — 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-18770 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