CVE-2018-21170
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 stack-based buffer overflow by an unauthenticated attacker. This affects EX2700 before 1.0.1.28, R7800 before 1.0.2.40, WN2000RPTv3 before 1.0.1.20, WN3000RPv3 before 1.0.2.50, and WN3100RPv2 before 1.0.0.56.
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 confidenceStack-based buffer overflow in NETGEAR router firmware (EX2700, R7800, WN2000RPTv3, WN3000RPv3, WN3100RPv2) allows unauthenticated remote attackers to overflow a stack buffer via crafted network requests, potentially enabling arbitrary code execution.
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.40< 1.0.1.28< 1.0.1.20< 1.0.2.50< 1.0.0.56CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 the NETGEAR device modelLocate the model number on the device label or log into the router web interface (typically 192.168.1.1) and check the status or administration page for the exact model designation (R7800, EX2700, WN2000RPTv3, WN3000RPv3, or WN3100RPv2)Affected if The device is one of these five models: R7800, EX2700, WN2000RPT, WN3000RP, or WN3100RP
-
Check the installed firmware versionIn the router web interface, navigate to the Firmware Update or Administration section and locate the current firmware version number displayed (format typically shows as x.x.x.x)Affected if The firmware version cannot be determined or is not displayed
-
Compare R7800 firmware version to the affected rangeIf the device is an R7800, check if the firmware version is lower than 1.0.2.40Affected if Firmware version is < 1.0.2.40 on an R7800
-
Compare EX2700 firmware version to the affected rangeIf the device is an EX2700, check if the firmware version is lower than 1.0.1.28Affected if Firmware version is < 1.0.1.28 on an EX2700
-
Compare WN2000RPT firmware version to the affected rangeIf the device is a WN2000RPT, check if the firmware version is lower than 1.0.1.20Affected if Firmware version is < 1.0.1.20 on a WN2000RPT
-
Compare WN3000RP firmware version to the affected rangeIf the device is a WN3000RP, check if the firmware version is lower than 1.0.2.50Affected if Firmware version is < 1.0.2.50 on a WN3000RP
The device is affected if it is one of the five models (R7800, EX2700, WN2000RPT, WN3000RP, or WN3100RP) and its firmware version falls below the corresponding threshold (1.0.2.40, 1.0.1.28, 1.0.1.20, 1.0.2.50, or 1.0.0.56 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.561.0.1.201.0.1.28
Apply vendor-supplied firmware updates: EX2700 to 1.0.1.28+, R7800 to 1.0.2.40+, WN2000RPTv3 to 1.0.1.20+, WN3000RPv3 to 1.0.2.50+, WN3100RPv2 to 1.0.0.56+. If patching is not feasible, restrict network access to these devices.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21170 — 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-2018-21170 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