CVE-2019-17517
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 · uneditedThe Bluetooth Low Energy implementation on Dialog Semiconductor SDK through 5.0.4 for DA14580/1/2/3 devices does not properly restrict the L2CAP payload length, allowing attackers in radio range to cause a buffer overflow via a crafted Link Layer packet.
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 confidenceThe Dialog Semiconductor BLE SDK through 5.0.4 for DA14580/1/2/3 chips fails to validate L2CAP payload lengths in incoming Link Layer packets, allowing attackers within radio range to send oversized payloads that overflow a fixed-size buffer.
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<= 5.0.4CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Dialog Semiconductor SDK version in useCheck SDK release notes, version headers, or firmware metadata for the version string. Look in SDK installation directories, typically under 'DA1458x_SDK' or similar naming conventions, for version files or documentation.Affected if The SDK version is 5.0.4 or earlier (any version <= 5.0.4).
-
Confirm target hardware is a DA14580/1/2/3 chipReview hardware specifications, device schematics, or firmware build configuration to identify the chip model number. These chips are part of Dialog Semiconductor's DA14580 series Bluetooth Low Energy SoCs.Affected if The firmware targets a DA14580, DA14581, DA14582, or DA14583 chip.
-
Verify L2CAP is enabled in the firmware configurationInspect the BLE stack configuration files (such as app_config.h, ble_stack_config.h, or similar) for L2CAP-related settings, GATT/GAP configuration, or L2CAP_CO_MAX or similar buffer size definitions.Affected if L2CAP is enabled in the BLE stack configuration.
-
Compare SDK version against affected rangeCross-reference the identified SDK version with the affected range. The vulnerability exists in SDK versions <= 5.0.4.Affected if The installed SDK version is 5.0.4 or any earlier version.
You are affected if your firmware uses Dialog Semiconductor BLE SDK version 5.0.4 or earlier on a DA14580/1/2/3 chip with L2CAP protocol support enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataObtain and deploy the patched SDK/firmware (5.0.5 or later) from Dialog Semiconductor to all affected devices; if no patch is available, retire or replace the vulnerable DA14580/1/2/3 hardware.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17517 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-17517 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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