BlueKitchen BTstack versions prior to 1.8.1 contain an out-of-bounds read vulnerability in the AVRCP Browsing Target GET_FOLDER_ITEMS handler that fails to validate packet boundaries and attribute count data. An attacker with a paired Bluetooth Classic connection can exploit insufficient bounds checking on the attr_id parameter to cause crashes and corrupt attribute bitmap state.
Security readout for executives and security teams
Plain-English summary
This is a Bluetooth stack flaw that can crash or disturb media-browsing behavior in products using BlueKitchen BTstack before 1.8.1. An attacker needs a paired Bluetooth Classic connection, so exposure is limited compared with internet-facing bugs, but embedded devices may be harder to inventory and update.
Executive priority
Treat as a targeted Bluetooth-adjacent risk, not an emergency internet-scale issue. Prioritize asset discovery and firmware/vendor validation, especially for devices exposed to public pairing environments or safety-sensitive operations.
Technical view
BTstack before 1.8.1 has insufficient bounds checks in the AVRCP Browsing Target GET_FOLDER_ITEMS handler. Invalid packet boundary or attribute count handling around attr_id can cause out-of-bounds reads and undefined behavior, with reported low integrity and availability impact.
Likely exposure
Most relevant to embedded, IoT, automotive, audio, or custom devices that include BlueKitchen BTstack with Bluetooth Classic AVRCP browsing enabled. The affected metadata in the bundle is sparse, so teams should verify actual library versions in firmware and SBOMs.
Exploitation context
The bundle does not cite active exploitation, and KEV status is false. The stated attacker position is adjacent Bluetooth range with a paired Bluetooth Classic connection and user interaction, limiting broad opportunistic exploitation.
Researcher notes
Focus review on AVRCP Browsing Target GET_FOLDER_ITEMS parsing, packet boundary validation, attribute count handling, and attr_id bitmap state. Avoid assuming exploitability beyond crash or state corruption without product-specific testing and vendor confirmation.
Mitigation direction
Upgrade BTstack components to version 1.8.1 or later where applicable.
Check vendor firmware advisories for products embedding BTstack.
Disable unused Bluetooth Classic or AVRCP browsing features where feasible.
Limit pairing to trusted devices and remove stale pairings.
Prioritize firmware updates for devices in shared or public environments.
Validation and detection
Inventory products, firmware, and SBOMs for BlueKitchen BTstack usage.
Confirm whether deployed builds are earlier than BTstack 1.8.1.
Verify whether AVRCP Browsing Target support is enabled.
Review vendor release notes and advisories for product-specific fixes.
Run defensive Bluetooth regression tests in a controlled lab environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
Reliance on Undefined, Unspecified, or Implementation-Defined Behavior represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.