CVE-2018-21199
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 D7800 before 1.0.1.30, R6100 before 1.0.1.22, R7500 before 1.0.0.122, R7500v2 before 1.0.3.24, R7800 before 1.0.2.40, R9000 before 1.0.2.52, and WNDR4300 before 1.0.2.98.
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 web interface allows authenticated users to execute arbitrary code via specially crafted HTTP requests. The vulnerability affects multiple router models (D7800, R6100, R7500, R7500v2, R7800, R9000, WNDR4300) in versions prior to specific firmware 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.1.30< 1.0.1.22< 1.0.3.24< 1.0.0.122< 1.0.2.40< 1.0.2.52< 1.0.2.98CVSS 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 your NETGEAR router modelLocate the model number on the device label or check the router web interface (typically at 192.168.1.1) for the model name displayed in the header or status pageAffected if The model is one of: D7800, R6100, R7500, R7500v2, R7800, R9000, or WNDR4300
-
Check installed firmware versionAccess the router web interface, navigate to the Administration or Advanced settings section, and locate the firmware version displayed on the status or router information pageAffected if A firmware version is displayed that can be compared against the affected ranges
-
Compare firmware version to affected thresholdsCompare your installed version number to the following thresholds: D7800 < 1.0.1.30, R6100 < 1.0.1.22, R7500 < 1.0.3.24 (or < 1.0.0.122 for older revisions), R7800 < 1.0.2.40, R9000 < 1.0.2.52, WNDR4300 < 1.0.2.98Affected if Your firmware version is lower than the threshold listed for your specific model
-
Confirm web interface is accessibleVerify the router web interface is reachable on the local network and that authentication is enabledAffected if The web interface is exposed and accepts authentication credentials (required for the exploit to be usable)
You are affected if you own one of the affected models (D7800, R6100, R7500, R7500v2, R7800, R9000, or WNDR4300) and your installed firmware version is below the threshold specified for that model.
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.1221.0.1.221.0.1.30
Update affected NETGEAR devices to the latest firmware versions: D7800 (1.0.1.30), R6100 (1.0.1.22), R7500 (1.0.0.122), R7500v2 (1.0.3.24), R7800 (1.0.2.40), R9000 (1.0.2.52), WNDR4300 (1.0.2.98).
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21199 — 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-21199 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