CVE-2018-21192
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 D6100 before 1.0.0.57, R6100 before 1.0.1.20, R7800 before 1.0.2.40, R9000 before 1.0.3.6, WNDR3700v4 before 1.0.2.92, WNDR4300 before 1.0.2.94, WNDR4300v2 before 1.0.0.50, WNDR4500v3 before 1.0.0.50, and WNR2000v5 before 1.0.0.62.
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 vulnerability in NETGEAR router firmware allows authenticated users to execute arbitrary code via specially crafted input. Multiple router models (D6100, R6100, R7800, R9000, WNDR3700v4, WNDR4300, WNDR4300v2, WNDR4500v3, WNR2000v5) are affected in versions prior to the patched releases.
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.57< 1.0.1.20< 1.0.2.40< 1.0.3.6< 1.0.2.92< 1.0.2.94< 1.0.0.50< 1.0.0.50< 1.0.0.62CVSS 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 the router modelLocate the model number on the router device label or check the admin web interface (typically at 192.168.1.1) under the Status or Device Information pageAffected if The model is one of: D6100, R6100, R7800, R9000, WNDR3700v4, WNDR4300, WNDR4300v2, WNDR4500v3, or WNR2000v5
-
Find the current firmware versionIn the router admin web interface, navigate to Administration > Firmware Upgrade or Advanced > Administration > Router Status to view the installed firmware version. The version may also be displayed on the main Status pageAffected if The firmware version cannot be determined or is not visible
-
Compare installed version against affected rangesMatch your firmware version to the affected version list: D6100 < 1.0.0.57, R6100 < 1.0.1.20, R7800 < 1.0.2.40, R9000 < 1.0.3.6, WNDR3700 < 1.0.2.92, WNDR4300 < 1.0.2.94 (or < 1.0.0.50 for v1), WNDR4500 < 1.0.0.50, WNR2000 < 1.0.0.62Affected if Your installed version is lower than the threshold for your specific model
-
Verify if remote management or authentication is accessibleConfirm whether the router admin interface is accessible (locally or remotely) and whether you can log in with valid credentialsAffected if The router admin interface is accessible and you have valid credentials - the vulnerability is exploitable by any authenticated user
You are affected if your router model matches one of the listed models and your installed firmware version falls below the threshold for that model, especially if remote admin access or authentication is 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.501.0.0.571.0.0.62
Apply vendor-supplied firmware updates to the affected NETGEAR devices. For devices reaching end-of-life, consider replacement with supported hardware.
- 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-2018-21192 — 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-21192 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