# CVE-2021-45550: Command injection in n/a > Authenticated attackers can execute arbitrary commands on various NETGEAR routers via command injection vulnerabilities. - **Severity:** Medium 6.6 (`CVSS:3.1/AC:L/AV:A/A:H/C:H/I:H/PR:H/S:U/UI:R`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 26 Dec 2021 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-hvp9-jp8f-v4wh ## What is CVE-2021-45550? CVE-2021-45550 is a medium-severity command injection vulnerability in Netgear D3600 Firmware, published on 26 Dec 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description Certain NETGEAR devices are affected by command injection by an authenticated user. This affects D3600 before 1.0.0.76, D6000 before 1.0.0.78, D6100 before 1.0.0.63, D6220 before 1.0.0.52, D6400 before 1.0.0.86, D7800 before 1.0.1.56, D8500 before 1.0.3.44, DGN2200Bv4 before 1.0.0.109, DGN2200v4 before 1.0.0.110, R6250 before 1.0.4.34, R6300v2 before 1.0.4.34, R6400 before 1.0.1.46, R6400v2 before 1.0.2.66, R6700 before 1.0.2.6, R6700v3 before 1.0.2.66, R6900 before 1.0.2.4, R6900P before 1.3.1.64, R7000 before 1.0.9.42, R7000P before 1.3.1.64, R7100LG before 1.0.0.50, R7300 before 1.0.0.70, R7900 before 1.0.3.8, R7900P before 1.4.1.30, R8000 before 1.0.4.28, R8000P before 1.4.1.30, R8300 before 1.0.2.128, R8500 before 1.0.2.128, WNDR3400v3 before 1.0.1.24, WNR3500Lv2 before 1.2.0.62, and XR500 before 2.3.2.56. Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2021-45550? It affects 28 products. Products: Netgear D3600 Firmware, Netgear D6000 Firmware, Netgear D6100 Firmware, Netgear D6220 Firmware, Netgear D6400 Firmware, Netgear D7800 Firmware, Netgear D8500 Firmware, Netgear Dgn2200 Firmware, Netgear Dgn2200b Firmware, Netgear R6250 Firmware, Netgear R6300 Firmware, Netgear R6400 Firmware, Netgear R6700 Firmware, Netgear R6900 Firmware, Netgear R6900p Firmware, Netgear R7000 Firmware, Netgear R7000p Firmware, Netgear R7100lg Firmware, Netgear R7300 Firmware, Netgear R7900 Firmware and 8 more. ## How do I fix CVE-2021-45550? No fix has been published for CVE-2021-45550 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-45550 being exploited? There is no known exploitation of CVE-2021-45550 in the wild and no public exploit code. ## Other vulnerabilities in Netgear D3600 Firmware - [CVE-2020-35799](https://insights.sbomify.com/CVE-2020-35799/): Memory corruption in n/a (high 8.8) - [CVE-2018-21207](https://insights.sbomify.com/CVE-2018-21207/): Memory corruption in n/a (high 8.8) - [CVE-2018-21210](https://insights.sbomify.com/CVE-2018-21210/): Memory corruption in n/a (high 8.8) - [CVE-2018-21211](https://insights.sbomify.com/CVE-2018-21211/): Memory corruption in n/a (high 8.8) - [CVE-2018-21212](https://insights.sbomify.com/CVE-2018-21212/): Memory corruption in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-45550 and fix it if it is affected. What it is: CVE-2021-45550 is a medium-severity command injection vulnerability in Netgear D3600 Firmware, published on 26 Dec 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2021-45550 in the wild and no public exploit code. Affected product: Netgear D3600 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-2021-45550/ (Markdown: https://insights.sbomify.com/CVE-2021-45550/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-45550 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-45550 - OSV: https://osv.dev/vulnerability/CVE-2021-45550 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-45550/ Summaries are generated and may contain mistakes; the official description above is the record.