CVE-2023-41192
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 PrimaryDNS 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-18812.
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 router's HNAP1 SOAP endpoint. The SetAPLanSettings function fails to validate user-supplied input (PrimaryDNS parameter) before using it in a system call, allowing unauthenticated network-adjacent 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 device modelAccess the router's web interface or check the device label to confirm it is a D-Link DAP-1325 routerAffected if The device is not a D-Link DAP-1325 model
-
Check firmware versionLog into the router web interface and navigate to the Status or Management page to view the firmware version, or use the command 'grep -i version /proc/mtd' or check the firmware file if you have access to the device via telnet/SSHAffected if The installed firmware version is lower than 1.09b03 (e.g., 1.08, 1.07, etc.)
-
Verify HNAP1 endpoint accessibilityAttempt to access the HNAP1 SOAP endpoint by sending an HTTP request to http://[router-ip]/HNAP1/ or check if port 80 or 443 is open and respondingAffected if The HNAP1 SOAP endpoint is reachable from the network (unauthenticated or authenticated)
-
Confirm PrimaryDNS parameter handlingIf you have access to the router, inspect the SetAPLanSettings function in the firmware binary or capture a network request to the HNAP1 endpoint to observe how the PrimaryDNS parameter is processedAffected if The PrimaryDNS parameter in SetAPLanSettings is passed to a system call without sanitization (requires binary analysis or source code access to confirm)
You are affected if you own a D-Link DAP-1325 router running firmware version lower than 1.09b03 and the HNAP1 management interface is accessible on your 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 is an end-of-life router with no available patch; replace with a currently supported device and restrict network access to management interfaces.
Firmware version 1.09b03 or later
- 1. Check the current firmware version of the DAP-1325 device through the router's web interface under the 'Status' or 'Management' section
- 2. Navigate to D-Link's official support page for the DAP-1325 at support.dlink.com
- 3. Download the firmware version 1.09b03 or later from the official download section
- 4. Access the router's web interface and go to the 'Management' or 'System' settings
- 5. Locate the 'Firmware Upgrade' or 'Update Firmware' option
- 6. Upload the downloaded firmware file and initiate the upgrade
- 7. Wait for the upgrade to complete (do not power off the device during this process)
- 8. After reboot, verify the firmware version has been updated to 1.09b03 or later
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-41192 — 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-41192 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