# CVE-2020-35798: 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.3 (`CVSS:3.1/AC:L/AV:L/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:** 29 Dec 2020 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-jrq7-2cwg-jfgc ## What is CVE-2020-35798? CVE-2020-35798 is a critical command injection vulnerability in Netgear R6900p Firmware, published on 29 Dec 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 R6400v2 before 1.0.4.84, R6700v3 before 1.0.4.84, R6900P before 1.3.2.124, R7000 before 1.0.11.100, R7000P before 1.3.2.124, R7800 before 1.0.2.74, R7850 before 1.0.5.60, R7900 before 1.0.4.26, R7960P before 1.4.1.50, R8000 before 1.0.4.52, R7900P before 1.4.1.50, R8000P before 1.4.1.50, RAX15 before 1.0.1.64, RAX20 before 1.0.1.64, RAX200 before 1.0.1.12, RAX45 before 1.0.2.66, RAX50 before 1.0.2.66, RAX75 before 1.0.3.102, RAX80 before 1.0.3.102, RBK752 before 3.2.16.6, RBR750 before 3.2.16.6, RBS750 before 3.2.16.6, RBK852 before 3.2.15.25, RBR850 before 3.2.15.25, RBS850 before 3.2.15.25, RBK842 before 3.2.15.25, RBR840 before 3.2.15.25, RBS840 before 3.2.15.25, RS400 before 1.5.0.48, and XR300 before 1.0.3.50. Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2020-35798? It affects 30 products. Products: Netgear R6400v2 Firmware, Netgear R6700v3 Firmware, Netgear R6900p Firmware, Netgear R7000 Firmware, Netgear R7000p Firmware, Netgear R7800 Firmware, Netgear R7850 Firmware, Netgear R7900 Firmware, Netgear R7900p Firmware, Netgear R7960p Firmware, Netgear R8000 Firmware, Netgear R8000p Firmware, Netgear Rax15 Firmware, Netgear Rax200 Firmware, Netgear Rax20 Firmware, Netgear Rax45 Firmware, Netgear Rax50 Firmware, Netgear Rax75 Firmware, Netgear Rax80 Firmware, Netgear Rbk752 Firmware and 10 more. ## How do I fix CVE-2020-35798? No fix has been published for CVE-2020-35798 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-35798 being exploited? There is no known exploitation of CVE-2020-35798 in the wild and no public exploit code. ## Other vulnerabilities in Netgear R6900p Firmware - [CVE-2021-45650](https://insights.sbomify.com/CVE-2021-45650/): Information disclosure in n/a (critical 9.1) - [CVE-2021-45643](https://insights.sbomify.com/CVE-2021-45643/): Misconfiguration in n/a (high 8.2) - [CVE-2021-40847](https://insights.sbomify.com/CVE-2021-40847/): Code injection in n/a (high 8.1) - [CVE-2024-51010](https://insights.sbomify.com/CVE-2024-51010/): Command injection in n/a (high 8.0) - [CVE-2024-51021](https://insights.sbomify.com/CVE-2024-51021/): Command injection in n/a (high 8.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-35798 and fix it if it is affected. What it is: CVE-2020-35798 is a critical command injection vulnerability in Netgear R6900p Firmware, published on 29 Dec 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-2020-35798 in the wild and no public exploit code. Affected product: Netgear R6900p 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-2020-35798/ (Markdown: https://insights.sbomify.com/CVE-2020-35798/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-35798 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-35798 - OSV: https://osv.dev/vulnerability/CVE-2020-35798 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-35798/ Summaries are generated and may contain mistakes; the official description above is the record.