CVE-2018-21228
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, EX6100v2 before 1.0.1.50, EX6150v2 before 1.0.1.50, EX6200v2 before 1.0.1.44, EX6400 before 1.0.1.60, EX7300 before 1.0.1.60, R6100 before 1.0.1.16, R7500 before 1.0.0.110, R7800 before 1.0.2.32, R9000 before 1.0.2.30, WN3000RPv3 before 1.0.2.50, WNDR4300v2 before 1.0.0.50, and WNDR4500v3 before 1.0.0.50.
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 confidenceCommand injection vulnerability in NETGEAR router and range extender firmware allows authenticated users to execute arbitrary operating system commands. Multiple models (D7800, EX6100v2, EX6150v2, EX6200v2, EX6400, EX7300, R6100, R7500, R7800, R9000, WN3000RPv3, WNDR4300v2, WNDR4500v3) are affected when running firmware versions before vendor-specified thresholds.
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.1.50< 1.0.1.50< 1.0.1.44< 1.0.1.60< 1.0.1.60< 1.0.1.16< 1.0.0.110CVSS 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 device modelLog into the router web interface and navigate to the Administration or Settings section to find the model number, or check the product label on the device itselfAffected if The model is one of: D7800, EX6100v2, EX6150v2, EX6200v2, EX6400, EX7300, R6100, R7500, R7800, R9000, WN3000RPv3, WNDR4300v2, or WNDR4500v3
-
Locate the firmware versionIn the router admin web interface, look for a Firmware Version or Router Status page typically found under Administration, Settings, or Help sectionsAffected if You cannot locate the firmware version or the device model is not immediately identifiable
-
Compare your firmware version against affected thresholdsMatch your installed firmware version to the following thresholds: D7800 < 1.0.1.34, EX6100 < 1.0.1.50, EX6150 < 1.0.1.50, EX6200 < 1.0.1.44, EX6400 < 1.0.1.60, EX7300 < 1.0.1.60, R6100 < 1.0.1.16, R7500 < 1.0.0.110Affected if Your firmware version is lower than the threshold listed for your specific model
-
Confirm administrative access is possibleVerify that the router web management interface is accessible, either locally or remotely, as this vulnerability requires authenticated access to the admin panelAffected if The admin interface is exposed and you have valid credentials for the device
-
Check for unauthorized access indicatorsReview router logs for unexpected commands, new user accounts, or configuration changes you did not make; look for unknown processes or network connectionsAffected if Any suspicious activity or unrecognized changes are present in logs or device configuration
You are affected if you own one of the listed NETGEAR models and your device is running firmware version lower than the specified threshold for that model, with the admin interface accessible to potential attackers.
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.1101.0.1.161.0.1.34
Update all affected NETGEAR devices to the latest firmware versions provided by the vendor. Until patches are applied, limit administrative interface access to trusted users only and monitor for indicators of compromise.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21228 — 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-21228 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