CVE-2019-20659
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 R6400v2 before 1.0.4.84, R6700 before 1.0.2.8, R6700v3 before 1.0.4.84, R6900 before 1.0.2.8, and R7900 before 1.0.3.10.
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 firmware (R6400v2, R6700, R6700v3, R6900, R7900) allows authenticated users to execute arbitrary OS commands through 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< 1.0.4.84< 1.0.2.8< 1.0.4.84< 1.0.2.8< 1.0.3.10CVSS 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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 router modelCheck the device label on the router or log into the web management interface and look at the status or administration page to confirm the exact model number (R6400v2, R6700, R6700v3, R6900, or R7900)Affected if The model is one of the affected models listed in the CVE (R6400v2, R6700, R6700v3, R6900, R7900)
-
Check firmware versionLog into the web management interface, navigate to the Administration or Firmware Update section, and note the displayed firmware version numberAffected if The installed firmware version is below 1.0.4.84 for R6400v2/R6700v3, below 1.0.2.8 for R6700/R6900, or below 1.0.3.10 for R7900
-
Verify web management interface accessibilityAttempt to access the router web interface from an external IP address or check router firewall/NAT settings to determine if the management interface (HTTP/HTTPS on ports 80/443) is exposed to the internetAffected if The web management interface is accessible from untrusted networks (internet-facing)
-
Review admin accounts for unauthorized usersLog into the web management interface and check the Administration or Users section to list all configured admin accountsAffected if Unexpected or unknown admin accounts exist beyond those created by the legitimate administrator
The environment is affected if the router model is one of the affected models (R6400v2, R6700, R6700v3, R6900, R7900) AND the firmware version is below the patched version for that model, AND the web interface is accessible to untrusted users.
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.2.81.0.3.101.0.4.84
Update router firmware to patched versions: R6400v2/R6700v3 to 1.0.4.84+, R6700/R6900 to 1.0.2.8+, R7900 to 1.0.3.10+. Restrict admin access to trusted users and monitor for unauthorized access.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20659 — 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-20659 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