# CVE-2021-45647: Information disclosure in n/a > Attackers can disclose sensitive information from various NETGEAR routers and extenders, requiring firmware upgrades to mitigate. - **Severity:** Medium 6.5 (`CVSS:3.1/AC:L/AV:A/A:N/C:H/I:N/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:** 26 Dec 2021 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-wgj8-hg3j-j44v ## What is CVE-2021-45647? CVE-2021-45647 is a medium-severity vulnerability in Netgear R6120 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 disclosure of sensitive information. This affects EAX80 before 1.0.1.62, EX7000 before 1.0.1.104, R6120 before 1.0.0.76, R6220 before 1.1.0.110, R6230 before 1.1.0.110, R6260 before 1.1.0.78, R6850 before 1.1.0.78, R6350 before 1.1.0.78, R6330 before 1.1.0.78, R6800 before 1.2.0.76, R6900v2 before 1.2.0.76, R6700v2 before 1.2.0.76, R7000 before 1.0.11.116, R6900P before 1.3.3.140, R7000P before 1.3.3.140, R7200 before 1.2.0.76, R7350 before 1.2.0.76, R7400 before 1.2.0.76, R7450 before 1.2.0.76, AC2100 before 1.2.0.76, AC2400 before 1.2.0.76, AC2600 before 1.2.0.76, R7900 before 1.0.4.38, R7960P before 1.4.1.66, R8000 before 1.0.4.68, R7900P before 1.4.1.66, R8000P before 1.4.1.66, RAX15 before 1.0.2.82, RAX20 before 1.0.2.82, RAX200 before 1.0.3.106, RAX45 before 1.0.2.72, RAX50 before 1.0.2.72, RAX75 before 1.0.3.106, and RAX80 before 1.0.3.106. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2021-45647? It affects 34 products. Products: Netgear Ac2100 Firmware, Netgear Ac2400 Firmware, Netgear Ac2600 Firmware, Netgear Eax80 Firmware, Netgear Ex7000 Firmware, Netgear R6120 Firmware, Netgear R6220 Firmware, Netgear R6230 Firmware, Netgear R6260 Firmware, Netgear R6330 Firmware, Netgear R6350 Firmware, Netgear R6700v2 Firmware, Netgear R6800 Firmware, Netgear R6850 Firmware, Netgear R6900p Firmware, Netgear R6900v2 Firmware, Netgear R7000 Firmware, Netgear R7000p Firmware, Netgear R7200 Firmware, Netgear R7350 Firmware and 14 more. ## How do I fix CVE-2021-45647? No fix has been published for CVE-2021-45647 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-45647 being exploited? There is no known exploitation of CVE-2021-45647 in the wild and no public exploit code. ## Other vulnerabilities in Netgear R6120 Firmware - [CVE-2021-38516](https://insights.sbomify.com/CVE-2021-38516/): Missing authorization in n/a (critical 10.0) - [CVE-2021-29068](https://insights.sbomify.com/CVE-2021-29068/): Memory corruption in n/a (critical 9.9) - [CVE-2020-35795](https://insights.sbomify.com/CVE-2020-35795/): Memory corruption in n/a (critical 9.8) - [CVE-2020-35800](https://insights.sbomify.com/CVE-2020-35800/): Misconfiguration in n/a (critical 9.4) - [CVE-2020-26927](https://insights.sbomify.com/CVE-2020-26927/): Auth bypass in n/a (critical 9.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-45647 and fix it if it is affected. What it is: CVE-2021-45647 is a medium-severity vulnerability in Netgear R6120 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-45647 in the wild and no public exploit code. Affected product: Netgear R6120 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-45647/ (Markdown: https://insights.sbomify.com/CVE-2021-45647/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-45647 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-45647 - OSV: https://osv.dev/vulnerability/CVE-2021-45647 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-45647/ Summaries are generated and may contain mistakes; the official description above is the record.