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 20 Jul 2023.
Dir 859 FirmwareOperating system · Dlink

CVE-2019-17621

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-30
Fix available
A fix is available. Upgrade to after 3.12b04 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges 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
The UPnP endpoint URL /gena.cgi in the D-Link DIR-859 Wi-Fi router 1.05 and 1.06B01 Beta01 allows an Unauthenticated remote attacker to execute system commands as root, by sending a specially crafted HTTP SUBSCRIBE request to the UPnP service when connecting to the local network.

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

Unauthenticated command injection vulnerability in the UPnP service (gena.cgi) on D-Link DIR-859 routers versions 1.05 and 1.06B01 Beta01. An attacker on the local network can send a specially crafted HTTP SUBSCRIBE request to /gena.cgi, leading to arbitrary command execution with root privileges.

MitigationApply vendor firmware update if available. If no patch exists, disable UPnP functionality on the router or replace the device. Restrict network access to trusted users to reduce attack surface.

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 859 FirmwareOperating system
Affected:<= 1.05b03= 1.06b01
Dir 822 FirmwareOperating system
Affected:<= 2.03b01<= 3.12b04
Dir 823 FirmwareOperating system
Affected:<= 1.00b06= 1.00b06
Dir 865l FirmwareOperating system
Affected:<= 1.07b01
Dir 868l FirmwareOperating system
Affected:<= 1.12b04<= 2.05b02
Dir 869 FirmwareOperating system
Affected:<= 1.03b02= 1.03b02
Dir 880l FirmwareOperating system
Affected:<= 1.08b04
Dir 890l FirmwareOperating system
Affected:<= 1.11b01= 1.11b01

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

CVSS:3.1/AV:N/AC:L/PR:N/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 your D-Link router model
    Check the device label on the router or log into the web management interface to confirm the exact model number (e.g., DIR-859, DIR-822, DIR-823, etc.)
    Affected if The router is any of the following models: DIR-859, DIR-822, DIR-823, DIR-865L, DIR-868L, DIR-869, DIR-880L, or DIR-890L
  2. Check your installed firmware version
    Log into the router web interface and navigate to the Status or Management page to view the firmware version; alternatively, check the firmware file name if you have shell access
    Affected if The firmware version falls within or matches the affected ranges: DIR-859 <= 1.05b03 or = 1.06b01; DIR-822 <= 2.03b01 or <= 3.12b04; DIR-823 <= 1.00b06 or = 1.00b06; DIR-865L <= 1.07b01; DIR-868L <= 1.12b04 or <= 2.05b02; DIR-869 <= 1.03b02 or = 1.03b02; DIR-880L <= 1.08b04; DIR-890L <= 1.11b01 or =
  3. Verify if UPnP service is enabled
    Log into the router web interface and navigate to Advanced or NAT settings to check if Universal Plug and Play (UPnP) is turned on
    Affected if UPnP is enabled on the router (the vulnerability exists in the UPnP service's /gena.cgi endpoint)

You are affected if you have a D-Link DIR series router matching one of the affected models, your firmware version is within or matches the listed affected versions, AND UPnP is currently enabled on the device.

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
Upgrade available Upgrade to a release after 3.12b04
Vendor patch supportannouncement.us.dlink.com →
Interim mitigation

Apply vendor firmware update if available. If no patch exists, disable UPnP functionality on the router or replace the device. Restrict network access to trusted users to reduce attack surface.

Recommended fix Moderate confidence

Latest firmware version available from D-Link support for the specific model (check support.dlink.com for your model)

  1. 1. Identify the exact model number and current firmware version of the D-Link router from the affected product list (DIR-859, DIR-822, DIR-823, DIR-865L, DIR-868L, DIR-869, DIR-880L, or DIR-890L).
  2. 2. Visit the official D-Link support website at support.dlink.com or www.dlink.com to search for firmware updates.
  3. 3. Locate the firmware download section for the specific router model.
  4. 4. Download the latest firmware version available from D-Link's official support page.
  5. 5. Access the router's web management interface (typically at 192.168.0.1 or 192.168.1.1).
  6. 6. Navigate to the Administration or System section of the router settings.
  7. 7. Locate the Firmware Upgrade or Update option.
  8. 8. Upload and apply the downloaded firmware file.
Caveat Firmware updates may reset router configuration to defaults; back up settings before upgrading if possible

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

Fix this in Dir 859 Firmware Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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