CVE-2020-35787
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCertain 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflow vulnerability in NETGEAR router firmware affecting multiple models (D3600, D6000, D7000, R6700, R7000, R7800, XR500, and others). The flaw allows authenticated users to potentially execute arbitrary code or cause denial of service via the overflow.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.0.0.76< 1.0.0.76< 1.1.00.36< 1.0.1.70< 1.0.1.78< 1.0.1.78< 1.0.1.186< 1.0.1.18CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your NETGEAR router modelLocate the model number on the device label or check the web admin interface (typically at 192.168.1.1) for the model name under Administration > Router StatusAffected if The model is D3600, D6000, D6200, D7000, Ex6200, Ex7000, Ex8000, Jr6150, R6700, R7000, R7800, XR500, or related variants
-
Check your current firmware versionLog into the router web interface and navigate to Administration > Router Status (or similar) to view the firmware version displayedAffected if The installed firmware version is lower than the patched versions (D3600/D6000: 1.0.0.76, D6200: 1.1.00.36, D7000: 1.0.1.70, Ex6200/Ex7000: 1.0.1.78, Ex8000: 1.0.1.186, Jr6150: 1.0.1.18, R7000: 1.0.9.42, XR500: 2.3.2.40, and similar thresholds for other models)
-
Verify if remote management is enabledIn the web interface, go to Advanced > Remote Management (or Administration > Remote Management) and check if Enable Remote Management is checkedAffected if Remote management is enabled, allowing unauthenticated network attackers to potentially reach the login page (though the CVE requires valid credentials)
-
Confirm the web management interface is accessibleAttempt to reach the router login page from both LAN and WAN IP addresses using HTTP/HTTPSAffected if The router web interface is reachable from the internet (WAN)
You are likely affected if your router model matches one of the listed models and your firmware version is below the patched threshold, especially if the web interface is internet-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.0.761.0.1.181.0.1.70
Update affected devices to the patched firmware versions specified in the advisory (e.g., R7000 to 1.0.9.42, XR500 to 2.3.2.40). If patching is not possible, limit administrative access and monitor for unauthorized activity.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35787 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-35787 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data