CVE-2018-21184
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.28, R7500v2 before 1.0.3.24, R7800 before 1.0.2.40, and R9000 before 1.0.3.6.
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 confidenceThis vulnerability is a stack-based buffer overflow in multiple NETGEAR router models (D6100, D7800, R7500v2, R7800, R9000) that can be exploited by an authenticated user to execute arbitrary code or cause denial of service.
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.28< 1.0.3.24< 1.0.2.40< 1.0.3.6CVSS 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 modelCheck the device label on the router or log into the web admin interface (typically at 192.168.1.1) and look for the model number in the status or administration pageAffected if The router is one of: D6100, D7800, R7500v2, R7800, or R9000
-
Check firmware versionIn the router web admin interface, navigate to Administration > Firmware Update or Advanced > Administration > Router Status to view the current firmware versionAffected if The installed firmware version is below: 1.0.0.57 for D6100, 1.0.1.28 for D7800, 1.0.3.24 for R7500, 1.0.2.40 for R7800, or 1.0.3.6 for R9000
-
Verify authentication requirementsThis vulnerability requires an authenticated user. Check if remote management is enabled under Advanced > Administration > Remote Management, and assess whether unauthorized users could obtain valid credentialsAffected if The router administration interface is accessible to untrusted users or weak credentials are in use
-
Compare version to fixed releasesCompare your firmware version against the fixed versions: D6100 = 1.0.0.57, D7800 = 1.0.1.28, R7500 = 1.0.3.24, R7800 = 1.0.2.40, R9000 = 1.0.3.6Affected if Your firmware version is lower than the fixed version for your model
You are affected if you own a D6100, D7800, R7500v2, R7800, or R9000 NETGEAR router running firmware below the specified fixed versions and an authenticated attacker could access the admin interface.
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.571.0.1.281.0.2.40
Apply the available firmware updates: D6100 to 1.0.0.57 or later, D7800 to 1.0.1.28 or later, R7500v2 to 1.0.3.24 or later, R7800 to 1.0.2.40 or later, and R9000 to 1.0.3.6 or later.
- 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-21184 — 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-21184 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