CVE-2019-20689
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 D6000 before 1.0.0.75, D6100 before 1.0.0.63, EX2700 before 1.0.1.48, EX6100v2 before 1.0.1.76, EX6150v2 before 1.0.1.76, EX6200v2 before 1.0.1.72, EX6400 before 1.0.2.136, EX7300 before 1.0.2.136, EX8000 before 1.0.1.180, R7800 before 1.0.2.52, R8900 before 1.0.4.2, R9000 before 1.0.4.2, WN2000RPTv3 before 1.0.1.32, WN3000RPv2 before 1.0.0.68, WN3100RPv2 before 1.0.0.60, WNDR3700v4 before 1.0.2.102, WNDR4300v1 before 1.0.2.104, WNDR4300v2 before 1.0.0.58, WNDR4500v3 before 1.0.0.58, WNR2000v5 before 1.0.0.68, 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 confidenceMultiple NETGEAR router and range extender models contain an authenticated command injection vulnerability in their web management interface. An attacker with valid credentials can execute arbitrary operating system commands by injecting shell metacharacters into input fields, 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< 1.0.0.75< 1.0.0.63< 1.0.1.48< 1.0.1.76< 1.0.1.76< 1.0.1.72< 1.0.2.136< 1.0.2.136CVSS 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 your NETGEAR device modelLocate the device label on the router or range extender itself, or log into the web management interface and check the status or device information page for the exact model number (e.g., D6000, Ex2700, Ex6400)Affected if The model matches one of the affected products: D6000, D6100, Ex2700, Ex6100, Ex6150, Ex6200, Ex6400, or Ex7300
-
Check the installed firmware versionLog into the web management interface (typically at 192.168.1.1 or 192.168.1.250), navigate to the Administration or Router Status section, and locate the firmware version displayedAffected if The firmware version is lower than the specified threshold for your model: D6000 < 1.0.0.75, D6100 < 1.0.0.63, Ex2700 < 1.0.1.48, Ex6100 < 1.0.1.76, Ex6150 < 1.0.1.76, Ex6200 < 1.0.1.72, Ex6400 < 1.0.2.136, Ex7300 < 1.0.2.136
-
Verify the web management interface is accessibleAttempt to access the router web interface from a browser on a device connected to the network. Confirm the login page loads successfully.Affected if The web management interface is reachable from network devices
-
Check if remote administration is enabledIn the web management interface, navigate to the Administration or Remote Management settings and determine whether remote access via WAN/internet is permittedAffected if Remote administration is enabled, exposing the interface beyond the local network
You are affected if your device model is on the affected list AND your current firmware version is below the specified threshold AND the web management interface is accessible, with remote administration enabled presenting the highest risk.
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.631.0.0.751.0.1.48
Update affected devices to the firmware versions specified in the advisory. If updates are unavailable, restrict web management interface access to trusted networks or disable remote administration.
- 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-20689 — 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-20689 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