Dap 1360 FirmwareOperating system · Dlink

CVE-2023-32145

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 Patch available

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 Hardcoded Credentials Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of D-Link DAP-1360 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the processing of login requests to the web-based user interface. The firmware contains hard-coded default credentials. An attacker can leverage this vulnerability to bypass authentication on the system. . Was ZDI-CAN-18455.

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

A detailed technical summary for this CVE is being prepared.

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

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
Recommended fix High confidence

DAP-1360: Firmware 6.15eub01 | DAP-2020: Firmware 1.03rc004

  1. 1. Identify the exact model number (DAP-1360 or DAP-2020) of your D-Link device
  2. 2. Check the current firmware version installed on the device through the web management interface
  3. 3. For DAP-1360: If firmware version is less than 6.15eub01, download the fixed firmware 6.15eub01 from the official D-Link support website
  4. 4. For DAP-2020: If firmware version is less than 1.03rc004, download the fixed firmware 1.03rc004 from the official D-Link support website
  5. 5. Access the device's web-based management interface and navigate to the firmware upgrade section
  6. 6. Upload and apply the downloaded firmware file following the on-screen instructions
  7. 7. After the upgrade completes, verify the new firmware version is installed and test that authentication functions properly
  8. 8. Consider changing any default credentials and configuring strong, unique passwords post-upgrade
Caveat Standard firmware upgrade risks apply - ensure stable power during upgrade process; backup configuration if possible; some settings may reset to defaults

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32145 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