CVE-2018-21185
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, D7800 before 1.0.1.34, R7500 before 1.0.0.122, R7500v2 before 1.0.3.24, R7800 before 1.0.2.40, R9000 before 1.0.2.52, 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 in NETGEAR router firmware allows authenticated users to execute arbitrary code by overflowing a stack-allocated buffer. The vulnerability exists in the web management interface and can be triggered via crafted HTTP requests after authentication.
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.34< 1.0.0.122< 1.0.3.24< 1.0.2.40< 1.0.2.52< 1.0.2.92< 1.0.2.94< 1.0.0.50< 1.0.0.50CVSS 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 NETGEAR router modelAccess the router's web management interface or check the device label to confirm the exact model number (e.g., D6100, D7800, R7500, R7800, R9000, Wndr3700, Wndr4300, or Wndr4500)Affected if The model is any of the following: D6100, D7800, R7500, R7800, R9000, Wndr3700, Wndr4300, or Wndr4500
-
Check the installed firmware versionLog into the web management interface and navigate to the Firmware Update or Administration section to view the current firmware version, or use the router's command line if availableAffected if The firmware version is below the fixed threshold for your model: D6100 < 1.0.0.57, D7800 < 1.0.1.34, R7500 < 1.0.0.122 or < 1.0.3.24 (depending on hardware version), R7800 < 1.0.2.40, R9000 < 1.0.2.52, Wndr3700 < 1.0.2.92, Wndr4300 < 1.0.2.94 or < 1.0.0.50 (depending on hardware version), Wndr4500
-
Verify the web management interface is enabledConfirm that the router's HTTP/HTTPS web management interface is accessible from the networkAffected if The web interface is accessible and the router is running an affected firmware version listed in step 2
The device is affected if it is a NETGEAR model from the affected list and its firmware version is below the fixed version 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.501.0.0.571.0.0.122
Apply vendor-supplied firmware updates to reach the fixed versions for each affected model (D6100 1.0.0.57, D7800 1.0.1.34, R7500 1.0.0.122, R7500v2 1.0.3.24, R7800 1.0.2.40, R9000 1.0.2.52, WNDR3700v4 1.0.2.92, WNDR4300 1.0.2.94, WNDR4300v2 1.0.0.50, WNDR4500v3 1.0.0.50, WNR2000v5 1.0.0.62).
- 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-21185 — 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-21185 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