dbcve.org
Gecko Software Development KitApplication · Silabs

CVE-2023-6387

HIGH · 7.5 CVSS v3.1 Published 2024-02-02
Fix available
A fix is available. Upgrade to 4.4.0 or later.
See remediation →
80/100
Remediation priority · High
No privileges Zero-click

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 · unedited
A potential buffer overflow exists in the Bluetooth LE HCI CPC sample application in the Gecko SDK which may result in a denial of service or remote code execution

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 confidence

A buffer overflow vulnerability exists in the Bluetooth LE HCI CPC sample application within Silicon Labs' Gecko SDK. The flaw resides in the Host Controller Interface (HCI) layer handling Bluetooth Low Energy communications via the CPC (Concurrent Protocol) sample application. The overflow occurs due to insufficient bounds checking on input data, potentially allowing an attacker to overwrite adjacent memory, leading to denial of service or remote code execution.

MitigationUpdate to the patched version of the Gecko SDK once available. If using custom code derived from this sample application, implement strict input validation and bounds checking on all HCI packet processing routines, particularly in CPC protocol handlers.

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
Gecko Software Development KitApplication
Affected:< 4.4.0

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Gecko SDK usage
    Locate the Silicon Labs Gecko SDK installation directory or check project dependencies for presence of 'gecko_sdk' or 'Gecko SDK' components
    Affected if The Gecko SDK is present in the environment
  2. Check Gecko SDK version
    Inspect the SDK version file or manifest (such as version.h, gecko_sdk_version.h, or a VERSION file) within the Gecko SDK directory
    Affected if The installed version is earlier than 4.4.0 (e.g., 4.3.x, 4.2.x, etc.)
  3. Confirm CPC sample application is in use
    Search project files for references to 'cpc', 'CPC', 'concurrent protocol', or the sample application directory structure typically named 'cpc' or 'cpc_sample' within the SDK
    Affected if The CPC sample application or code derived from it is present in the project
  4. Verify HCI over CPC is enabled
    Inspect the build configuration, #define macros, or runtime settings for HCI_TRANSPORT=CPC or similar CPC-related HCI configuration options
    Affected if HCI communication over CPC transport is enabled in the build or configuration
  5. Confirm Bluetooth LE functionality
    Review the firmware or application configuration to determine if Bluetooth LE (BLE) stack components are compiled and active
    Affected if Bluetooth LE functionality is implemented using the Gecko SDK BLE stack

The environment is affected if using Gecko SDK version below 4.0 with the CPC sample application or derived code and HCI over CPC transport enabled for Bluetooth LE communications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.4.0 or later
Fixed in 4.4.0
Interim mitigation

Update to the patched version of the Gecko SDK once available. If using custom code derived from this sample application, implement strict input validation and bounds checking on all HCI packet processing routines, particularly in CPC protocol handlers.

Recommended fix High confidence

Gecko SDK 4.4.0

  1. 1. Identify the current version of the Gecko SDK being used in your project by checking the SDK version file or release notes
  2. 2. Navigate to the official Silicon Labs Gecko SDK download page or their GitHub repository
  3. 3. Download Gecko SDK version 4.4.0 or later
  4. 4. Replace the existing SDK files in your development environment with the updated version
  5. 5. Rebuild and recompile the Bluetooth LE HCI CPC sample application with the updated SDK
  6. 6. Re-deploy the rebuilt application to the affected devices
  7. 7. Verify the application functions correctly after the upgrade
Caveat Check Silicon Labs release notes for 4.4.0 for any API changes or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gecko Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6387 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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