CVE-2019-20716
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 DGN2200v4 before 1.0.0.110 and DGND2200Bv4 before 1.0.0.109.
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 confidenceNETGEAR DGN2200v4 and DGND2200Bv4 routers contain a stack-based buffer overflow vulnerability that can be exploited by an unauthenticated remote attacker, potentially allowing arbitrary code execution or device compromise.
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.110< 1.0.0.109CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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.
-
Identify router modelCheck the physical device label or web interface for the exact model number (DGN2200v4 or DGND2200Bv4)Affected if Model is DGN2200v4 or DGND2200Bv4
-
Access router administration interfaceNavigate to the router's web interface (typically http://192.168.1.1) and log in to access firmware version informationAffected if Unable to access the router interface to verify version
-
Locate firmware versionIn the router web interface, look for a Firmware Version or Router Status section (usually under Administration, Settings, or a Status page)Affected if Firmware version cannot be determined from the interface
-
Compare version to affected rangeFor DGN2200v4: note the firmware version (e.g., 1.0.0.50). For DGND2200Bv4: note the firmware version. Compare numerically to 1.0.0.110 (DGN2200v4) or 1.0.0.109 (DGND2200Bv4)Affected if DGN2200v4 firmware is below 1.0.0.110 OR DGND2200Bv4 firmware is below 1.0.0.109
The device is affected if it is a DGN2200v4 router running firmware version lower than 1.0.0.110, or a DGND2200Bv4 router running firmware version lower than 1.0.0.109.
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.1091.0.0.110
Update firmware to version 1.0.0.110 or later for DGN2200v4, and version 1.0.0.109 or later for DGND2200Bv4, as these patches address the buffer overflow vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20716 — 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-20716 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