Security readout for executives and security teams
Plain-English summary
CVE-2023-6387 is a high-severity buffer handling flaw in Silicon Labs Gecko SDK Bluetooth LE HCI CPC sample application. A crafted adjacent Bluetooth interaction may crash affected firmware or possibly allow code execution if the vulnerable sample code was incorporated into a product. Exposure depends on whether teams used or adapted that sample code.
Executive priority
Treat as high priority for embedded or Bluetooth-enabled products using Silicon Labs Gecko SDK samples. Business urgency is highest where sample code reached production firmware, because impacts include device outage and potential code execution. If the sample was never used, residual risk is lower.
Technical view
The CVE describes incorrect buffer parsing in the Bluetooth LE HCI CPC sample application in Gecko SDK. It maps to out-of-bounds read and write weaknesses, CWE-125 and CWE-787. CVSS 3.1 is 7.5 with adjacent attack vector, high complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Organizations are most likely exposed if firmware or products include Silicon Labs GSDK 1.0 Bluetooth LE HCI CPC sample code or derivative parsing logic. The listed attack vector is adjacent, so exposure is generally near-range Bluetooth rather than internet-wide.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation is high complexity and adjacent network only, but successful exploitation could cause denial of service or remote code execution.
Researcher notes
The evidence identifies the vulnerable component and impact class but does not include exploit details, patch confirmation, or affected downstream products. Validate exposure by code provenance, not by vendor name alone. Avoid assuming all Gecko SDK users are affected without confirming use of the Bluetooth LE HCI CPC sample application.
Mitigation direction
- Inventory products using Silicon Labs GSDK Bluetooth LE HCI CPC sample code.
- Check Silicon Labs advisory and v4.4.0 release notes for vendor remediation guidance.
- Prioritize replacement or removal of sample-derived buffer parsing logic where used.
- Restrict Bluetooth exposure for affected devices until vendor-guided remediation is complete.
- Add regression tests around malformed or truncated Bluetooth HCI CPC inputs.
Validation and detection
- Confirm whether any firmware builds include GSDK 1.0 or sample-derived HCI CPC code.
- Map affected code paths to shipped Bluetooth LE device models and firmware versions.
- Review parser bounds checks against expected buffer lengths and message structures.
- Run non-destructive robustness tests in a controlled lab environment.
- Track vendor advisory status and document applied fixes or compensating controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCWE-787: 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.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-6387 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/SiliconLabs/gecko_sdk/releases/tag/v4.4.0CVE reference
- https://community.silabs.com/069Vm000000WNKuIAOCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.