CVE-2024-23625
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 · uneditedA 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.
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 confidenceA command injection vulnerability exists in D-Link DAP-1650 devices in the UPnP SUBSCRIBE message handling functionality. An unauthenticated attacker can send specially crafted UPnP SUBSCRIBE messages containing shell metacharacters to execute arbitrary commands on the device with root privileges.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm D-Link DAP-1650 device presenceIdentify D-Link DAP-1650 units on your network by checking device hostname, MAC address prefix (e.g., 1C:AF:F7 for D-Link), or via network scan of model information. Access the device web interface at its LAN IP address and verify the model number in the status or management page.Affected if The device model is D-Link DAP-1650 and it is deployed on the network.
-
Verify UPnP is enabledLog into the DAP-1650 web interface (typically at 192.168.0.1 or via DHCP-assigned IP). Navigate to Settings > UPnP or Advanced > UPnP settings. Check if the UPnP enable/checkbox is selected or if UPnP status shows as enabled.Affected if UPnP functionality is turned on in the device configuration.
-
Check UPnP service accessibilityFrom a network-connected host, scan the DAP-1650 IP for open UPnP ports. UPnP typically uses port 1900 (UDP) for SSDP and may use HTTP ports for SOAP requests. Use a command such as: nmap -sU -p 1900 <device-ip> or nmap -p 5000,1900 <device-ip> to identify accessible UPnP endpoints.Affected if The UPnP service port (1900/UDP or associated HTTP ports) is open and reachable from an untrusted network segment.
-
Inspect UPnP subscription configurationIf the UPnP service is running, attempt to interact with it by querying the UPnP device description. Use a tool like upnp-inspector or manually send a M-SEARCH request to the device IP on port 1900 to confirm the UPnP SUBSCRIBE functionality is operational.Affected if The device responds to UPnP discovery requests and exposes subscription-capable services.
If you have a D-Link DAP-1650 device with UPnP enabled and the UPnP service is network-accessible, your environment is affected by this vulnerability.
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 dataDisable UPnP functionality on the DAP-1650 if not required, or restrict network access to the UPnP service. Network segmentation can limit exposure; contact D-Link for firmware updates.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23625 — 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-2024-23625 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