# CVE-2017-18764: Command injection in n/a > Unauthenticated attackers can execute arbitrary commands on various NETGEAR routers via command injection vulnerabilities. - **Severity:** High 8.8 (`CVSS:3.0/AC:L/AV:A/A:H/C:H/I:H/PR:N/S:U/UI:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 22 Apr 2020 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-qqhw-hqj9-7pv5 ## What is CVE-2017-18764? CVE-2017-18764 is a high-severity command injection vulnerability in Netgear D6100 Firmware, published on 22 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Certain NETGEAR devices are affected by command injection by an unauthenticated attacker. This affects D6100 before 1.0.0.55, D7000 before 1.0.1.50, D7800 before 1.0.1.28, JNR1010v2 before 1.1.0.44, JR6150 before 1.0.1.10, JWNR2010v5 before 1.1.0.44, PR2000 before 1.0.0.18, R6050 before 1.0.1.10, R6100 before 1.0.1.14, R6120 before 1.0.0.30, R6220 before 1.1.0.50, R6700v2 before 1.2.0.4, R6800 before 1.2.0.4, R6900v2 before 1.2.0.4, R7500 before 1.0.0.110, R7500v2 before 1.0.3.20, R7800 before 1.0.2.36, R9000 before 1.0.2.52, WN3000RPv3 before 1.0.2.50, WNDR3700v4 before 1.0.2.88, WNDR3700v5 before 1.1.0.48, WNDR4300v1 before 1.0.2.90, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, WNR1000v4 before 1.1.0.44, WNR2000v5 before 1.0.0.58, WNR2020 before 1.1.0.44, and WNR2050 before 1.1.0.44. Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) ## Which versions are affected by CVE-2017-18764? It affects 25 products. Products: Netgear D6100 Firmware, Netgear D7000 Firmware, Netgear D7800 Firmware, Netgear Jnr1010 Firmware, Netgear Jr6150 Firmware, Netgear Jwnr2010 Firmware, Netgear Pr2000 Firmware, Netgear R6050 Firmware, Netgear R6100 Firmware, Netgear R6120 Firmware, Netgear R6220 Firmware, Netgear R6700 Firmware, Netgear R6800 Firmware, Netgear R6900 Firmware, Netgear R7500 Firmware, Netgear R7800 Firmware, Netgear R9000 Firmware, Netgear Wn3000rp Firmware, Netgear Wndr3700 Firmware, Netgear Wndr4300 Firmware and 5 more. ## How do I fix CVE-2017-18764? No fix has been published for CVE-2017-18764 yet. Limit exposure of the affected software until one is available. ## Is CVE-2017-18764 being exploited? There is no known exploitation of CVE-2017-18764 in the wild and no public exploit code. ## Other vulnerabilities in Netgear D6100 Firmware - [CVE-2016-10174](https://insights.sbomify.com/CVE-2016-10174/): NETGEAR WNR2000v5 Router Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2018-21208](https://insights.sbomify.com/CVE-2018-21208/): Command injection in n/a (high 8.8) - [CVE-2018-21113](https://insights.sbomify.com/CVE-2018-21113/): Command injection in n/a (high 8.8) - [CVE-2017-18776](https://insights.sbomify.com/CVE-2017-18776/): Auth bypass in n/a (high 8.4) - [CVE-2017-18792](https://insights.sbomify.com/CVE-2017-18792/): Command injection in n/a (high 8.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-18764 and fix it if it is affected. What it is: CVE-2017-18764 is a high-severity command injection vulnerability in Netgear D6100 Firmware, published on 22 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2017-18764 in the wild and no public exploit code. Affected product: Netgear D6100 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-18764/ (Markdown: https://insights.sbomify.com/CVE-2017-18764/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-18764 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-18764 - OSV: https://osv.dev/vulnerability/CVE-2017-18764 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-18764/ Summaries are generated and may contain mistakes; the official description above is the record.