CVE-2019-20717
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 denial of service. This affects D3600 before 1.0.0.75, D6000 before 1.0.0.75, D7800 before 1.0.1.44, EX2700 before 1.0.1.52, EX6200v2 before 1.0.1.74, EX8000 before 1.0.1.180, R7500v2 before 1.0.3.38, R7800 before 1.0.2.58, RBK20 before 2.3.0.28, RBR20 before 2.3.0.28, RBS20 before 2.3.0.28, RBK50 before 2.3.0.32, RBR50 before 2.3.0.32, RBS50 before 2.3.0.32, RBS40 before 2.3.0.28, SRK60 before 2.2.1.210, SRR60 before 2.2.1.210, SRS60 before 2.2.1.210, WN2000RPTv3 before 1.0.1.34, WN3000RPv2 before 1.0.0.68, WN3000RPv3 before 1.0.2.70, WN3100RPv2 before 1.0.0.60, WNDR4300v2 before 1.0.0.58, and WNDR4500v3 before 1.0.0.58.
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 · moderate confidenceA denial of service vulnerability affects multiple NETGEAR wireless router, extender, and mesh system models. The specific attack vector and vulnerable service are not detailed in the available description, but the vulnerability allows remote or authenticated attackers to cause device unavailability.
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.75< 1.0.0.75< 1.0.1.44< 1.0.1.52< 1.0.1.74< 1.0.1.180< 1.0.3.38< 1.0.2.58CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device modelLog into the router's web admin interface or check the device label to confirm the exact model number (e.g., D3600, D6000, D7800, Ex2700, Ex6200, Ex8000, R7500, R7800).Affected if The device model is one of the following: D3600, D6000, D7800, Ex2700, Ex6200, Ex8000, R7500, or R7800.
-
Check the installed firmware versionAccess the router admin panel, typically at 192.168.1.1 or 192.168.0.1, and navigate to the Firmware Update or Administration section to view the current firmware version.Affected if The device model matches one listed in the affected products and the firmware version is below the fixed version for that model.
-
Compare firmware version against affected rangesCheck if your installed firmware version is less than: D3600/D6000 < 1.0.0.75, D7800 < 1.0.1.44, Ex2700 < 1.0.1.52, Ex6200 < 1.0.1.74, Ex8000 < 1.0.1.180, R7500 < 1.0.3.38, R7800 < 1.0.2.58.Affected if Your installed firmware version is lower than the version threshold listed for your specific model.
-
Assess remote access exposureDetermine if the router management interface is exposed to the internet (check port forwarding rules, WAN access settings, or use an external port scanner to see if ports 80/443 are reachable from outside your local network).Affected if The router admin interface is accessible from the internet and the firmware version is in the affected range.
You are affected if your NETGEAR device matches one of the listed models and is running a firmware version lower than the specified fixed version for that model.
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.751.0.1.441.0.1.52
Update firmware on affected devices to the versions specified in the advisory (e.g., D3600/D6000 to 1.0.0.75, R7800 to 1.0.2.58, RBK50/RBR50/RBS50 to 2.3.0.32). If patching is not immediately possible, restrict network access to trusted users and monitor for device availability issues.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20717 — 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-2019-20717 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