dbcve.org
Dap 1650 FirmwareOperating system · Dlink

CVE-2019-12768

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-30
Fix available
A fix is available. Upgrade to 1.04b02_j65h or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
An issue was discovered on D-Link DAP-1650 devices through v1.03b07 before 1.04B02_J65H Hot Fix. Attackers can bypass authentication via forceful browsing.

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-1650 wireless access point contains an authentication bypass vulnerability allowing attackers to circumvent login requirements through forceful browsing (direct URL access to protected endpoints). The vulnerability exists in firmware versions up to v1.03b07 and is addressed by hot fix 1.04B02_J65H.

MitigationApply firmware version 1.04B02_J65H or later to affected DAP-1650 devices to remediate the authentication bypass vulnerability.

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 1650 FirmwareOperating system
Affected:< 1.04b02_j65h

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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-1650
    Access the device web interface or check the device label/metadata to verify the model number is DAP-1650
    Affected if Device is not a D-Link DAP-1650 unit (this CVE does not apply)
  2. Identify installed firmware version
    Log into the device web interface and navigate to the Status or System Information page to view the current firmware version, or use the device's diagnostic/management interface
    Affected if Unable to retrieve firmware version information from the device
  3. Compare firmware version to affected range
    Review the firmware version displayed on the device and compare it numerically and alphanumerically against the vulnerable range: versions up to and including v1.03b07, and any version prior to 1.04b02_j65h
    Affected if Firmware version is less than 1.04b02_j65h (including all versions up to v1.03b07)
  4. Verify web management interface accessibility
    Attempt to access the device web interface over HTTP/HTTPS from a network-connected host
    Affected if Web interface is reachable but login protection cannot be verified (vulnerability allows bypassing authentication via direct URL access to protected endpoints)

The device is affected if it is a D-Link DAP-1650 running firmware version lower than 1.04b02_j65h, as the authentication bypass flaw exists in those versions.

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.04b02_j65h or later
Fixed in 1.04b02_j65h
Interim mitigation

Apply firmware version 1.04B02_J65H or later to affected DAP-1650 devices to remediate the authentication bypass vulnerability.

Recommended fix Moderate confidence

1.04B02_J65H (Hot Fix)

  1. 1. Obtain firmware version 1.04B02_J65H or later from ftp2.dlink.com or the official D-Link support website for the DAP-1650 device
  2. 2. Access the DAP-1650 web-based management interface using an administrator account
  3. 3. Navigate to the firmware upgrade section (typically found under System > Firmware Upgrade or Management > Firmware Upgrade)
  4. 4. Upload the downloaded firmware file (.bin or .img) and initiate the upgrade
  5. 5. Wait for the device to complete the firmware update and reboot automatically
  6. 6. After reboot, verify the firmware version has been updated to 1.04B02_J65H or later in the device status page

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

Fix this in Dap 1650 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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