# CVE-2018-21169: Misconfiguration in n/a > Incorrect security settings in NETGEAR routers allow attackers to bypass security controls, requiring firmware updates to remediate. - **Severity:** High 8.8 (`CVSS:3.0/AC:L/AV:A/A:H/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:** 27 Apr 2020 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-4x8j-w832-rw4c ## What is CVE-2018-21169? CVE-2018-21169 is a high-severity vulnerability in Netgear D7000 Firmware, published on 27 Apr 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 incorrect configuration of security settings. This affects D7000 before 2018-03-01, D7800 before 1.0.1.31, D8500 before 1.0.3.36, JNR1010v2 before 1.1.0.46, JR6150 before 1.0.1.14, JWNR2010v5 before 1.1.0.46, PR2000 before 2018-03-01, R6050 before 1.0.1.14, R6220 before 1.1.0.60, R6400 before 1.1.0.26, R6400v2 before 1.0.2.46, R6700v2 before 1.2.0.2, R6800 before 1.2.0.2, R6900v2 before 1.2.0.2, R7300DST before 1.0.0.56, R7500 before 1.0.0.112, R7500v2 before 1.0.3.24, R7800 before 1.0.2.36, R7900P before 1.1.4.6, R8000P before 1.1.4.6, R8300 before 1.0.2.104, R8500 before 1.0.2.104, R9000 before 1.0.2.52, WNDR3700v4 before 1.0.2.94, WNDR3700v5 before 1.1.0.50, WNDR4300 before 1.0.2.96, WNDR4300v2 before 1.0.0.52, WNDR4500v3 before 1.0.0.52, WNR1000v4 before 1.1.0.46, WNR2020 before 1.1.0.46, and WNR2050 before 1.1.0.46. ## Which versions are affected by CVE-2018-21169? It affects 27 products. Products: Netgear D7000 Firmware, Netgear D7800 Firmware, Netgear D8500 Firmware, Netgear Jnr1010 Firmware, Netgear Jr6150 Firmware, Netgear Jwnr2010 Firmware, Netgear Pr2000 Firmware, Netgear R6050 Firmware, Netgear R6220 Firmware, Netgear R6400 Firmware, Netgear R6700 Firmware, Netgear R6800 Firmware, Netgear R6900 Firmware, Netgear R7300dst Firmware, Netgear R7500 Firmware, Netgear R7800 Firmware, Netgear R7900p Firmware, Netgear R8000p Firmware, Netgear R8300 Firmware, Netgear R8500 Firmware and 7 more. ## How do I fix CVE-2018-21169? No fix has been published for CVE-2018-21169 yet. Limit exposure of the affected software until one is available. ## Is CVE-2018-21169 being exploited? There is no known exploitation of CVE-2018-21169 in the wild and no public exploit code. ## Other vulnerabilities in Netgear D7000 Firmware - [CVE-2021-45497](https://insights.sbomify.com/CVE-2021-45497/): Auth bypass in n/a (critical 9.4) - [CVE-2021-45496](https://insights.sbomify.com/CVE-2021-45496/): Auth bypass in n/a (critical 9.1) - [CVE-2017-18791](https://insights.sbomify.com/CVE-2017-18791/): Cross-site request forgery in n/a (high 8.8) - [CVE-2021-45512](https://insights.sbomify.com/CVE-2021-45512/): Weak cryptography in n/a (high 8.6) - [CVE-2017-18843](https://insights.sbomify.com/CVE-2017-18843/): Information disclosure in n/a (high 8.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-21169 and fix it if it is affected. What it is: CVE-2018-21169 is a high-severity vulnerability in Netgear D7000 Firmware, published on 27 Apr 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-2018-21169 in the wild and no public exploit code. Affected product: Netgear D7000 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-2018-21169/ (Markdown: https://insights.sbomify.com/CVE-2018-21169/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-21169 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-21169 - OSV: https://osv.dev/vulnerability/CVE-2018-21169 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-21169/ Summaries are generated and may contain mistakes; the official description above is the record.