# CVE-2021-45617: Command injection in n/a > Unauthenticated attackers can execute arbitrary commands on various NETGEAR routers and mesh systems via command injection vulnerabilities. - **Severity:** Critical 9.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 26 Dec 2021 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-3cgx-5266-6jv3 ## What is CVE-2021-45617? CVE-2021-45617 is a critical command injection vulnerability in Netgear R6400 Firmware, published on 26 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Certain NETGEAR devices are affected by command injection by an unauthenticated attacker. This affects CBR40 before 2.5.0.24, EAX20 before 1.0.0.48, EAX80 before 1.0.1.64, EX7500 before 1.0.0.72, R6400 before 1.0.1.68, R6900P before 1.3.2.132, R7000 before 1.0.11.116, R7000P before 1.3.2.132, R7900 before 1.0.4.38, R7960P before 1.4.1.66, R8000 before 1.0.4.66, RAX200 before 1.0.3.106, RS400 before 1.5.1.80, XR300 before 1.0.3.68, MK62 before 1.0.6.110, MR60 before 1.0.6.110, R6400v2 before 1.0.4.106, R8000P before 1.4.1.66, RAX20 before 1.0.2.64, RAX45 before 1.0.2.82, RAX80 before 1.0.3.106, MS60 before 1.0.6.110, R6700v3 before 1.0.4.106, R7900P before 1.4.1.66, RAX15 before 1.0.2.64, RAX50 before 1.0.2.82, RAX75 before 1.0.3.106, RBR750 before 3.2.16.22, RBR850 before 3.2.16.22, RBS750 before 3.2.16.22, RBS850 before 3.2.16.22, RBK752 before 3.2.16.22, and RBK852 before 3.2.16.22. Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2021-45617? It affects 33 products. Products: Netgear Cbr40 Firmware, Netgear Eax20 Firmware, Netgear Eax80 Firmware, Netgear Ex7500 Firmware, Netgear Mk62 Firmware, Netgear Mr60 Firmware, Netgear Ms60 Firmware, Netgear R6400 Firmware, Netgear R6400v2 Firmware, Netgear R6700v3 Firmware, Netgear R6900p Firmware, Netgear R7000 Firmware, Netgear R7000p Firmware, Netgear R7900 Firmware, Netgear R7900p Firmware, Netgear R7960p Firmware, Netgear R8000 Firmware, Netgear R8000p Firmware, Netgear Rax15 Firmware, Netgear Rax200 Firmware and 13 more. ## How do I fix CVE-2021-45617? No fix has been published for CVE-2021-45617 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-45617 being exploited? There is no known exploitation of CVE-2021-45617 in the wild and no public exploit code. ## Other vulnerabilities in Netgear R6400 Firmware - [CVE-2021-45630](https://insights.sbomify.com/CVE-2021-45630/): Command injection in n/a (critical 10.0) - [CVE-2023-36187](https://insights.sbomify.com/CVE-2023-36187/): Memory corruption in n/a (critical 9.8) - [CVE-2021-45504](https://insights.sbomify.com/CVE-2021-45504/): Auth bypass in n/a (critical 9.6) - [CVE-2021-45507](https://insights.sbomify.com/CVE-2021-45507/): Auth bypass in n/a (critical 9.6) - [CVE-2021-45508](https://insights.sbomify.com/CVE-2021-45508/): Auth bypass in n/a (critical 9.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-45617 and fix it if it is affected. What it is: CVE-2021-45617 is a critical command injection vulnerability in Netgear R6400 Firmware, published on 26 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2021-45617 in the wild and no public exploit code. Affected product: Netgear R6400 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-45617/ (Markdown: https://insights.sbomify.com/CVE-2021-45617/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-45617 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-45617 - OSV: https://osv.dev/vulnerability/CVE-2021-45617 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-45617/ Summaries are generated and may contain mistakes; the official description above is the record.