CVE-2019-20712
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 D6220 before 1.0.0.52, D6400 before 1.0.0.86, D7000v2 before 1.0.0.53, D8500 before 1.0.3.44, DGN2200v4 before 1.0.0.110, DGND2200Bv4 before 1.0.0.109, R6250 before 1.0.4.34, R6300v2 before 1.0.4.32, R6400 before 1.0.1.46, R6400v2 before 1.0.2.62, R6700 before 1.0.2.6, R6900 before 1.0.2.4, R6900P before 1.3.1.64, R7000 before 1.0.9.60, R7000P before 1.3.1.64, R7100LG before 1.0.0.52, R7300DST before 1.0.0.70, R7900 before 1.0.3.8, R7900P before 1.4.1.30, R8000 before 1.0.4.28, R8000P before 1.4.1.30, R8300 before 1.0.2.128, R8500 before 1.0.2.128, WNDR3400v3 before 1.0.1.24, and WNR3500Lv2 before 1.2.0.56.
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 multiple NETGEAR router firmware versions allows authenticated users to overflow a buffer, potentially leading to arbitrary code execution or device compromise. The vulnerability exists in the web management interface and requires authentication to exploit.
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.52< 1.0.0.86< 1.0.0.53< 1.0.3.44< 1.0.0.110< 1.0.0.109< 1.0.4.34< 1.0.4.32CVSS 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 device label on the router or log into the admin interface and look for the model number displayed on the status or administration page.Affected if The model is NOT one of: D6220, D6400, D7000, D8500, Dgn2200, Dgnd2200b, R6250, or R6300.
-
Check firmware versionLog into the router web management interface, navigate to the Administration or Firmware Upgrade section, and record the displayed firmware version number.Affected if The installed firmware version is lower than the threshold for your model: D6220 < 1.0.0.52, D6400 < 1.0.0.86, D7000 < 1.0.0.53, D8500 < 1.0.3.44, Dgn2200 < 1.0.0.110, Dgnd2200b < 1.0.0.109, R6250 < 1.0.4.34, or R6300 < 1.0.4.32.
-
Verify web management interface is accessibleAttempt to access the router login page by entering the router IP address in a web browser. Confirm the login page loads.Affected if The web management interface is accessible from untrusted networks (e.g., WAN/internet-facing).
-
Confirm administrative access is enabledCheck the router security settings under Administration > Remote Management or similar. Verify that remote administration is enabled or that the default admin credentials have not been changed.Affected if Remote web management is enabled and the default admin credentials remain in use, allowing authenticated access to the interface where the overflow occurs.
You are affected if your router model is on the list AND the firmware version is below the specified threshold AND the web management interface is accessible with valid admin credentials.
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.521.0.0.531.0.0.86
Update affected NETGEAR devices to the specified firmware versions (e.g., D6220 to 1.0.0.52, R7000 to 1.0.9.60) or later. If updates are unavailable, restrict web management interface access to trusted networks only.
- 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-20712 — 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-20712 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