dbcve.org
Dap 1325 FirmwareOperating system · Dlink

CVE-2023-41210

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.09b03 or later.
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-1325 SetHostIPv6StaticSettings StaticDNS2 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-1325 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of XML data provided to the HNAP1 SOAP endpoint. 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-18836.

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

Stack-based buffer overflow in D-Link DAP-1325 routers in the HNAP1 SOAP endpoint's SetHostIPv6StaticSettings action. The StaticDNS2 XML parameter lacks length validation before copying user-supplied data to a fixed-size stack buffer, allowing remote code execution as root without authentication.

MitigationNetwork-segment the affected device behind a firewall to limit exposure; apply vendor firmware updates when available; if unsupported, replace the device.

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 1325 FirmwareOperating system
Affected:< 1.09b03

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.1/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. Confirm device model is D-Link DAP-1325
    Access the router web interface and check the status/model page, or look for the model label on the physical device
    Affected if The device is a D-Link DAP-1325 router
  2. Check firmware version
    Log into the router web interface and navigate to the firmware or status page to view the installed firmware version; compare against 1.09b03
    Affected if The firmware version is below 1.09b03 (e.g., 1.08, 1.07, etc.)
  3. Verify HNAP1 SOAP service is accessible
    Attempt to access the HNAP1 endpoint (typically http://<router-ip>/HNAP1 or check if port 80/443 is open and responds to SOAP requests)
    Affected if The HNAP1 service is exposed and accepting requests on the network
  4. Check if IPv6 settings feature is enabled
    Navigate to the router's IPv6 or network settings page and verify whether static IPv6 configuration options are accessible or enabled
    Affected if The SetHostIPv6StaticSettings action can be invoked through the web interface or API

You are affected if you have a D-Link DAP-1325 router running firmware version prior to 1.09b03 with the HNAP1 service accessible on your network and IPv6 static settings feature available.

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 1.09b03 or later
Fixed in 1.09b03
Interim mitigation

Network-segment the affected device behind a firewall to limit exposure; apply vendor firmware updates when available; if unsupported, replace the device.

Recommended fix Moderate confidence

D-Link DAP-1325 Firmware version 1.09b03 or later

  1. 1. Download the firmware version 1.09b03 or later from the official D-Link support website (support.dlink.com)
  2. 2. Ensure you have a stable power connection to the DAP-1325 router during the upgrade process
  3. 3. Access the router's web management interface through its IP address
  4. 4. Navigate to the Administration or Management section
  5. 5. Locate the Firmware Upgrade or Update option
  6. 6. Upload the downloaded firmware file (.bin or .img)
  7. 7. Wait for the upload to complete and for the router to reboot automatically
  8. 8. After reboot, verify the firmware version in the router's status page to confirm the update was successful
Caveat Firmware upgrades can sometimes reset configuration to defaults; back up current settings before upgrading if possible

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

Fix this in Dap 1325 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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