CVE-2023-41199
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 HNAP SetHostIPv6StaticSettings StaticDNS2 Command Injection 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 a request parameter provided to the HNAP1 SOAP endpoint. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-18819.
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 confidenceCommand injection vulnerability in D-Link DAP-1325 routers where the HNAP1 SOAP endpoint's SetHostIPv6StaticSettings function does not validate the StaticDNS2 parameter before using it in a system call. Attackers can inject arbitrary shell commands without authentication, executing code in root context.
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 router's web interface or check the device label to confirm it is a D-Link DAP-1325 model. Alternatively, use network scanning to identify the device via its MAC OUI or HTTP responses.Affected if The device is confirmed to be a D-Link DAP-1325 router.
-
Check the installed firmware versionLog into the router's web interface and navigate to the Status or Management section to view the firmware version. Alternatively, use the router's administration pages or SNMP to query the firmware build.Affected if The firmware version is lower than 1.09b03 (for example, 1.08, 1.07, or any version number less than 1.09b03).
-
Verify HNAP1 SOAP endpoint accessibilitySend an HTTP POST request to the /HNAP1 endpoint on the router (typically http://<router-ip>/HNAP1) with a probe request to confirm the service is responding. The vulnerability exists in the SetHostIPv6StaticSettings function.Affected if The router responds to HNAP1 SOAP requests, indicating the HNAP service is enabled and accessible.
-
Confirm IPv6 static settings configuration is availableCheck if the router's web interface includes IPv6 static address configuration options (under IPv6 or network settings). The vulnerable parameter is StaticDNS2.Affected if IPv6 static configuration is available and the router allows saving static DNS settings, meaning the SetHostIPv6StaticSettings function is present in the firmware.
If the device is a D-Link DAP-1325 with firmware version below 1.09b03 and the HNAP1 service is accessible, the device is affected by this command injection vulnerability.
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; if no patch exists, disable HNAP services or replace the affected device. Network segmentation can limit exposure to adjacent attackers.
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's web management interface
- 2. Navigate to the Administration or Settings section to locate the firmware version information
- 3. Download the latest firmware version 1.09b03 or later from the official D-Link support website (supportannouncement.us.dlink.com)
- 4. Access the router's web management interface and navigate to the firmware upgrade section
- 5. Upload the downloaded firmware file and initiate the upgrade process
- 6. Wait for the upgrade to complete and the device to reboot
- 7. After reboot, verify the new firmware version is installed and test that network functionality is working properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41199 — 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-41199 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