CVE-2019-20703
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 confidenceAuthenticated command injection vulnerability in NETGEAR D3600, D6000, and XR500 routers. An attacker with valid credentials can inject arbitrary OS commands through the web management interface due to insufficient input validation, potentially leading to complete 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< 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 modelLog into the router web management interface and navigate to the Administration or Settings section to confirm the exact model number (D3600, D6000, or XR500).Affected if The router model is D3600, D6000, or XR500.
-
Check installed firmware versionIn the router web interface, go to Administration > Firmware Update or similar section to view the current firmware version. Alternatively, check the status or overview page.Affected if The firmware version is below 1.0.0.76 for D3600/D6000, or below 2.3.2.32 for XR500.
-
Verify web management interface statusAttempt to access the router login page via HTTP/HTTPS from the network segment in question, or check in the router settings under Administration > Web Management or Remote Management.Affected if The web management interface is enabled and accessible.
-
Check remote administration settingsIn the router interface, look for Remote Management, Remote Access, or WAN Access settings under Administration. Determine if remote administration is permitted from external networks.Affected if Remote administration is enabled, allowing access from outside the local network.
-
Assess credential exposureDetermine if default administrative credentials are still in use or if credentials may have been compromised. Check if strong, unique passwords are configured.Affected if Default credentials are in use or credentials may be known to untrusted parties, enabling authenticated exploitation.
A user is affected if they own a D3600, D6000, or XR500 router with firmware below the specified version thresholds AND the web management interface is accessible with valid 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.762.3.2.32
Update router firmware to version 1.0.0.76 or later for D3600/D6000, or 2.3.2.32 or later for XR500. If updates are unavailable, restrict web management access to trusted networks or disable remote administration.
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20703 — 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-20703 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