# CVE-2021-45658: Code injection in n/a > Attackers can execute arbitrary code on vulnerable NETGEAR routers and extenders via server-side injection flaws. - **Severity:** High 7.1 (`CVSS:3.1/AC:L/AV:L/A:N/C:H/I:H/PR:L/S:U/UI:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **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-7j2w-pcvm-23jm ## What is CVE-2021-45658? CVE-2021-45658 is a high-severity code 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 server-side injection. This affects D7800 before 1.0.1.58, DM200 before 1.0.0.66, EX2700 before 1.0.1.56, EX6150v2 before 1.0.1.86, EX6100v2 before 1.0.1.86, EX6200v2 before 1.0.1.78, EX6250 before 1.0.0.110, EX6410 before 1.0.0.110, EX6420 before 1.0.0.110, EX6400v2 before 1.0.0.110, EX7300 before 1.0.2.144, EX6400 before 1.0.2.144, EX7320 before 1.0.0.110, EX7300v2 before 1.0.0.110, R7500v2 before 1.0.3.48, R7800 before 1.0.2.68, R8900 before 1.0.5.2, R9000 before 1.0.5.2, RAX120 before 1.0.1.90, RBK40 before 2.5.1.16, RBK20 before 2.5.1.16, RBR20 before 2.5.1.16, RBS20 before 2.5.1.16, RBK50 before 2.5.1.16, RBR50 before 2.5.1.16, RBS50 before 2.5.1.16, RBS50Y before 2.6.1.40, WN3000RPv2 before 1.0.0.78, WN3000RPv3 before 1.0.2.80, WNR2000v5 before 1.0.0.72, XR500 before 2.3.2.56, and XR700 before 1.0.1.20. Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) ## Which versions are affected by CVE-2021-45658? It affects 32 products. Products: Netgear D7800 Firmware, Netgear Dm200 Firmware, Netgear Ex2700 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 R7500v2 Firmware, Netgear R7800 Firmware, Netgear R8900 Firmware, Netgear R9000 Firmware, Netgear Rax120 Firmware, Netgear Rbk20 Firmware and 12 more. ## How do I fix CVE-2021-45658? No fix has been published for CVE-2021-45658 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-45658 being exploited? There is no known exploitation of CVE-2021-45658 in the wild and no public exploit code. ## Other vulnerabilities in Netgear D7800 Firmware - [CVE-2021-45618](https://insights.sbomify.com/CVE-2021-45618/): Command injection in n/a (critical 9.6) - [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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-45658 and fix it if it is affected. What it is: CVE-2021-45658 is a high-severity code 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-45658 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-45658/ (Markdown: https://insights.sbomify.com/CVE-2021-45658/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-45658 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-45658 - OSV: https://osv.dev/vulnerability/CVE-2021-45658 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-45658/ Summaries are generated and may contain mistakes; the official description above is the record.