dbcve.org
Dap 1360 FirmwareOperating system · Dlink

CVE-2023-32136

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.03rc004 / 6.15eub01 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-1360 webproc var:menu Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of D-Link DAP-1360 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling requests to the /cgi-bin/webproc endpoint. When parsing the var:menu parameter, the process does not properly validate the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. . Was ZDI-CAN-18414.

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

A stack-based buffer overflow vulnerability exists in the D-Link DAP-1360 router's web management interface. The flaw is located in the /cgi-bin/webproc endpoint where the var:menu parameter is parsed without proper length validation before being copied to a fixed-size stack buffer, allowing an unauthenticated network-adjacent attacker to overflow the buffer and execute arbitrary code with root privileges.

MitigationApply available firmware updates from D-Link; if no patch exists, disable remote web management access, segment the device on an isolated network, or replace the end-of-life device.

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 1360 FirmwareOperating system
Affected:< 6.15eub01
Dap 2020 FirmwareOperating system
Affected:< 1.03rc004

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. Identify the device model
    Locate the physical device or check network inventory for D-Link DAP-1360 or DAP-2020 access points. The model number is usually printed on a label on the device chassis.
    Affected if The device is a D-Link DAP-1360 or DAP-2020 unit.
  2. Determine the installed firmware version
    Access the router web management interface and navigate to the Status or Management section to view the firmware version. Alternatively, check the device label or documentation if the device is not network-accessible.
    Affected if The firmware version is below 6.15eub01 for DAP-1360 or below 1.03rc004 for DAP-2020.
  3. Verify the web management interface is accessible
    Attempt to reach the device web interface by browsing to its IP address on ports 80 or 443. Confirm the /cgi-bin/webproc endpoint responds by sending a request to http://[device-ip]/cgi-bin/webproc.
    Affected if The web management interface and the /cgi-bin/webproc endpoint are reachable from the network.
  4. Check if remote web management is enabled
    In the web interface, go to the Management or System settings section and look for options like Remote Management, Web Access, or HTTP/HTTPS management access. Confirm whether it is set to allow access from LAN only or from WAN/remote locations.
    Affected if Remote or WAN-side web management access is enabled, making the vulnerable endpoint accessible from outside the local network.

You are affected if you have a D-Link DAP-1360 or DAP-2020 device running firmware below the patched versions and the web management interface with the vulnerable /cgi-bin/webproc endpoint is network-accessible.

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.03rc004 / 6.15eub01 or later
Fixed in 1.03rc0046.15eub01
Interim mitigation

Apply available firmware updates from D-Link; if no patch exists, disable remote web management access, segment the device on an isolated network, or replace the end-of-life device.

Recommended fix High confidence

DAP-1360: Upgrade to firmware 6.15eub01 or later; DAP-2020: Upgrade to firmware 1.03rc004 or later

  1. Identify the specific D-Link model (DAP-1360 or DAP-2020) from the affected devices on the network
  2. Navigate to the D-Link support page (www.dlink.com or region-specific support)
  3. Download the firmware update: For DAP-1360, obtain version 6.15eub01 or later; For DAP-2020, obtain version 1.03rc004 or later
  4. Access the router's web management interface via HTTP/HTTPS
  5. Locate the Firmware Upgrade or Administration section in the router settings
  6. Upload the downloaded firmware file and initiate the upgrade
  7. Wait for the upgrade to complete and the device to reboot
  8. Verify the firmware version has been updated successfully
Caveat Router firmware upgrades may reset configuration to defaults; backup current settings before upgrading and reapply after

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

Fix this in Dap 1360 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA8.0 h
64.0 hours of engineering $11,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32136 — 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-32136 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