CVE-2018-21106
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 · uneditedNETGEAR R7800 devices before 1.0.2.60 are affected by command injection by an authenticated user.
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 confidenceNETGEAR R7800 firmware versions prior to 1.0.2.60 contain a command injection vulnerability that allows an authenticated attacker to execute arbitrary operating system commands on the device. The vulnerability exists in the web management interface and can be exploited by sending specially crafted requests.
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.60CVSS 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 device modelAccess the device's web management interface or check the device label/marketing to confirm it is a NETGEAR R7800 routerAffected if Device is not a NETGEAR R7800 model
-
Check firmware versionLog into the web management interface and navigate to the firmware version information page, typically found under Administration or Advanced settings. Compare the displayed version to 1.0.2.60Affected if Firmware version is less than 1.0.2.60
-
Confirm web management interface is enabledVerify that the web management interface is accessible by attempting to reach the router's admin page (usually http://192.168.1.1) from a connected deviceAffected if Web management interface is accessible and the device is a vulnerable R7800 model with firmware < 1.0.2.60
-
Verify administrative access existsConfirm that administrative credentials are configured or that default credentials have not been changed, as the vulnerability requires an authenticated attackerAffected if Administrative credentials are active on a vulnerable R7800 device
The device is affected if it is a NETGEAR R7800 router running firmware version prior to 1.0.2.60 with the web management interface accessible and administrative accounts configured.
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.60
Upgrade NETGEAR R7800 firmware to version 1.0.2.60 or later. If upgrading is not immediately possible, restrict administrative access to the web interface to trusted IP addresses only and change default administrative credentials.
- 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-21106 — 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-21106 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