Xr500 FirmwareOperating system · Netgear

CVE-2019-20710

HIGH · 8.0 CVSS v3.1 Published 2020-04-16
Fix available
A fix is available. Upgrade to 1.0.0.76 / 2.3.2.32 or later.
See remediation →
82/100
Remediation priority · High
Zero-click

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 · unedited
Certain 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 confidence

This is an authenticated command injection vulnerability affecting NETGEAR D3600, D6000, and XR500 routers. An authenticated attacker can execute arbitrary OS commands on the underlying system through this flaw, effectively achieving privilege escalation from authenticated user to full system command execution.

MitigationUpdate router firmware to version 1.0.0.76 or later for D3600/D6000, and 2.3.2.32 or later for XR500. If immediate patching is not feasible, limit administrative access to trusted users only and monitor for suspicious activity.

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
Xr500 FirmwareOperating system
Affected:< 2.3.2.32
D3600 FirmwareOperating system
Affected:< 1.0.0.76
D6000 FirmwareOperating system
Affected:< 1.0.0.76

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Access the router admin web interface and check the device information page, or look at the device label/marketing material to confirm the model is XR500, D3600, or D6000
    Affected if Model is Netgear XR500, D3600, or D6000 and firmware version is below the fixed release
  2. Check firmware version
    In the router admin interface, navigate to Administration > Firmware Update or look under the device status/information section to find the currently installed firmware version
    Affected if Firmware version is less than 2.3.2.32 for XR500, or less than 1.0.0.76 for D3600/D6000
  3. Verify web management interface accessibility
    Check if the router web admin interface is accessible from the WAN/internet side. This is typically found under Advanced > Admin > Remote Management or similar. Attempt to access the router login page from an external network if remote management is enabled
    Affected if Remote management is enabled and the router is directly accessible from the internet
  4. Review admin accounts for unauthorized changes
    In the router admin interface, navigate to Administration > Setup > Wireless Setup or the user account management section to review the list of configured administrator accounts
    Affected if Unexpected administrator accounts exist or account changes were made without your knowledge
  5. Monitor for unusual network activity
    Inspect connected devices and network traffic logs for any unexpected devices or unusual outbound connections originating from the router, which could indicate command injection activity
    Affected if Unknown devices are connected or unusual outbound connections are observed

The device is affected if it is a Netgear XR500, D3600, or D6000 router running firmware versions below 2.3.2.32 (XR500) or below 1.0.0.76 (D3600/D6000) and the admin interface is accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.0.0.76 / 2.3.2.32 or later
Fixed in 1.0.0.762.3.2.32
Interim mitigation

Update router firmware to version 1.0.0.76 or later for D3600/D6000, and 2.3.2.32 or later for XR500. If immediate patching is not feasible, limit administrative access to trusted users only and monitor for suspicious activity.

Fix this in Xr500 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-20710 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-20710 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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