# CVE-2020-35787: Memory corruption in n/a > Authenticated attackers can exploit a buffer overflow in NETGEAR router firmware to execute arbitrary code or escalate privileges. - **Severity:** High 8.0 (`CVSS:3.1/AC:L/AV:A/A:H/C:H/I:H/PR:L/S:U/UI:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **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-6gcw-7qx9-8vhw ## What is CVE-2020-35787? CVE-2020-35787 is a high-severity memory corruption vulnerability in Netgear D3600 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 a buffer overflow by an authenticated user. This affects D3600 before 1.0.0.76, D6000 before 1.0.0.76, D6200 before 1.1.00.36, D7000 before 1.0.1.70, EX6200v2 before 1.0.1.78, EX7000 before 1.0.1.78, EX8000 before 1.0.1.186, JR6150 before 1.0.1.18, PR2000 before 1.0.0.28, R6020 before 1.0.0.42, R6050 before 1.0.1.18, R6080 before 1.0.0.42, R6120 before 1.0.0.46, R6220 before 1.1.0.80, R6260 before 1.1.0.64, R6300v2 before 1.0.4.34, R6700 before 1.0.2.6, R6700v2 before 1.2.0.36, R6800 before 1.2.0.36, R6900 before 1.0.2.4, R6900P before 1.3.1.64, R6900v2 before 1.2.0.36, R7000 before 1.0.9.42, R7000P before 1.3.1.64, R7800 before 1.0.2.60, R8900 before 1.0.4.12, R9000 before 1.0.4.12, and XR500 before 2.3.2.40. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2020-35787? It affects 26 products. Products: Netgear D3600 Firmware, Netgear D6000 Firmware, Netgear D6200 Firmware, Netgear D7000 Firmware, Netgear Ex6200 Firmware, Netgear Ex7000 Firmware, Netgear Ex8000 Firmware, Netgear Jr6150 Firmware, Netgear Pr2000 Firmware, Netgear R6020 Firmware, Netgear R6050 Firmware, Netgear R6080 Firmware, Netgear R6120 Firmware, Netgear R6220 Firmware, Netgear R6260 Firmware, Netgear R6300 Firmware, Netgear R6700 Firmware, Netgear R6800 Firmware, Netgear R6900 Firmware, Netgear R6900p Firmware and 6 more. ## How do I fix CVE-2020-35787? No fix has been published for CVE-2020-35787 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-35787 being exploited? There is no known exploitation of CVE-2020-35787 in the wild and no public exploit code. ## Other vulnerabilities in Netgear D3600 Firmware - [CVE-2020-35799](https://insights.sbomify.com/CVE-2020-35799/): Memory corruption in n/a (high 8.8) - [CVE-2018-21207](https://insights.sbomify.com/CVE-2018-21207/): Memory corruption in n/a (high 8.8) - [CVE-2018-21210](https://insights.sbomify.com/CVE-2018-21210/): Memory corruption in n/a (high 8.8) - [CVE-2018-21211](https://insights.sbomify.com/CVE-2018-21211/): Memory corruption in n/a (high 8.8) - [CVE-2018-21212](https://insights.sbomify.com/CVE-2018-21212/): Memory corruption in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-35787 and fix it if it is affected. What it is: CVE-2020-35787 is a high-severity memory corruption vulnerability in Netgear D3600 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-35787 in the wild and no public exploit code. Affected product: Netgear D3600 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-35787/ (Markdown: https://insights.sbomify.com/CVE-2020-35787/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-35787 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-35787 - OSV: https://osv.dev/vulnerability/CVE-2020-35787 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-35787/ Summaries are generated and may contain mistakes; the official description above is the record.