# CVE-2021-38527: Command injection in n/a > Unauthenticated attackers can execute arbitrary commands on various NETGEAR routers and mesh systems via command injection vulnerabilities. - **Severity:** High 8.1 (`CVSS:3.1/AC:L/AV:A/A:N/C:H/I:H/PR:N/S:U/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:** 11 Aug 2021 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-qccx-cxhf-2m4w ## What is CVE-2021-38527? CVE-2021-38527 is a high-severity command injection vulnerability in Netgear R7800 Firmware, published on 11 Aug 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 CBR40 before 2.5.0.14, EX6100v2 before 1.0.1.98, EX6150v2 before 1.0.1.98, EX6250 before 1.0.0.132, EX6400 before 1.0.2.158, EX6400v2 before 1.0.0.132, EX6410 before 1.0.0.132, EX6420 before 1.0.0.132, EX7300 before 1.0.2.158, EX7300v2 before 1.0.0.132, EX7320 before 1.0.0.132, EX7700 before 1.0.0.216, EX8000 before 1.0.1.232, R7800 before 1.0.2.78, RBK12 before 2.6.1.44, RBR10 before 2.6.1.44, RBS10 before 2.6.1.44, RBK20 before 2.6.1.38, RBR20 before 2.6.1.36, RBS20 before 2.6.1.38, RBK40 before 2.6.1.38, RBR40 before 2.6.1.36, RBS40 before 2.6.1.38, RBK50 before 2.6.1.40, RBR50 before 2.6.1.40, RBS50 before 2.6.1.40, RBK752 before 3.2.16.6, RBR750 before 3.2.16.6, RBS750 before 3.2.16.6, RBK852 before 3.2.16.6, RBR850 before 3.2.16.6, RBS850 before 3.2.16.6, RBS40V before 2.6.2.4, RBS50Y before 2.6.1.40, RBW30 before 2.6.2.2, and XR500 before 2.3.2.114. Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2021-38527? It affects 34 products. Products: Netgear Cbr40 Firmware, Netgear Ex6100 Firmware, Netgear Ex6150 Firmware, Netgear Ex6250 Firmware, Netgear Ex6400 Firmware, Netgear Ex6410 Firmware, Netgear Ex6420 Firmware, Netgear Ex7300 Firmware, Netgear Ex7320 Firmware, Netgear Ex7700 Firmware, Netgear Ex8000 Firmware, Netgear R7800 Firmware, Netgear Rbk12 Firmware, Netgear Rbk20 Firmware, Netgear Rbk40 Firmware, Netgear Rbk50 Firmware, Netgear Rbk752 Firmware, Netgear Rbk852 Firmware, Netgear Rbr10 Firmware, Netgear Rbr20 Firmware and 14 more. ## How do I fix CVE-2021-38527? No fix has been published for CVE-2021-38527 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-38527 being exploited? There is no known exploitation of CVE-2021-38527 in the wild and no public exploit code. ## Other vulnerabilities in Netgear R7800 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-45617](https://insights.sbomify.com/CVE-2021-45617/): Command injection 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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-38527 and fix it if it is affected. What it is: CVE-2021-38527 is a high-severity command injection vulnerability in Netgear R7800 Firmware, published on 11 Aug 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-38527 in the wild and no public exploit code. Affected product: Netgear R7800 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-38527/ (Markdown: https://insights.sbomify.com/CVE-2021-38527/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-38527 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-38527 - OSV: https://osv.dev/vulnerability/CVE-2021-38527 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-38527/ Summaries are generated and may contain mistakes; the official description above is the record.