CVE-2018-21113
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 unauthenticated attacker. This affects D6100 before 1.0.0.58, D7800 before 1.0.1.42, R6100 before 1.0.1.28, R7500 before 1.0.0.130, R7500v2 before 1.0.3.36, R7800 before 1.0.2.52, R8900 before 1.0.4.12, R9000 before 1.0.4.12, WNDR3700v4 before 1.0.2.102, WNDR4300 before 1.0.2.104, WNDR4300v2 before 1.0.0.56, and WNDR4500v3 before 1.0.0.56.
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 confidenceUnauthenticated command injection vulnerability in multiple NETGEAR router models (D6100, D7800, R6100, R7500, R7500v2, R7800, R8900, R9000, WNDR3700v4, WNDR4300, WNDR4300v2, WNDR4500v3). An attacker can execute arbitrary commands on the affected devices without authentication, likely through insufficient input validation in a web interface parameter.
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.58< 1.0.1.42< 1.0.1.28< 1.0.0.130< 1.0.3.36< 1.0.2.52< 1.0.4.12< 1.0.4.12< 1.0.2.102CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 access the router web interface (typically at 192.168.1.1) and check the status or administration page for the model identifierAffected if Model is D6100, D7800, R6100, R7500, R7500v2, R7800, R8900, R9000, WNDR3700v4, WNDR4300, WNDR4300v2, or WNDR4500v3
-
Check firmware versionIn the router web interface, navigate to the Administration or Advanced settings section and locate the firmware version field. This is usually found under Router Status, Firmware Version, or Administration > Firmware UpdateAffected if Firmware version cannot be determined or is below the fixed version for that model
-
Compare installed version to < 1.0.0.58Affected if Version is 1.0.0.57 or lower
-
Compare installed version to < 1.0.1.42Affected if Version is 1.0.1.41 or lower
-
Compare installed version to < 1.0.1.28Affected if Version is 1.0.1.27 or lower
-
Compare installed version to < 1.0.0.130 or < 1.0.3.36 (whichever range applies)Affected if Version is 1.0.0.129 or lower, or between 1.0.1.x and 1.0.3.35
The device is affected if it is one of the listed NETGEAR models and the installed firmware version falls below the specified fixed version for that model, allowing unauthenticated command injection via the web 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.581.0.0.1301.0.1.28
Update NETGEAR router firmware to the specified version for each model (e.g., D6100 to 1.0.0.58, R7800 to 1.0.2.52, WNDR4300 to 1.0.2.104). If updates are unavailable, restrict network access to the router's management interface.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-21113 — 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-21113 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