CVE-2019-20709
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 confidenceNETGEAR D3600, D6000, and XR500 routers contain an authenticated command injection vulnerability. An attacker with valid administrative credentials can execute arbitrary operating system commands on the affected devices through improper input validation in the web management interface.
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 modelAccess the router web management interface and check the device information page, or look at the physical device label to confirm the exact model number (XR500, D3600, or D6000)Affected if The model is Netgear XR500, D3600, or D6000
-
Check installed firmware versionLog into the web management interface and navigate to the firmware version or status page. Compare the displayed firmware version against the affected ranges: XR500 < 2.3.2.32, D3600 < 1.0.0.76, D6000 < 1.0.0.76Affected if The firmware version is lower than the respective threshold for your model
-
Verify web management interface exposureDetermine if the router web management interface (HTTP/HTTPS on ports 80 or 443) is accessible from outside your trusted internal network, such as from the internet or an untrusted VLANAffected if The administrative web interface is accessible from untrusted networks without firewall protection
-
Confirm administrative access controlReview whether the router administration password has been changed from default values and whether access is restricted to specific IP addresses if such controls are available in the router settingsAffected if Default administrative credentials remain in use or administrative access is not restricted to trusted users only
You are affected if your router is an XR500, D3600, or D6000 model running firmware below 2.3.2.32 (XR500) or below 1.0.0.76 (D3600/D6000), especially if the web management interface is exposed to untrusted networks.
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 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 administrative interface access to trusted networks only and change default credentials.
- Consultation4.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20709 — 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-20709 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