CVE-2023-41195
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 SetHostIPv6Settings IPv6Mode 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-18815.
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 confidenceThe D-Link DAP-1325 router contains a command injection vulnerability in its HNAP1 SOAP endpoint's SetHostIPv6Settings function. The vulnerability stems from insufficient validation of user-supplied input before passing it to a system call, allowing unauthenticated attackers to execute arbitrary code with root privileges.
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-1325Affected if The device is not a D-Link DAP-1325, this specific CVE does not apply
-
Check the firmware versionLog into the router web interface and navigate to Status or Management page to view the firmware version, or use the command: `grep Version /etc/os-release` or check the file system if you have telnet/SSH accessAffected if Firmware version is less than 1.09b03 (e.g., 1.08, 1.07, etc.)
-
Verify HNAP1 SOAP endpoint accessibilityAttempt to access the HNAP1 endpoint via HTTP at the router's IP address (typically http://<router-ip>/HNAP1/)Affected if The HNAP1 SOAP endpoint is reachable from the network where the attacker is located
-
Confirm SetHostIPv6Settings function exposureSend a SOAP request to the HNAP1 endpoint with the SetHostIPv6Settings action to test if the function is exposed and accepts inputAffected if The SetHostIPv6Settings function is accessible and processes input without proper sanitization
The device is affected if it is a D-Link DAP-1325 running firmware version below 1.09b03 and the HNAP1 SOAP endpoint with SetHostIPv6Settings is accessible from the network.
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 available firmware updates from D-Link; if no patch exists, implement network segmentation to restrict access to the device or replace the affected hardware.
D-Link DAP-1325 Firmware version 1.09b03 or later
- 1. Check the current firmware version of the D-Link DAP-1325 router via the web management interface (usually at http://192.168.0.1)
- 2. Navigate to the Administration or System Settings section to view firmware version
- 3. If the firmware version is below 1.09b03, download the latest firmware (1.09b03 or later) from D-Link's official support website (supportannouncement.us.dlink.com)
- 4. In the router's web interface, go to the Firmware Upgrade section
- 5. Upload the downloaded firmware file and apply the update
- 6. Wait for the router to reboot and verify the new firmware version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41195 — 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-41195 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