CVE-2020-35799
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 stack-based buffer overflow by an unauthenticated attacker. This affects D3600 before 1.0.0.76, D6000 before 1.0.0.78, D6200 before 1.1.00.32, D7000 before 1.0.1.68, D7800 before 1.0.1.56, DM200 before 1.0.0.61, EX2700 before 1.0.1.52, EX6100v2 before 1.0.1.76, EX6150v2 before 1.0.1.76, EX6200v2 before 1.0.1.74, EX6400 before 1.0.2.140, EX7300 before 1.0.2.140, EX8000 before 1.0.1.186, JR6150 before 1.0.1.18, PR2000 before 1.0.0.28, R6020 before 1.0.0.38, R6050 before 1.0.1.18, R6080 before 1.0.0.38, R6120 before 1.0.0.46, R6220 before 1.1.0.80, R6230 before 1.1.0.80, R6260 before 1.1.0.40, R6700v2 before 1.2.0.36, R6800 before 1.2.0.36, R6900v2 before 1.2.0.36, R7500v2 before 1.0.3.40, R7800 before 1.0.2.62, R8900 before 1.0.4.12, R9000 before 1.0.4.12, RBK20 before 2.3.0.28, RBR20 before 2.3.0.28, RBS20 before 2.3.0.28, RBK40 before 2.3.0.28, RBR40 before 2.3.0.28, RBS40 before 2.3.0.28, RBK50 before 2.3.0.32, RBR50 before 2.3.0.32, RBS50 before 2.3.0.32, WN2000RPTv3 before 1.0.1.34, WN3000RPv2 before 1.0.0.78, WN3000RPv2 before 1.0.0.78, WN3000RPv3 before 1.0.2.78, WN3100RPv2 before 1.0.0.66, WNR2000v5 before 1.0.0.70, WNR2020 before 1.1.0.62, XR450 before 2.3.2.32, and XR500 before 2.3.2.32.
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 confidenceStack-based buffer overflow vulnerability in NETGEAR wireless routers and range extenders allows remote unauthenticated attackers to execute arbitrary code via malformed HTTP requests. The vulnerability affects 54 different NETGEAR device models across multiple product lines (D, EX, R, RBK, RBR, RBS, WN, WNR, XR series) running firmware versions prior to the specified patched releases.
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.078< 1.1.00.32< 1.0.1.68< 1.0.1.56< 1.0.0.61< 1.0.1.52< 1.0.1.76CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 NETGEAR device modelCheck the device label, web interface footer, or network fingerprint (many routers expose model info in HTTP headers or on the login page)Affected if Device is a NETGEAR router or range extender from the D, EX, R, RBK, RBR, RBS, WN, WNR, or XR series
-
Locate firmware version in web interfaceLog into the router web interface (typically at 192.168.1.1 or 192.168.0.1) and check under Administration > Firmware Update or Router Status pageAffected if Firmware version cannot be determined or device is inaccessible via web interface
-
Compare firmware version to affected rangesMatch your firmware version against the specific thresholds: D3600 < 1.0.0.76, D6000 < 1.0.0.78, D6200 < 1.1.00.32, D7000 < 1.0.1.68, D7800 < 1.0.1.56, Dm200 < 1.0.0.61, Ex2700 < 1.0.1.52, Ex6100v2 < 1.0.1.76 (and other affected models if your specific model is listed)Affected if Installed firmware version is lower than the patched version for your exact model
-
Confirm HTTP service is exposedVerify that the router web management interface is accessible over HTTP/HTTPS from the network (the vulnerability is exploited via malformed HTTP requests)Affected if HTTP service is enabled and reachable from network segments other than trusted management VLANs
-
Check for vendor disclosureReview NETGEAR security advisory for your device model to confirm it is included in CVE-2020-35799Affected if Your specific model is not listed in NETGEAR's advisory for this CVE or has no published patch
You are affected if you run a NETGEAR router or range extender model listed in the advisory with a firmware version below the patched release threshold and the device HTTP interface is network-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.
dbcve · scoped1.0.0.611.0.0.761.0.1.52
Apply available firmware updates from NETGEAR for each affected device model. For devices that have reached end-of-life and no longer receive updates, consider replacement with newer hardware.
Model-specific firmware: D3600 (1.0.0.76), D6000 (1.0.0.78), D6200 (1.1.00.32), D7000 (1.0.1.68), D7800 (1.0.1.56), DM200 (1.0.0.61), EX2700 (1.0.1.52), EX6100v2 (1.0.1.76) - download exact version from NETGEAR support site
- 1. Identify the specific NETGEAR device model number from the affected list (D3600, D6000, D6200, D7000, D7800, DM200, EX2700, EX6100v2, or other affected models listed in the CVE)
- 2. Access the router's web interface by entering the router's IP address in a web browser (typically 192.168.1.1 or 192.168.0.1)
- 3. Navigate to the Administration or Advanced settings section and locate the Firmware Update option
- 4. Check the current firmware version to confirm it is vulnerable (versions prior to the fixed release)
- 5. Download the fixed firmware version from the official NETGEAR support site (support.netgear.com) by searching for the specific model number
- 6. In the router's web interface, select the option to upload manually and choose the downloaded firmware file
- 7. Wait for the firmware upload and installation to complete - do not power off the router during this process
- 8. After the router restarts, verify the new firmware version matches the fixed release version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-35799 — 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-35799 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