CVE Tools

CVE-2024-23625

D-Link DAP-1650 SUBSCRIBE Callback Command Injection Vulnerability

No known exploitation. EPSS puts it in the 94th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • D-Link DAP-1650Affected: ≤ 1.04B01Upgrade to: after 1.04B01Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether you own or use a D-Link DAP-1650 range extender/access point anywhere on your network.
  2. If found, disconnect it from the internet-facing side or place it behind a firewall so it cannot receive traffic from untrusted networks.
  3. Disable UPnP on the device if that option exists in its settings.
  4. Check for a firmware update on D-Link's support site; no fixed version has been published yet, so continue monitoring for one.
  5. If the device cannot be isolated or updated, plan to retire and replace it with a supported model.

What it is

From the CVE record

A command injection vulnerability exists in D-Link DAP-1650 devices when handling UPnP SUBSCRIBE messages. An unauthenticated attacker can exploit this vulnerability to gain command execution on the device as root.

In plain language

Written by AI from the record

A serious flaw in the D-Link DAP-1650 Wi-Fi device lets an attacker on your network take full control of it without a password, and no official fix exists yet, so you should isolate or replace the device rather than wait for a patch.

Unauthenticated OS command injection (CWE-77) in the D-Link DAP-1650's UPnP SUBSCRIBE callback handler allows root-level arbitrary command execution from the adjacent network, with no vendor patch currently available.

If you're affected

  • Full device takeover
  • Network pivot point for attackers
  • Operational disruption
  • Router used as foothold for further attacks

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS94th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

7.3% chance of exploitation activity in the next 30 days, which ranks it in the 94th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 987 days, from the signal feeds we watch.

  1. EPSS band changemoderate → 0epss band change
  2. OpenVAS check added
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Scored 9.6 by NVD.

How it is reached

  • Attack Vector AdjacentRequires access to the local network (e.g. same Wi-Fi, Bluetooth)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for DAP-1650, not every advisory.