Dap 2622 FirmwareOperating system · Dlink

CVE-2023-35718

HIGH · 8.8 CVSS v3.0 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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
D-Link DAP-2622 DDP Change ID Password Auth Password Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of D-Link DAP-2622 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the DDP service. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. . Was ZDI-CAN-20061.

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

A stack-based buffer overflow in the DDP service of D-Link DAP-2622 routers allows network-adjacent attackers to execute arbitrary code as root without authentication, due to insufficient length validation on user-supplied data before copying to a fixed-size stack buffer.

MitigationRestrict network access to the DDP service (UDP port 5870) or disable it if possible until an official firmware patch is available from D-Link.

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
Dap 2622 FirmwareOperating system
Affected:= 1.00

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

CVSS:3.0/AV:A/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 the device model
    Access the router web interface or check the device label to confirm the model is D-Link DAP-2622
    Affected if The device is not a D-Link DAP-2622 router, then this CVE does not apply
  2. Check the firmware version
    Log into the router web interface and navigate to Status or System Info section to view the firmware version, or use the command 'cat /proc/version' or 'nvram get firmver' via telnet/SSH if available
    Affected if The firmware version is 1.00, then this specific version is affected by the vulnerability
  3. Verify the DDP service is enabled
    Check if UDP port 5870 is listening by running 'netstat -uan | grep 5870' or 'ss -uan | grep 5870' on the router via telnet/SSH, or scan the router from the network using 'nmap -sU -p 5870 <router_ip>'
    Affected if UDP port 5870 is open and the DDP service is running, then the vulnerable service is exposed
  4. Confirm network accessibility to the DDP port
    From a network-adjacent host, attempt to reach the DDP service with 'nc -u <router_ip> 5870' or send a UDP packet to confirm the service responds
    Affected if The DDP service (UDP 5870) is reachable from the network, then an attacker could exploit the buffer overflow

A user is affected if they have a D-Link DAP-2622 router running firmware version 1.00 with the DDP service (UDP port 5870) enabled and accessible from the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the DDP service (UDP port 5870) or disable it if possible until an official firmware patch is available from D-Link.

Fix this in Dap 2622 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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