CVE-2023-41198
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 StaticDNS1 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-18818.
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 allowing unauthenticated network-adjacent attackers to execute arbitrary code as root. The flaw exists in the HNAP1 SOAP endpoint's SetHostIPv6StaticSettings function where the StaticDNS1 parameter is not validated before being used in a system call.
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 modelCheck the device label or access the router web interface and look for the model number DAP-1325 in the system information or status pageAffected if The device is not a D-Link DAP-1325 router, then it is not affected by this specific CVE
-
Check the firmware versionAccess the router web interface, typically at 192.168.0.1, and navigate to Status or System Info page to find the firmware version. Alternatively, check the download file name or release notes if you have access to the firmware fileAffected if The firmware version is 1.09b03 or higher, then it is not vulnerable; versions below 1.09b03 are affected
-
Verify HNAP1 SOAP service is accessibleAttempt to access the HNAP1 endpoint on the router, typically at http://<router-ip>/HNAP1/ or check if port 80/443 responds to HNAP1 SOAP requestsAffected if The HNAP1 endpoint is not exposed or not responding, the attack surface may be reduced but the vulnerability still exists in the firmware if version is below 1.09b03
-
Check network accessibility of management interfaceDetermine if the router web interface is accessible from the network segment where potential attackers would be. Try accessing the router from a non-trusted network or verify ACLs/firewall rulesAffected if The management interface is exposed to untrusted network segments, an adjacent attacker could reach the vulnerable HNAP1 endpoint
The device is affected if it is a D-Link DAP-1325 router running firmware version below 1.09b03 and the HNAP1 SOAP endpoint is accessible from the network segment where untrusted users reside.
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 if available; otherwise restrict network access to router management interface or replace the end-of-life device.
DAP-1325 firmware version 1.09b03
- 1. Identify the current firmware version of the DAP-1325 router by accessing the web management interface.
- 2. Navigate to the D-Link support page for the DAP-1325 at supportannouncement.us.dlink.com to download the fixed firmware version 1.09b03.
- 3. Access the router's admin panel (typically at 192.168.0.1 or 192.168.1.1) and locate the firmware upgrade section under Administration or Settings.
- 4. Upload and apply firmware version 1.09b03 to the device.
- 5. After the upgrade completes and the device reboots, verify the new firmware version is 1.09b03 or higher.
- 6. Confirm the vulnerability is remediated by verifying the HNAP SetHostIPv6StaticSettings function properly handles the StaticDNS1 parameter without command injection.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41198 — 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-41198 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