CVE-2023-44405
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 get_value_of_key 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-18824.
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 confidenceA stack-based buffer overflow vulnerability exists in the HNAP1 SOAP endpoint of D-Link DAP-1325 routers. The flaw allows remote attackers to execute arbitrary code as root by sending specially crafted XML data without proper length validation before copying to a fixed-size stack buffer. No authentication is required for exploitation.
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 DAP-1325 device on your networkAccess the router web administration interface (typically at http://192.168.0.1 or the IP assigned by your DHCP server). Look for the device model name displayed on the login page or status/dashboard page.Affected if The device is not a D-Link DAP-1325, then this CVE does not apply.
-
Check the installed firmware versionIn the router web admin interface, navigate to the Status, Maintenance, or System Information page. Locate the firmware version field. Compare the version number to 1.09b03.Affected if The displayed firmware version is less than 1.09b03 (for example, 1.08, 1.07, etc.), indicating the device is in the affected version range.
-
Verify the HNAP1 SOAP endpoint is reachableFrom a computer on the same network as the router, attempt to access the HNAP1 endpoint using a web browser or curl command: curl http://<router-ip>/HNAP1/ or curl http://<router-ip>/HNAP1. Examine the response.Affected if The HNAP1 endpoint responds with any content (including XML, SOAP fault, or redirect), confirming the service is enabled and reachable.
-
Assess network exposure of the management interfaceDetermine if the router web interface (port 80/HTTP and possibly 443/HTTPS) is accessible from outside your local network. Check router port forwarding rules, firewall settings, or perform an external port scan against your public IP on ports 80 and 443.Affected if The router management interface (including HNAP1) is exposed directly to the internet or an untrusted network, making it remotely exploitable without authentication.
A user is affected if they own a D-Link DAP-1325 router running firmware version prior to 1.09b03, the HNAP1 endpoint is active, and the device is accessible to potential attackers (especially if exposed to the internet).
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
Replace the DAP-1325 router with a currently supported model, as D-Link may not provide firmware updates for this older device. If replacement is not immediately possible, restrict network access to the device's management interface to minimize exposure.
DAP-1325 firmware version 1.09b03 or later
- 1. Identify the current firmware version of the D-Link DAP-1325 device by accessing the router web interface or checking the device administration page.
- 2. Navigate to the firmware update section in the router's web-based management interface (typically found under Administration > Firmware Upgrade or Settings > Maintenance).
- 3. Download the latest firmware version from the official D-Link support website for the DAP-1325 model.
- 4. Upload the firmware file through the router's web interface and allow the device to complete the update process.
- 5. After the router restarts, verify the new firmware version is installed and confirm it is version 1.09b03 or later.
- 6. Test that router functionality (wireless, wired connections, repeater mode) operates normally after the update.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44405 — 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-44405 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