# CVE-2021-45618: Command injection in n/a > Unauthenticated attackers can execute arbitrary commands on various NETGEAR routers and extenders via command injection vulnerabilities. - **Severity:** Critical 9.6 (`CVSS:3.1/AC:L/AV:A/A:H/C:H/I:H/PR:N/S:C/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:** 26 Dec 2021 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-8fp7-34g5-gw45 ## What is CVE-2021-45618? CVE-2021-45618 is a critical command injection vulnerability in Netgear D7800 Firmware, published on 26 Dec 2021. 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 D7800 before 1.0.1.64, EX6200v2 before 1.0.1.86, EX6250 before 1.0.0.134, EX7700 before 1.0.0.216, EX8000 before 1.0.1.232, LBR20 before 2.6.3.50, R7800 before 1.0.2.80, R8900 before 1.0.5.26, R9000 before 1.0.5.26, RAX120 before 1.2.0.16, RBS50Y before 1.0.0.56, WNR2000v5 before 1.0.0.76, XR450 before 2.3.2.114, XR500 before 2.3.2.114, XR700 before 1.0.1.36, EX6150v2 before 1.0.1.98, EX7300 before 1.0.2.158, EX7320 before 1.0.0.134, EX6100v2 before 1.0.1.98, EX6400 before 1.0.2.158, EX7300v2 before 1.0.0.134, EX6410 before 1.0.0.134, RBR10 before 2.6.1.44, RBR20 before 2.6.2.104, RBR40 before 2.6.2.104, RBR50 before 2.7.2.102, EX6420 before 1.0.0.134, RBS10 before 2.6.1.44, RBS20 before 2.6.2.104, RBS40 before 2.6.2.104, RBS50 before 2.7.2.102, EX6400v2 before 1.0.0.134, RBK12 before 2.6.1.44, RBK20 before 2.6.2.104, RBK40 before 2.6.2.104, and RBK50 before 2.7.2.102. Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2021-45618? It affects 36 products. Products: Netgear D7800 Firmware, Netgear Ex6100v2 Firmware, Netgear Ex6150v2 Firmware, Netgear Ex6200v2 Firmware, Netgear Ex6250 Firmware, Netgear Ex6400 Firmware, Netgear Ex6400v2 Firmware, Netgear Ex6410 Firmware, Netgear Ex6420 Firmware, Netgear Ex7300 Firmware, Netgear Ex7300v2 Firmware, Netgear Ex7320 Firmware, Netgear Ex7700 Firmware, Netgear Ex8000 Firmware, Netgear Lbr20 Firmware, Netgear R7800 Firmware, Netgear R8900 Firmware, Netgear R9000 Firmware, Netgear Rax120 Firmware, Netgear Rbk12 Firmware and 16 more. ## How do I fix CVE-2021-45618? No fix has been published for CVE-2021-45618 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-45618 being exploited? There is no known exploitation of CVE-2021-45618 in the wild and no public exploit code. ## Other vulnerabilities in Netgear D7800 Firmware - [CVE-2021-34947](https://insights.sbomify.com/CVE-2021-34947/): NETGEAR R7800 net-cgi Out-Of-Bounds Write Remote Code Execution Vulnerability (high 8.8) - [CVE-2022-27641](https://insights.sbomify.com/CVE-2022-27641/): Integer overflow in R6700v3 (high 8.8) - [CVE-2020-26909](https://insights.sbomify.com/CVE-2020-26909/): Command injection in n/a (high 8.8) - [CVE-2018-21202](https://insights.sbomify.com/CVE-2018-21202/): Memory corruption in n/a (high 8.8) - [CVE-2018-21204](https://insights.sbomify.com/CVE-2018-21204/): Memory corruption in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-45618 and fix it if it is affected. What it is: CVE-2021-45618 is a critical command injection vulnerability in Netgear D7800 Firmware, published on 26 Dec 2021. 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-2021-45618 in the wild and no public exploit code. Affected product: Netgear D7800 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-45618/ (Markdown: https://insights.sbomify.com/CVE-2021-45618/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-45618 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-45618 - OSV: https://osv.dev/vulnerability/CVE-2021-45618 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-45618/ Summaries are generated and may contain mistakes; the official description above is the record.