CVE-2019-20722
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 D7800 before 1.0.1.44, DM200 before 1.0.0.58, R7500v2 before 1.0.3.38, R7800 before 1.0.2.52, R8900 before 1.0.4.2, R9000 before 1.0.4.2, RBK20 before 2.3.0.28, RBR20 before 2.3.0.28, RBS20 before 2.3.0.28, RBK50 before 2.3.0.32, RBR50 before 2.3.0.32, RBS50 before 2.3.0.32, RBS40 before 2.3.0.28, 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 models contain a command injection vulnerability in their web management interface. An authenticated attacker can inject and execute arbitrary OS commands through insufficient input validation in certain parameters. This affects 17 different NETGEAR device models across multiple product lines.
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.1.44< 1.0.0.58< 1.0.3.38< 1.0.2.52< 1.0.4.2< 1.0.4.2< 2.3.0.28< 2.3.0.28CVSS 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 router modelLocate the model number on the device label or in the web management interface under Administration > Router InformationAffected if The model is one of: D7800, Dm200, R7500, R7800, R8900, R9000, Rbk20, or Rbr20
-
Check the installed firmware versionLog into the web management interface and navigate to Administration > Router Upgrade or Administration > Firmware Upgrade to view the current firmware versionAffected if The firmware version is below the threshold for your model: D7800 < 1.0.1.44, Dm200 < 1.0.0.58, R7500 < 1.0.3.38, R7800 < 1.0.2.52, R8900 < 1.0.4.2, R9000 < 1.0.4.2, Rbk20 < 2.3.0.28, Rbr20 < 2.3.0.28
-
Verify web management interface accessibilityDetermine if the router web interface is reachable from untrusted networks by checking NAT/firewall rules or port forwarding configurationsAffected if The web management interface (ports 80/443) is exposed to the internet or untrusted networks
-
Confirm administrative credentials are in useCheck if an administrator account is enabled on the router through the web interface under Administration > Setup > Wireless Setup or User ManagementAffected if Admin credentials are configured and the device is accessible to an attacker who could obtain those credentials
You are affected if you use one of the eight listed NETGEAR models and your firmware version is below the specified threshold for that model, combined with network exposure to the web management interface.
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.581.0.1.441.0.2.52
Apply the vendor-supplied firmware updates for each affected model. If updates are unavailable, restrict administrative interface access to trusted networks only, enforce strong administrative credentials, and monitor for unauthorized administrative sessions.
- 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-20722 — 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-20722 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