CVE-2019-20728
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 D6400 before 1.0.0.74, D7000v2 before 1.0.0.74, D7800 before 1.0.1.34, D8500 before 1.0.3.39, DGN2200v4 before 1.0.0.102, DGND2200Bv4 before 1.0.0.102, DM200 before 1.0.0.52, JNDR3000 before 1.0.0.22, RBK50 before 2.3.5.30, RBR50 before 2.3.5.30, RBS50 before 2.3.5.30, RBW30 before 2.1.2.6, R6250 before 1.0.4.26, R6300v2 before 1.0.4.24, R6400 before 1.0.1.36, R6400v2 before 1.0.2.52, R6700 before 1.0.1.44, R6900 before 1.0.1.44, R7000 before 1.0.9.26, R6900P before 1.3.0.20, R7000P before 1.3.0.20, R7100LG before 1.0.0.40, R7300DST before 1.0.0.62, R7500v2 before 1.0.3.26, R7800 before 1.0.2.44, R7900 before 1.0.2.10, R8000 before 1.0.4.12, R7900P before 1.3.0.10, R8000P before 1.3.0.10, R8300 before 1.0.2.116, R8500 before 1.0.2.116, R8900 before 1.0.3.10, R9000 before 1.0.3.10, WNDR3400v3 before 1.0.1.18, WNDR3700v4 before 1.0.2.96, WNDR4300v1 before 1.0.2.98, WNDR4300v2 before 1.0.0.54, WNDR4500v3 before 1.0.0.54, WNR2000v5 before 1.0.0.64, and WNR3500Lv2 before 1.2.0.48.
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 confidenceA buffer overflow vulnerability exists in multiple NETGEAR router models that can be exploited by an authenticated user. The vulnerability affects various router series (R6000, R7000, R8000, etc.) and wireless systems (Orbi, EX) with firmware versions prior to the specified patched releases. Successful exploitation could allow an authenticated attacker to execute arbitrary code or cause a denial of service.
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.74< 1.0.0.74< 1.0.1.34< 1.0.3.39< 1.0.0.102< 1.0.0.102< 1.0.0.52< 1.0.0.22CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Access router administration interfaceOpen a web browser and navigate to the router's default gateway (typically 192.168.1.1). Log in with administrator credentials to access the web management console.Affected if Unable to log in or access the admin interface (authenticated access required for this vulnerability).
-
Locate firmware version informationIn the router web interface, navigate to the status or advanced settings page. Look for a field labeled 'Firmware Version', 'Router Version', or similar. This is usually found on the main status dashboard or under 'Administration' > 'Router Update'.Affected if Firmware version displayed is lower than the patched version for your specific model.
-
Identify exact router model numberCheck the router physical label or the web interface for the exact model number (e.g., D6400, D7000, D7800, D8500, Dgn2200, Dgnd2200b, Dm200, Jndr3000). The model is typically displayed on the main status page or on a 'Router Info' section.Affected if Router model is one of the affected models listed in the CVE.
-
Compare installed version against patched versionsCompare your installed firmware version to the threshold: D6400/D7000 < 1.0.0.74, D7800 < 1.0.1.34, D8500 < 1.0.3.39, Dgn2200/Dgnd2200b < 1.0.0.102, Dm200 < 1.0.0.52, Jndr3000 < 1.0.0.22. If your version is lower than the threshold for your model, the device is affected.Affected if Installed firmware version is less than the patched version threshold for your specific model.
The device is affected if it is one of the listed Netgear models (D6400, D7000, D7800, D8500, Dgn2200, Dgnd2200b, Dm200, Jndr3000) AND the installed firmware version is lower than the patched version threshold 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.221.0.0.521.0.0.74
Apply the vendor-supplied firmware updates to the specific versions listed for each affected model (e.g., R7000 to 1.0.9.26, R6400 to 1.0.1.36). If firmware updates are unavailable for certain devices, consider network segmentation or replacement with supported hardware.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20728 — 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-20728 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