CVE-2023-41204
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 · uneditedD-Link DAP-1325 SetAPLanSettings SecondaryDNS 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-18830.
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 confidenceStack-based buffer overflow in D-Link DAP-1325's HNAP1 SOAP endpoint when handling XML data in SetAPLanSettings. The vulnerability stems from insufficient length validation before copying user-supplied data to a fixed-size stack buffer, allowing network-adjacent attackers to achieve root-level code execution without authentication.
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< 1.09b03CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device's web administration interface or check the device label/menu to confirm the exact model is D-Link DAP-1325Affected if The device is not a D-Link DAP-1325 model - this vulnerability only affects that specific device
-
Check the installed firmware versionLog into the DAP-1325 web interface and navigate to the firmware/version information page, or use the device's status display to find the firmware version numberAffected if The firmware version is less than 1.09b03 (for example, 1.08 or earlier versions)
-
Verify HNAP1 SOAP service is accessibleAttempt to access the HNAP1 endpoint on the device (typically at /HNAP1/ or check if the SOAP service responds to requests on the local network)Affected if The HNAP1 SOAP endpoint is reachable from the network and responds to requests - this is the vulnerable service interface
-
Confirm network exposure of the deviceDetermine if the DAP-1325 is placed on a network segment accessible to untrusted users - check if the device management interface is exposed beyond a trusted local networkAffected if The device is network-adjacent to untrusted users (e.g., on a shared or guest network segment, or directly internet-exposed)
You are affected if you have a D-Link DAP-1325 device running firmware version 1.09b03 or lower, and the HNAP1 SOAP service is accessible from a network segment where untrusted users can reach it.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.09b03
Apply vendor firmware patch when available; otherwise segment the device on a restricted VLAN or replace the affected hardware, as the vulnerability is exploitable without credentials and provides root access.
D-Link DAP-1325 Firmware version 1.09b03 or later
- Check your D-Link DAP-1325 router's current firmware version in the administrative web interface (typically at 192.168.0.1)
- Navigate to the firmware update or administration section
- Download the latest firmware version 1.09b03 or later from D-Link's official support website (supportannouncement.us.dlink.com)
- Upload and apply the firmware update through the router's web interface
- Verify the firmware version has been updated to 1.09b03 or later after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41204 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-41204 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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