CVE-2017-18773
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 D6100 before V1.0.0.55, D7800 before V1.0.1.24, EX6150v2 before 1.0.0.48, R6100 before 1.0.1.14, R7500 before 1.0.0.110, R7500v2 before V1.0.3.16, R7800 before V1.0.2.36, WNDR4300v1 before 1.0.2.90, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, and WNR2000v5 before 1.0.0.48.
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 confidenceAuthenticated command injection vulnerability in multiple NETGEAR router models (D6100, D7800, EX6150v2, R6100, R7500, R7500v2, R7800, WNDR4300v1, WNDR4300v2, WNDR4500v3, WNR2000v5). An authenticated attacker can execute arbitrary commands on the affected devices 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.0.55< 1.0.1.24< 1.0.0.48< 1.0.1.14< 1.0.0.110< 1.0.3.16< 1.0.2.36< 1.0.2.90< 1.0.0.48< 1.0.0.48CVSS 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 your NETGEAR router modelCheck the device label or log into the web management interface (typically http://192.168.1.1) and look for the model number in the router status or administration pageAffected if The model is D6100, D7800, EX6150v2, R6100, R7500, R7500v2, R7800, WNDR4300v1, WNDR4300v2, WNDR4500v3, or WNR2000v5
-
Check the installed firmware versionIn the router web interface, navigate to Administration > Router Update or Advanced > Administration > Firmware Upgrade to view the current firmware version. Alternatively, check the firmware file name if you have access to the router filesystem.Affected if The firmware version is lower than the affected ranges: D6100 < 1.0.0.55, D7800 < 1.0.1.24, Ex6150 < 1.0.0.48, R6100 < 1.0.1.14, R7500 < 1.0.0.110 or < 1.0.3.16, R7800 < 1.0.2.36, Wndr4300 < 1.0.2.90 or < 1.0.0.48, Wndr4500 < 1.0.0.48
-
Determine if web management interface is accessibleAttempt to access the router web interface from the network. Check if port 80 or 443 is open on the router's IP address using a port scanner or by attempting a connection.Affected if The web management interface is reachable from an untrusted network (not just the local LAN)
-
Verify authentication status on the management interfaceCheck if the router requires login credentials to access the web interface. Determine if default credentials are still in use or if custom credentials have been configured.Affected if The web interface is accessible and accepts authentication credentials (any valid credentials would suffice for the attacker to exploit this vulnerability)
Your device is affected if it is one of the listed models AND the firmware version is below the patched versions AND the web management interface is accessible with valid credentials.
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.481.0.0.551.0.0.110
Update affected NETGEAR devices to the patched firmware versions specified in the advisory. If updates are unavailable, restrict access to the device management interface to trusted networks or IP addresses.
- 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-2017-18773 — 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-18773 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