CVE-2018-21163
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 authenticated user. This affects DGN2200Bv4 before 1.0.0.102, DGN2200v4 before 1.0.0.102, EX3700 before 1.0.0.70, EX3800 before 1.0.0.70, EX6000 before 1.0.0.30, EX6100 before 1.0.2.22, EX6120 before 1.0.0.40, EX6130 before 1.0.0.22, EX6150 before 1.0.0.38, EX6200 before 1.0.3.86, EX7000 before 1.0.0.64, R6300v2 before 1.0.4.22, R6900P before 1.3.0.18, R7000P before 1.3.0.18, R7300DST before 1.0.0.62, R7900P before 1.3.0.10, R8000 before 1.0.4.12, R8000P before 1.3.0.10, WN2500RPv2 before 1.0.1.52, and WNDR3400v3 before 1.0.1.18.
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 confidenceA stack-based buffer overflow vulnerability exists in the web management interface of multiple NETGEAR routers, extenders, and wireless repeaters. An authenticated attacker can exploit this to execute arbitrary code or cause denial of service. The vulnerability affects 20 different device models across multiple firmware versions.
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.102< 1.0.0.102< 1.0.0.70< 1.0.0.70< 1.0.0.30< 1.0.2.22< 1.0.0.40< 1.0.0.22CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 the NETGEAR device modelLocate the model number on the device label or check the web management interface header/status page for the exact model name (e.g., Dgn2200, Ex3700, Ex6130)Affected if The device model matches one of the affected models listed in the CVE (Dgn2200, Dgn2200b, Ex3700, Ex3800, Ex6000, Ex6100, Ex6120, Ex6130)
-
Check the installed firmware versionAccess the router web interface, navigate to the Status or Administration section, and locate the Firmware Version field. Alternatively, check the device label or use the NETGEAR desktop/mobile app if available.Affected if The firmware version is lower than the threshold for your model: Dgn2200/Dgn2200b < 1.0.0.102, Ex3700/Ex3800 < 1.0.0.70, Ex6000 < 1.0.0.30, Ex6100 < 1.0.2.22, Ex6120 < 1.0.0.40, Ex6130 < 1.0.0.22
-
Verify the web management interface is enabledLog into the router and navigate to the Administration or Advanced settings. Check if the web management interface (HTTP/HTTPS) is turned on. This is typically found under 'Remote Management' or 'Web Management Access' settings.Affected if The web management interface is enabled and accessible (even locally, as authentication is required for exploitation)
-
Check remote administration exposureIn the router settings, examine the Remote Management or Access Control section. Look for settings that allow web interface access from outside the local network (WAN-side access).Affected if Remote administration is enabled and the management interface is exposed to the internet or untrusted networks
You are affected if your NETGEAR device model is listed in the CVE and your installed firmware version is below the specified threshold for that model, with the web management interface enabled.
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.221.0.0.301.0.0.40
Update affected devices to the specified firmware versions. Apply vendor patches immediately and restrict administrative access to trusted users only.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21163 — 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-21163 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