dbcve.org
Dap 1325 FirmwareOperating system · Dlink

CVE-2023-41209

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 StaticDNS1 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-18835.

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 when handling StaticDNS1 parameter in SetHostIPv6StaticSettings via HNAP1 SOAP endpoint. The vulnerability stems from insufficient length validation of user-supplied XML data before copying to a fixed-size stack buffer, allowing remote code execution as root without authentication.

MitigationApply vendor firmware patch when available; until then, isolate affected devices on restricted network segments and monitor for exploitation attempts against the HNAP1 endpoint.

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 web administration interface or check the device label/metadata to confirm the model is D-Link DAP-1325
    Affected if Device is not a D-Link DAP-1325 router (different models are not affected by this specific CVE)
  2. Check firmware version
    In the router web interface, navigate to Status or Management section and locate the firmware version information. Compare the installed version against 1.09b03
    Affected if Firmware version is less than 1.09b03 (versions 1.09b02 and earlier are vulnerable)
  3. Verify HNAP1 SOAP endpoint accessibility
    Attempt to access the HNAP1 endpoint on the router (typically at http://<router-ip>/HNAP1 or check if port 80/443 responds to HNAP1 SOAP requests)
    Affected if The HNAP1 endpoint is exposed and accepts SOAP requests - this is the attack surface required for exploitation
  4. Check IPv6 static configuration availability
    In the router web interface, look for IPv6 or network settings where static IPv6 configuration (including StaticDNS1 parameter) can be configured via the SetHostIPv6StaticSettings function
    Affected if IPv6 static settings feature is accessible - this feature must be present and configurable for the vulnerable code path to be triggered

The device is affected if it is a D-Link DAP-1325 router running firmware version below 1.09b03 and the HNAP1 interface with IPv6 static settings is accessible on 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.

dbcve · scoped
Upgrade available Upgrade to 1.09b03 or later
Fixed in 1.09b03
Interim mitigation

Apply vendor firmware patch when available; until then, isolate affected devices on restricted network segments and monitor for exploitation attempts against the HNAP1 endpoint.

Recommended fix Moderate confidence

D-Link DAP-1325 Firmware 1.09b03 or later

  1. Identify the current firmware version of the D-Link DAP-1325 device through the web management interface or physical label
  2. Navigate to the D-Link DAP-1325 web management interface (typically at 192.168.0.1)
  3. Access the firmware update section (usually under Settings > Maintenance > Firmware Upgrade)
  4. Download the latest firmware version from the official D-Link support website (support.dlink.com)
  5. Upload and apply the firmware update, ensuring power is not interrupted during the process
  6. After reboot, verify the firmware version has been updated to 1.09b03 or later
  7. Confirm the HNAP1 SOAP endpoint is no longer vulnerable by verifying the device functions normally
Caveat Standard router firmware update - backup configuration if applicable; service interruption expected during upgrade

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

Fix this in Dap 1325 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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