Software Development KitApplication · Dialog Semiconductor

CVE-2019-17518

MEDIUM · 6.5 CVSS v3.1 Published 2020-02-10
Fix available
A fix is available. Upgrade to after 1.0.14.1081 or later.
See remediation →
70/100
Remediation priority · Elevated
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
The Bluetooth Low Energy implementation on Dialog Semiconductor SDK through 1.0.14.1081 for DA1468x devices responds to link layer packets with a payload length larger than expected, allowing attackers in radio range to cause a buffer overflow via a crafted packet. This affects, for example, August Smart Lock.

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

Dialog Semiconductor's BLE SDK for DA1468x devices fails to validate payload length in incoming link layer packets, allowing a remote attacker within radio range to send specially crafted packets with oversized payloads that overflow a buffer during the response handling.

MitigationUpdate to a patched version of the Dialog Semiconductor SDK (beyond 1.0.14.1081) and deploy recompiled firmware to affected devices. If no update is available, consider network segmentation to limit BLE radio range exposure.

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
Software Development KitApplication
Affected:<= 1.0.14.1081

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 DA1468x BLE hardware in use
    Determine whether your device or product utilizes Dialog Semiconductor's DA1468x series Bluetooth Low Energy chipset. This may be documented in hardware specifications, schematics, or Bill of Materials (BOM).
    Affected if The device uses DA14680, DA14681, DA14682, DA14683, DA14684, DA14685, DA14686, DA14687, or DA14688 BLE chipsets
  2. Determine the Dialog BLE SDK version
    Locate the Dialog Semiconductor Software Development Kit version used to compile your device firmware. Check build documentation, version control history, or SDK installation directory for a version identifier. SDK version is typically found in SDK release notes or the installed SDK folder name.
    Affected if SDK version is 1.0.14.1081 or any earlier version (versions <= 1.0.14.1081)
  3. Verify BLE link layer is enabled
    Confirm that Bluetooth Low Energy functionality is actively used on the device. The vulnerability exists in incoming link layer packet handling, so any device with BLE advertising, scanning, or connection capabilities is processing these packets.
    Affected if BLE feature is enabled and the device accepts incoming BLE connections or advertises
  4. Compare firmware version against affected range
    Retrieve the compiled firmware version running on your DA1468x device. This may be accessible via firmware metadata, bootloader information, or by querying the device if debug access is available.
    Affected if The firmware was built using SDK version 1.0.14.1081 or earlier and contains the unpatched link layer handling code

You are affected if your DA1468x-based device uses firmware built with the Dialog Semiconductor BLE SDK at version 1.0.14.1081 or earlier, where BLE link layer processing is active.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0.14.1081
Interim mitigation

Update to a patched version of the Dialog Semiconductor SDK (beyond 1.0.14.1081) and deploy recompiled firmware to affected devices. If no update is available, consider network segmentation to limit BLE radio range exposure.

Fix this in Software Development Kit Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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