dbcve.org
Dap 1325 FirmwareOperating system · Dlink

CVE-2023-41207

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 StaticAddress 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-18833.

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 the SetHostIPv6StaticSettings function of the D-Link DAP-1325 router's HNAP1 SOAP endpoint. The vulnerability stems from insufficient length validation on XML data before copying to a fixed-size stack buffer, enabling remote code execution as root without authentication.

MitigationApply vendor firmware update if available; otherwise restrict network access to the device, disable WAN management interfaces, and consider replacing the EOL 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. Identify device model
    Access the router's web interface or check the device label to confirm the model is D-Link DAP-1325
    Affected if Device is not a D-Link DAP-1325 (different models are not affected)
  2. Check firmware version
    Log into the router web interface and navigate to Status or Management page to view the firmware version, or use the command 'cat /proc/version' via telnet/SSH if available
    Affected if Firmware version is earlier than 1.09b03 (versions 1.09b03 and later are patched)
  3. Verify HNAP1 SOAP endpoint availability
    Attempt to access http://[router-ip]/HNAP1/ or check if port 80/443 responds to HNAP1 SOAP requests
    Affected if HNAP1 endpoint returns a valid response (this is the attack surface for the vulnerability)
  4. Confirm remote management exposure
    Check router firewall settings or WAN management configuration to determine if the web interface is accessible from the WAN/internet side
    Affected if WAN management or remote administration is enabled, allowing unauthenticated attackers from the internet to reach the HNAP1 endpoint

The device is affected if it is a D-Link DAP-1325 running firmware version earlier than 1.09b03 and the HNAP1 endpoint is exposed (especially if WAN-accessible), since exploitation requires reaching the SOAP endpoint without authentication.

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

Apply vendor firmware update if available; otherwise restrict network access to the device, disable WAN management interfaces, and consider replacing the EOL device.

Recommended fix High confidence

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

  1. 1. Visit D-Link's official support page for the DAP-1325 router at support.dlink.com
  2. 2. Download the latest firmware version (1.09b03 or later) - ensure it is obtained directly from D-Link
  3. 3. Access the DAP-1325 web management interface via a browser at the router's local IP address
  4. 4. Navigate to the Administration or Management section of the web interface
  5. 5. Locate the Firmware Upgrade or Update option
  6. 6. Upload the downloaded firmware file and initiate the upgrade process
  7. 7. Wait for the router to complete the firmware update and reboot
  8. 8. After reboot, verify the firmware version in the router's status page to confirm the update was successful
Caveat firmware upgrades may reset router configuration to defaults; backup current settings before upgrading if needed

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,610
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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