CVE-2017-18767
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, D8500 before 1.0.3.39, R6400 before 1.0.1.14, R6400v2 before 1.0.2.32, R6700 before 1.0.1.22, R6900 before 1.0.1.22, R7000 before 1.0.9.4, R7100LG before 1.0.0.32, R7300 before 1.0.0.56, R7800 before 1.0.2.36, R7900 before 1.0.2.10, R8000 before 1.0.3.24, R8300 before 1.0.2.74, and R8500 before 1.0.2.74.
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 users to execute arbitrary operating system commands through improperly sanitized input parameters. The vulnerability affects multiple router models (D7800, D8500, R6400, R6700, R7000, R7800, and others) via the web management interface.
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.39< 1.0.1.14< 1.0.2.32< 1.0.1.22< 1.0.1.22< 1.0.9.4< 1.0.0.32< 1.0.0.56CVSS 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 footer for the model nameAffected if Model is D7800, D8500, R6400, R6700, R6900, R7000, R7100lg, R7300, or R7800 (or other affected models from advisory)
-
Check firmware versionAccess the router web management interface and navigate to the Administration or Firmware Update page to view the current firmware versionAffected if Firmware version is below the patched version for your model (D7800 < 1.0.1.34, D8500 < 1.0.3.39, R6400 < 1.0.2.32, R6700 < 1.0.1.22, R6900 < 1.0.1.22, R7000 < 1.0.9.4, R7100lg < 1.0.0.32, R7300 < 1.0.0.56)
-
Verify web interface is accessibleConfirm you can reach the router login page at the default gateway IP address (typically 192.168.1.1) via HTTP or HTTPSAffected if Web management interface is accessible on the network
-
Confirm authentication capabilityAttempt to log in to the web interface with valid admin credentialsAffected if You can authenticate to the router admin panel
You are affected if your router model matches one of the affected models AND your current firmware version is below the patched version listed for that model, and the web management interface is accessible.
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.321.0.0.561.0.1.14
Apply the latest NETGEAR firmware updates for affected devices: D7800 to 1.0.1.34, R7000 to 1.0.9.4, R7800 to 1.0.2.36, and other models to their respective patched versions as listed in the advisory.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18767 — 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-18767 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