CVE-2019-20680
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 D7000v2 before 1.0.0.53, R6220 before 1.1.0.80, R6260 before 1.1.0.64, R6700 before 1.0.2.6, R6700v2 before 1.2.0.36, R6800 before 1.2.0.36, R6900 before 1.0.2.4, R6900P before 1.3.1.64, R6900v2 before 1.2.0.36, R7000 before 1.0.9.60, R7000P before 1.3.1.64, R7800 before 1.0.2.60, R7900 before 1.0.3.8, R7900P before 1.4.1.30, R8000 before 1.0.4.46, R8000P before 1.4.1.30, R8300 before 1.0.2.128, R8500 before 1.0.2.128, R8900 before 1.0.4.12, R9000 before 1.0.4.12, 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 models contain a command injection vulnerability allowing authenticated users to execute arbitrary OS commands through the web management interface. User-supplied input is not properly sanitized before being passed to system shell commands.
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.53< 1.1.0.80< 1.1.0.64< 1.0.2.6< 1.2.0.36< 1.2.0.36< 1.0.2.4< 1.2.0.36< 1.3.1.64< 1.0.9.60CVSS 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 your NETGEAR router modelCheck the device label on the router or log into the web management interface to view the model number displayed on the admin pageAffected if The model number matches D7000, R6220, R6260, R6700, R6800, R6900, R6900p, or R7000
-
Determine the installed firmware versionLog into the router web management interface and navigate to the Administration or Firmware Update section to view the current firmware version, or check the version shown on the admin login pageAffected if The firmware version is below 1.0.0.53 (D7000), 1.1.0.80 (R6220), 1.1.0.64 (R6260), 1.0.2.6 or 1.2.0.36 (R6700), 1.2.0.36 (R6800), 1.0.2.4 or 1.2.0.36 (R6900), 1.3.1.64 (R6900p), or 1.0.9.60 (R7000)
-
Verify the router web management interface is accessibleAttempt to access the router admin page at the default gateway IP address (typically 192.168.1.1) from a connected deviceAffected if The web interface responds and accepts authentication credentials, meaning the management interface is exposed on the network
-
Confirm administrative authentication is enabledCheck that the router requires a password for web management access; ensure the default admin password has not been left at factory defaultsAffected if The web management interface allows authenticated access, which is required for the command injection to be exploitable per the CVE description
You are affected if you own one of the listed NETGEAR router models AND your firmware version is below the specified threshold AND the web management interface is accessible with authentication 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.531.0.2.41.0.2.6
Update affected router firmware to the versions specified in the NETGEAR advisory. If updates are unavailable, restrict administrative access to trusted users only and consider network segmentation.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20680 — 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-20680 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