CVE-2017-18796
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. This affects R6400 before 1.0.1.24, R6700 before 1.0.1.26, R6900 before 1.0.1.28, R7000 before 1.0.9.10, R7000P before 1.0.1.16, R6900P before 1.0.1.16, and R7800 before 1.0.2.36.
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 firmware allows authenticated attackers to execute arbitrary commands on affected devices. The vulnerability affects multiple router models (R6400, R6700, R6900, R7000, R7000P, R6900P, R7800) running firmware versions prior to the specified fixed 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.24< 1.0.1.26< 1.0.1.28< 1.0.9.10< 1.0.1.16< 1.0.1.16< 1.0.2.36CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 interface (typically displayed on the status/dashboard page)Affected if Model is R6400, R6700, R6900, R7000, R7000P, R6900P, or R7800
-
Check firmware versionAccess the router web admin interface and navigate to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware versionAffected if Version cannot be determined or is visible
-
Compare version to affected rangesMatch your model to the corresponding threshold: R6400 < 1.0.1.24, R6700 < 1.0.1.26, R6900 < 1.0.1.28, R7000 < 1.0.9.10, R7000P < 1.0.1.16, R6900P < 1.0.1.16, R7800 < 1.0.2.36Affected if Installed firmware version is lower than the threshold for your specific model
If your router model is one of the affected models AND the running firmware version is below the specified threshold for that model, your device is vulnerable to command injection.
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.1.161.0.1.241.0.1.26
Update affected NETGEAR router firmware to the versions specified in the advisory (R6400: 1.0.1.24, R6700: 1.0.1.26, R6900: 1.0.1.28, R7000: 1.0.9.10, R7000P: 1.0.1.16, R6900P: 1.0.1.16, R7800: 1.0.2.36). For end-of-life devices that cannot be updated, consider replacement.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18796 — 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-2017-18796 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