dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Apr 2022.
Dir 610 FirmwareOperating system · Dlink

CVE-2020-9377

HIGH · 8.8 CVSS v3.1 Published 2020-07-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit Remotely reachable Zero-click Patch available

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
D-Link DIR-610 devices allow Remote Command Execution via the cmd parameter to command.php. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

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

The D-Link DIR-610 router contains a command injection vulnerability in command.php where the cmd parameter is not properly sanitized, allowing remote attackers to execute arbitrary operating system commands on the device.

MitigationSince the product is end-of-life and unsupported, apply network-based mitigations such as placing the device behind a firewall, restricting access to the management interface, or replace with a currently supported router model.

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
Dir 610 FirmwareOperating system
Affected:all versions

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 the device model
    Access the router's web interface or check the device label/marketing to confirm it is a D-Link DIR-610 model
    Affected if The device is a D-Link DIR-610
  2. Check the firmware version
    Log into the router web interface and navigate to the Status or Firmware Upgrade page to view the installed firmware version, or use nmap or curl to access the web page source for version information
    Affected if Any firmware version is installed (the CVE states all versions are affected)
  3. Confirm web management interface is accessible
    Attempt to access the router's web interface on the typical HTTP ports (80, 8080) via browser or curl from an internal network location
    Affected if The web management interface is reachable on the network
  4. Verify command.php endpoint exists
    Send an HTTP GET request to http://[router-ip]/command.php and check for a valid HTTP response (200 or similar)
    Affected if The command.php file responds, indicating the vulnerable script is present
  5. Test for command injection (optional)
    Send a crafted HTTP request to command.php with a test payload in the cmd parameter, such as cmd=test or cmd=;ls, and observe the response for evidence of command execution
    Affected if The cmd parameter reflects input in the response or executes system commands

If the device is a D-Link DIR-610 with any firmware version and its web management interface with command.php is accessible, the environment is affected by CVE-2020-9377.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch gist.github.com →
Interim mitigation

Since the product is end-of-life and unsupported, apply network-based mitigations such as placing the device behind a firewall, restricting access to the management interface, or replace with a currently supported router model.

Recommended fix High confidence

Replace with a currently-supported router (D-Link or other vendor) that receives security updates

  1. This vulnerability affects the D-Link DIR-610 router, which is end-of-life and no longer supported by D-Link.
  2. No official firmware updates or security patches are available for this device.
  3. Replace the affected D-Link DIR-610 device with a currently-supported router model that receives regular security updates.
  4. If replacement is not immediately possible, place the device in a restricted network segment to limit exposure to untrusted networks.
  5. Disable any remote management interfaces if not required, and restrict administrative access to trusted IP addresses only.
Caveat The DIR-610 is end-of-life with no security support; replacement is the only reliable remediation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 610 Firmware Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-9377 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2020-9377 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