CVE-2018-21152
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 command injection by an authenticated user. This affects D7800 before 1.0.1.34, R7500v2 before 1.0.3.26, R7800 before 1.0.2.42, R8900 before 1.0.3.10, R9000 before 1.0.3.10, WNDR4300v2 before 1.0.0.54, and WNDR4500v3 before 1.0.0.54.
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 · moderate confidenceAuthenticated command injection vulnerability in NETGEAR router web management interface allows remote code execution on the underlying operating system by injecting shell commands through HTTP requests. The attacker needs valid admin credentials to exploit this issue, which affects multiple router models running firmware 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.1.34< 1.0.3.26< 1.0.2.42< 1.0.3.10< 1.0.3.10< 1.0.0.54< 1.0.0.54CVSS 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 the web management interface status page for the exact model designationAffected if Model is D7800, R7500, R7800, R8900, R9000, Wndr4300, or Wndr4500
-
Check installed firmware versionLog into the web management interface and navigate to Administration > Firmware Update or Router Status page to view the current firmware version numberAffected if Firmware version is below 1.0.1.34 for D7800, below 1.0.3.26 for R7500, below 1.0.2.42 for R7800, below 1.0.3.10 for R8900/R9000, or below 1.0.0.54 for Wndr4300/Wndr4500
-
Verify remote web management accessCheck the router web interface under Advanced > Administration > Remote Management to see if remote access is enabledAffected if Remote web management is enabled and the admin interface is accessible from untrusted networks
-
Confirm admin credential statusDetermine whether default admin credentials are still in use or if strong unique credentials have been configuredAffected if Default NETGEAR admin credentials remain unchanged or weak credentials are in use
The device is affected if it matches one of the listed models and runs a firmware version lower than the specified patched version, combined with accessible admin 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.0.541.0.1.341.0.2.42
Update affected NETGEAR devices to the specified firmware versions (D7800 1.0.1.34, R7500v2 1.0.3.26, R7800 1.0.2.42, R8900/R9000 1.0.3.10, WNDR4300v2/WNDR4500v3 1.0.0.54). If updates are not possible, restrict administrative interface access to trusted networks or VPN.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21152 — 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-21152 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