CVE-2019-17060
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 (BLE) stack implementation on the NXP KW41Z (based on the MCUXpresso SDK with Bluetooth Low Energy Driver 2.2.1 and earlier) does not properly restrict the BLE Link Layer header and executes certain memory contents upon receiving a packet with a Link Layer ID (LLID) equal to zero. This allows attackers within radio range to cause deadlocks, cause anomalous behavior in the BLE state machine, or trigger a buffer overflow via a crafted BLE Link Layer frame.
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 · moderate confidenceThe NXP KW41Z BLE stack (MCUXpresso SDK with BLE Driver 2.2.1 and earlier) fails to validate the Link Layer ID (LLID) field in incoming BLE packets. When LLID equals zero, the stack either attempts to execute arbitrary memory contents or triggers a buffer overflow, enabling remote code execution, deadlocks, or state machine corruption within radio range.
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<= 2.2.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the MCUXpresso SDK version in useCheck project files, build artifacts, or firmware metadata for the SDK version string (e.g., in SDK manifest, version.h, or release notes). Look for references to 'MCUXpresso SDK' or 'mcux' in the build system.Affected if The SDK version is 2.2.1 or earlier
-
Identify the BLE Driver versionLocate the BLE stack library or source files in the SDK. Check the driver version in the SDK components folder (typically under middleware/ble) or in version headers within the BLE stack.Affected if BLE Driver version is 2.2.1 or earlier, or version cannot be determined but SDK is <=2.2.1
-
Check for LLID validation code in BLE stackSearch BLE stack source code (typically in controller/ll or similar path) for LLID field handling. Look for functions that parse the LLID byte in packet headers and verify whether there is a check rejecting LLID=0 before processing.Affected if No explicit validation for LLID=0 is found, or the code shows direct use of LLID value without bounds checking before memory operations
-
Verify BLE stack is enabled and processing packetsConfirm the device has BLE functionality enabled and is actively using the KW41Z radio stack. Check configuration files (e.g., ble_config.h) or runtime behavior indicating BLE is operational.Affected if BLE is enabled and the vulnerable BLE stack code is running on KW41Z hardware
You are affected if the MCUXpresso SDK version is 2.2.1 or earlier, the BLE Driver version is 2.2.1 or earlier, and BLE functionality is active on a KW41Z-based device.
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 dataUpdate the BLE driver to a version that properly validates LLID fields, or implement input validation at the radio interface to reject packets with invalid (zero) LLID values before they reach the stack.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17060 — 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-17060 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