CVE-2019-20708
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 command injection by an authenticated user. This affects D3600 before 1.0.0.76, D6000 before 1.0.0.76, 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 confidenceCommand injection vulnerability in NETGEAR router web interfaces (D3600, D6000, XR500) allows authenticated users to execute arbitrary OS commands via unsanitized input passed to system shell. The vulnerability exists in firmware versions prior to 1.0.0.76 (D3600/D6000) and 2.3.2.32 (XR500).
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< 2.3.2.32< 1.0.0.76< 1.0.0.76CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 modelLocate the model number on the router physical label or log into the router web interface and check the status or dashboard page for the model designation (D3600, D6000, or XR500)Affected if Router model is D3600, D6000, or XR500
-
Locate firmware version in web interfaceLog into the router administration panel (typically at 192.168.1.1 or 192.168.0.1), navigate to the Router Status, Administration, or Firmware Upgrade page, and record the displayed firmware version numberAffected if Model is one of the affected devices and version is displayed
-
Compare version against thresholdsCompare the installed firmware version to the affected ranges: for D3600/D6000 versions below 1.0.0.76 are vulnerable; for XR500 versions below 2.3.2.32 are vulnerableAffected if Installed version is less than 1.0.0.76 on D3600/D6000, or less than 2.3.2.32 on XR500
-
Verify remote management status (optional context)Check the router web interface under Remote Management or Access Control settings to see if remote web management is enabledAffected if Remote management is enabled and the router is internet-accessible, increasing exposure to potential attackers
A user is affected if they have a D3600, D6000, or XR500 router running firmware version lower than 1.0.0.76 (D3600/D6000) or 2.3.2.32 (XR500) with the web management interface accessible.
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.762.3.2.32
Apply vendor-supplied firmware updates: upgrade D3600/D6000 to version 1.0.0.76 or later, and XR500 to version 2.3.2.32 or later. Restrict web management interface access to trusted networks or disable remote management if unnecessary.
- 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-20708 — 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-20708 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