CVE-2018-21182
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 R7800 before 1.0.2.40, R9000 before 1.0.2.52, WNDR3700v4 before 1.0.2.92, and WNDR4300 before 1.0.2.94.
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 (R7800, R9000, WNDR3700v4, WNDR4300) allows authenticated users to overflow a stack buffer, potentially leading to 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.2.52< 1.0.2.92< 1.0.2.94CVSS 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 router modelLocate the model number on the device label or check via the router's web admin interface (usually at 192.168.1.1) under the Administration or Advanced settings sectionAffected if Model is R7800, R9000, WNDR3700v4, or WNDR4300
-
Find installed firmware versionIn the router web admin interface, go to Administration > Firmware Update or Advanced > Administration > Router Status to view the current firmware version. The version may also be displayed on the main status pageAffected if Firmware version cannot be determined or is visible
-
Compare version to affected rangesCompare your installed firmware version against: R7800 < 1.0.2.40, R9000 < 1.0.2.52, WNDR3700 < 1.0.2.92, WNDR4300 < 1.0.2.94Affected if Installed version falls below the corresponding threshold for your model
-
Confirm admin access is enabledVerify the router web management interface is accessible (default at 192.168.1.1) and check if remote management is enabled under Advanced > Administration > Remote ManagementAffected if Web admin interface is accessible with credentials (authenticated access is required to trigger the overflow)
You are affected if your router model is R7800, R9000, WNDR3700v4, or WNDR4300 AND your current firmware version is below 1.0.2.40, 1.0.2.52, 1.0.2.92, or 1.0.2.94 respectively AND the router admin interface is accessible with valid credentials.
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.2.401.0.2.521.0.2.92
Update firmware to the patched versions (R7800: 1.0.2.40+, R9000: 1.0.2.52+, WNDR3700v4: 1.0.2.92+, WNDR4300: 1.0.2.94+); if devices are no longer supported, replace them.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21182 — 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-21182 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