CVE-2023-41190
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 SetAPLanSettings IPAddr 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-18810.
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 confidenceUnauthenticated command injection in D-Link DAP-1325 routers via the HNAP1 SOAP endpoint. The SetAPLanSettings function fails to validate user-supplied IPAddr parameter before passing it to a system call, allowing attackers to execute arbitrary commands as root 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.
-
Confirm device modelAccess the router's web management interface and check the device information page, or check the device label for the model number DAP-1325Affected if The device is not a D-Link DAP-1325 router, then this specific CVE does not apply
-
Check firmware versionIn the router's web UI, navigate to Status or Management section and locate the firmware version field. Compare it to 1.09b03Affected if The installed firmware version is less than 1.09b03, the device is in the affected version range
-
Verify HNAP1 service is accessibleAttempt to access the HNAP1 SOAP endpoint via HTTP request to the router's IP address, typically at /HNAP1/ or check if port 80/443 is open for the management interfaceAffected if The HNAP1 SOAP endpoint is reachable from the network, providing the attack surface for command injection
-
Check if SetAPLanSettings function is exposedSend a SOAP request to the HNAP1 endpoint with a test SetAPLanSettings action and observe the router's response for validation errorsAffected if The SetAPLanSettings function responds to requests, indicating it is enabled and exploitable if the IPAddr parameter is not properly sanitized
The environment is affected if it contains a D-Link DAP-1325 router running firmware version lower than 1.09b03 with the HNAP1 SOAP endpoint accessible on 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
This device is end-of-life with no firmware patch available. Implement network segmentation to restrict access to the router's management interface, or replace the device with a supported model. If the device must remain in service, disable HNAP functionality if possible and monitor for exploitation attempts.
DAP-1325 Firmware version 1.09b03 or later
- 1. Navigate to the D-Link DAP-1325 router's web management interface
- 2. Go to the 'Management' or 'System' settings section
- 3. Locate the 'Firmware Upgrade' or 'Software Update' option
- 4. Download the firmware version 1.09b03 or later from the official D-Link support site (support.dlink.com)
- 5. Upload the firmware file through the web interface and wait for the upgrade to complete
- 6. After reboot, verify the firmware version in the router's status page to confirm the update was successful
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-41190 — 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-41190 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