CVE-2024-48289
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 · uneditedAn issue in the Bluetooth Low Energy implementation of Cypress Bluetooth SDK v3.66 allows attackers to cause a Denial of Service (DoS) via supplying a crafted LL_PAUSE_ENC_REQ 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 · moderate confidenceA vulnerability in the Bluetooth Low Energy implementation of Cypress Bluetooth SDK v3.66 allows attackers to cause a Denial of Service by sending a specially crafted LL_PAUSE_ENC_REQ packet, which is a Link Layer control message used during BLE encryption negotiation. The malformed packet likely triggers an error condition or crash in the BLE stack.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cypress Bluetooth SDK usageSearch project dependencies, firmware manifests, or SDK documentation for references to Cypress Bluetooth SDK. Look for header files like btle.h, ble_task.c, or library files from Cypress (often named CYBT* or WICED*).Affected if The system uses Cypress Bluetooth SDK for BLE functionality
-
Verify SDK version is v3.66Check SDK version file, release notes, or firmware build metadata for exact version string. Compare against v3.66.Affected if Installed version is exactly v3.66 and no patches have been applied
-
Confirm BLE stack is activeInspect runtime configuration or firmware to determine if BLE is enabled. Look for BLE initialization calls, BLE_GAP or BLE_GATT service activation, or check if BLE advertising/scanning is running.Affected if BLE functionality is enabled and the stack is initialized
-
Check encryption negotiation is permittedReview BLE security configuration. Verify whether BLE link encryption (LE Secure Connections or Legacy Pairing) is permitted in the BLE_GAP conn_params or security settings. LL_PAUSE_ENC_REQ is only processed when encryption has been established and is being paused.Affected if BLE encryption negotiation is enabled and the device can enter an encrypted link state
A system is affected if it uses Cypress Bluetooth SDK v3.66 with BLE enabled and supports BLE link layer encryption negotiation, making it vulnerable to malformed LL_PAUSE_ENC_REQ packets causing stack failure.
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 to a patched version of the Cypress Bluetooth SDK once available. In the interim, restrict physical proximity to Bluetooth devices or implement network-level BLE packet filtering to block malicious LL control packets.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48289 — 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-2024-48289 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