# CVE-2021-45610: Memory corruption in n/a > Unauthenticated attackers can trigger a buffer overflow in various NETGEAR routers to execute arbitrary code. - **Severity:** Critical 9.6 (`CVSS:3.1/AC:L/AV:A/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:** 26 Dec 2021 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-m3x6-j75p-546g ## What is CVE-2021-45610? CVE-2021-45610 is a critical memory corruption vulnerability in Netgear D6220 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 a buffer overflow by an unauthenticated attacker. This affects D6220 before 1.0.0.66, D6400 before 1.0.0.100, D7000v2 before 1.0.0.66, D8500 before 1.0.3.58, DC112A before 1.0.0.52, DGN2200v4 before 1.0.0.118, EAX80 before 1.0.1.64, R6250 before 1.0.4.48, R7000 before 1.0.11.110, R7100LG before 1.0.0.72, R7900 before 1.0.4.30, R7960P before 1.4.1.64, R8000 before 1.0.4.62, RAX200 before 1.0.3.106, RS400 before 1.5.1.80, XR300 before 1.0.3.68, R6400v2 before 1.0.4.106, R7000P before 1.3.2.132, R8000P before 1.4.1.64, RAX20 before 1.0.2.82, RAX45 before 1.0.2.82, RAX80 before 1.0.3.106, R6700v3 before 1.0.4.106, R6900P before 1.3.2.132, R7900P before 1.4.1.64, RAX15 before 1.0.2.82, RAX50 before 1.0.2.82, and RAX75 before 1.0.3.106. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2021-45610? It affects 28 products. Products: Netgear D6220 Firmware, Netgear D6400 Firmware, Netgear D7000v2 Firmware, Netgear D8500 Firmware, Netgear Dc112a Firmware, Netgear Dgn2200v4 Firmware, Netgear Eax80 Firmware, Netgear R6250 Firmware, Netgear R6400v2 Firmware, Netgear R6700v3 Firmware, Netgear R6900p Firmware, Netgear R7000 Firmware, Netgear R7000p Firmware, Netgear R7100lg Firmware, Netgear R7900 Firmware, Netgear R7900p Firmware, Netgear R7960p Firmware, Netgear R8000 Firmware, Netgear R8000p Firmware, Netgear Rax15 Firmware and 8 more. ## How do I fix CVE-2021-45610? No fix has been published for CVE-2021-45610 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-45610 being exploited? There is no known exploitation of CVE-2021-45610 in the wild and no public exploit code. ## Other vulnerabilities in Netgear D6220 Firmware - [CVE-2016-6277](https://insights.sbomify.com/CVE-2016-6277/): NETGEAR Multiple Routers Remote Code Execution (high 8.8, exploited in the wild) - [CVE-2021-45527](https://insights.sbomify.com/CVE-2021-45527/): Memory corruption in n/a (critical 9.6) - [CVE-2021-45638](https://insights.sbomify.com/CVE-2021-45638/): Memory corruption in n/a (critical 9.6) - [CVE-2021-34982](https://insights.sbomify.com/CVE-2021-34982/): NETGEAR Multiple Routers httpd Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8) - [CVE-2023-33533](https://insights.sbomify.com/CVE-2023-33533/): Command injection in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-45610 and fix it if it is affected. What it is: CVE-2021-45610 is a critical memory corruption vulnerability in Netgear D6220 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-45610 in the wild and no public exploit code. Affected product: Netgear D6220 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-45610/ (Markdown: https://insights.sbomify.com/CVE-2021-45610/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-45610 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-45610 - OSV: https://osv.dev/vulnerability/CVE-2021-45610 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-45610/ Summaries are generated and may contain mistakes; the official description above is the record.