CVE-2019-20713
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 authenticated user. This affects D8500 before 1.0.3.44, R6250 before 1.0.4.34, R6300v2 before 1.0.4.32, R6400 before 1.0.1.46, R6700 before 1.0.2.6, R6900 before 1.0.2.4, R6900P before 1.3.1.64, R7000 before 1.0.9.42, R7000P before 1.3.1.64, R7100LG before 1.0.0.50, 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, and R8500 before 1.0.2.128.
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 confidenceMultiple NETGEAR router models contain a stack-based buffer overflow vulnerability that can be exploited by an authenticated user. The vulnerability exists in the firmware of the listed devices (D8500, R6250, R6300v2, R6400, R6700, R6900, R6900P, R7000, R7000P, R7100LG, R7300DST, R7900, R7900P, R8000, R8000P, R8300, R8500) prior to the specified firmware versions. An attacker with valid credentials could potentially exploit this 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.3.44< 1.0.4.34< 1.0.4.32< 1.0.1.46< 1.0.2.6< 1.0.2.4< 1.3.1.64< 1.0.9.42CVSS 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 model number printed on the device label or access the router admin panel (usually at 192.168.1.1) and look for the model name in the status or settings pageAffected if Router model is one of: D8500, R6250, R6300v2, R6400, R6700, R6900, R6900P, R7000, R7000P, R7100LG, R7300DST, R7900, R7900P, R8000, R8000P, R8300, R8500
-
Check current firmware versionIn the router admin panel, navigate to Administration > Firmware Update or Advanced > Administration > Router Update to view the current firmware version. Alternatively, check the status page or the label on the device for the firmware versionAffected if Firmware version is below the threshold for your model (D8500: < 1.0.3.44, R6250: < 1.0.4.34, R6300v2: < 1.0.4.32, R6400: < 1.0.1.46, R6700: < 1.0.2.6, R6900: < 1.0.2.4, R6900P: < 1.3.1.64, R7000: < 1.0.9.42, and similar thresholds for R7000P, R7100LG, R7300DST, R7900, R7900P, R8000, R8000P, R8300,
-
Verify remote management accessIn the router admin panel, go to Advanced > Remote Management to check if remote administration is enabled. Also check Advanced > Administration > Router Status for the web management port settingsAffected if Remote management (HTTP/HTTPS) is enabled and accessible from the internet, which increases exposure to authenticated attackers
Your router is affected if it is one of the listed models AND the firmware version is below the specified threshold AND an attacker with valid credentials could reach the admin interface.
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.1.461.0.2.41.0.2.6
Update the router firmware to the versions specified in the advisory (e.g., D8500 to 1.0.3.44, R7000 to 1.0.9.42). If updating is not immediately possible, restrict administrative access to trusted IP addresses only and change default credentials.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20713 — 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-20713 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