CVE-2019-20682
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 D3600 before 1.0.0.76, D6000 before 1.0.0.76, D6200 before 1.1.00.32, D7000 before 1.0.1.68, JR6150 before 1.0.1.18, PR2000 before 1.0.0.28, R6020 before 1.0.0.38, R6050 before 1.0.1.18, R6080 before 1.0.0.38, R6120 before 1.0.0.46, R6220 before 1.1.0.80, R6260 before 1.1.0.40, R6700v2 before 1.2.0.36, R6800 before 1.2.0.36, R6900v2 before 1.2.0.36, WNR2020 before 1.1.0.62, and XR500 before 2.3.2.32.
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 confidenceStack-based buffer overflow in NETGEAR router firmware allowing remote code execution by unauthenticated attackers. The vulnerability exists in the web management interface and can be exploited without credentials, likely through malformed HTTP requests that overflow a stack-allocated buffer.
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.76< 1.0.0.76< 1.1.00.32< 1.0.1.68< 1.0.1.18< 1.0.0.28< 1.0.0.38< 1.0.1.18CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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 the NETGEAR router modelLocate the model number on the device label or access the web管理界面 (typically at 192.168.1.1) and check the status or administration page for the exact model designationAffected if The model matches one of: D3600, D6000, D6200, D7000, JR6150, PR2000, R6020, or R6050
-
Determine the installed firmware versionAccess the router web管理界面, navigate to Administration > Firmware Update or Router Status page, and record the displayed firmware version numberAffected if The firmware version cannot be determined or is not visible via the web interface
-
Compare firmware version against affected rangesMatch your installed version to the vulnerable thresholds: D3600/D6000 < 1.0.0.76, D6200 < 1.1.00.32, D7000 < 1.0.1.68, JR6150/R6050 < 1.0.1.18, PR2000 < 1.0.0.28, R6020 < 1.0.0.38Affected if Your installed version is lower than the threshold for your specific model
-
Verify web management interface accessibilityConfirm whether the router web管理界面 is accessible from the network by attempting to reach the router IP from an external host or checking remote management settings under Administration > Remote ManagementAffected if The web management interface is exposed to untrusted networks or the internet
You are affected if your router model is one of the listed models AND your firmware version is below the specified threshold AND the web management interface is accessible from an untrusted network.
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.281.0.0.381.0.0.76
Apply vendor-supplied firmware updates to all affected devices: D3600 to 1.0.0.76, D6000 to 1.0.0.76, D6200 to 1.1.00.32, D7000 to 1.0.1.68, JR6150/PR2000/R6050/R6080 to 1.0.1.18/1.0.0.28/1.0.1.18/1.0.0.38 respectively, R6020/R6120/R6260 to 1.0.0.38/1.0.0.46/1.1.0.40, R6220 to 1.1.0.80, R6700v2/R6800/R6900v2 to 1.2.0.36, WNR2020 to 1.1.0.62, and XR500 to 2.3.2.32. If patching is not feasible, restrict management interface access to trusted networks or disable remote administration.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20682 — 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-20682 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