dbcve.org
Dap 1325 FirmwareOperating system · Dlink

CVE-2023-41203

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 SetAPLanSettings PrimaryDNS 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-18829.

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 SetAPLanSettings function of D-Link DAP-1325 routers. The vulnerability exists in the HNAP1 SOAP endpoint's handling of XML data for the PrimaryDNS parameter, where user-supplied data is copied to a fixed-length stack buffer without proper length validation. This allows remote, unauthenticated attackers to achieve RCE as root.

MitigationApply vendor firmware patch when available; until then, restrict network access to the router's management interface, disable HNAP if possible, and place device in isolated network segment.

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 the device model
    Check the router label or access the web interface to confirm the exact model number is D-Link DAP-1325
    Affected if Device is not a D-Link DAP-1325 unit
  2. Check the installed firmware version
    Access the router web interface (usually at 192.168.0.1) and navigate to Status or Management section to view the firmware version; alternatively, check the device label or use nmap to probe the HTTP service for version disclosure
    Affected if Firmware version is 1.09b03 or higher (versions below 1.09b03 are vulnerable)
  3. Verify HNAP1 SOAP endpoint accessibility
    Send an HTTP POST request to /HNAP1/ with a SOAPAction header pointing to SetAPLanSettings; for example: curl -X POST http://192.168.0.1/HNAP1/ -H 'SOAPAction: http://purenetworks.com/HNAP1/SetAPLanSettings' -d '<xml>test</xml>'
    Affected if HNAP1 endpoint responds with valid SOAP XML (indicates service is exposed)
  4. Confirm remote management is enabled
    In the router web interface, check under Administration or Management settings for 'Remote Management' or 'HTTP Management' - verify if it allows external access from non-local IP addresses
    Affected if Remote management is enabled and the router's WAN/Internet-facing IP can reach the HNAP1 endpoint

The device is affected if it is a D-Link DAP-1325 running firmware version below 1.09b03 and the HNAP1 SOAP endpoint is network-accessible (especially from external networks).

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, restrict network access to the router's management interface, disable HNAP if possible, and place device in isolated network segment.

Recommended fix Moderate confidence

D-Link DAP-1325 Firmware 1.09b03 or later

  1. 1. Access the D-Link DAP-1325 router web management interface
  2. 2. Navigate to the firmware update or system settings section
  3. 3. Check the current firmware version under status or management settings
  4. 4. If the firmware version is earlier than 1.09b03, download the latest firmware from the official D-Link support website
  5. 5. Upload and apply the firmware update following the on-screen instructions
  6. 6. After the router reboots, verify the new firmware version is 1.09b03 or later
Caveat Firmware updates may temporarily disrupt network connectivity; ensure stable power during the update process

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

Fix this in Dap 1325 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA2.0 h
26.0 hours of engineering $4,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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