dbcve.org
Dap 1325 FirmwareOperating system · Dlink

CVE-2023-41196

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.09b03 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
D-Link DAP-1325 HNAP SetHostIPv6StaticSettings StaticAddress 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-18816.

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 confidence

The D-Link DAP-1325 router contains a command injection vulnerability in its HNAP1 SOAP endpoint's SetHostIPv6StaticSettings function. The StaticAddress parameter is not validated before being used in a system call, allowing an attacker to inject arbitrary shell commands. Since authentication is not required and the vulnerable code executes with root privileges, network-adjacent attackers can achieve unauthenticated remote code execution.

MitigationApply vendor firmware patches when available; if no patch exists, isolate the device on a restricted network segment to limit exposure to adjacent attackers.

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
Dap 1325 FirmwareOperating system
Affected:< 1.09b03

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is D-Link DAP-1325
    Access the router web interface or check the device label/sticker to verify the exact model number
    Affected if Device is not a D-Link DAP-1325 unit, then it is not affected by this specific CVE
  2. Check the installed firmware version
    Log into the router admin interface and navigate to the Status or Firmware Upgrade page to view the current firmware version, then compare it against 1.09b03
    Affected if Firmware version is lower than 1.09b03 (for example, 1.08 or earlier), indicating the device is within the affected version range
  3. Verify HNAP1 SOAP service is accessible
    Attempt to access the HNAP1 endpoint on the device (typically at /HNAP1/ or check for port 80/443 open responses) to confirm the service is exposed on the local network
    Affected if The HNAP1 interface is reachable from the network and responds to SOAP requests, meaning the attack surface is present
  4. Check if router is network-adjacent to untrusted devices
    Review network segmentation and ACLs to determine if the router management interface can be reached by untrusted or guest network segments
    Affected if The router is accessible from network segments that include untrusted or unauthenticated users, which would allow adjacent attackers to reach the vulnerable endpoint

A user is affected if they have a D-Link DAP-1325 router running firmware version lower than 1.09b03 with the HNAP1 service accessible on a network segment reachable by adjacent attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.09b03 or later
Fixed in 1.09b03
Interim mitigation

Apply vendor firmware patches when available; if no patch exists, isolate the device on a restricted network segment to limit exposure to adjacent attackers.

Recommended fix High confidence

D-Link DAP-1325 firmware version 1.09b03 or later

  1. Access the D-Link DAP-1325 router web management interface
  2. Navigate to the firmware upgrade or administration section
  3. Download the latest firmware version from D-Link's official support page (supportannouncement.us.dlink.com) for the DAP-1325 model
  4. Upload the firmware file and initiate the upgrade process
  5. Wait for the router to reboot and apply the new firmware
  6. Verify the firmware version has been updated to 1.09b03 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dap 1325 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA2.0 h
23.0 hours of engineering $4,020
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41196 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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