CVE-2023-3024
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 · uneditedForcing the Bluetooth LE stack to segment 'prepare write response' packets can lead to an out-of-bounds memory access.
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 confidenceThis vulnerability allows an attacker within Bluetooth LE range to force the segmentation of 'prepare write response' packets, triggering an out-of-bounds memory access in the BLE stack. This is a memory corruption issue that could potentially allow code execution or denial of service, given the adjacent attack vector and medium severity.
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>= 1.0.0, < 6.0.0CVSS 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 Silabs Gecko SDK usageDetermine if your embedded application or firmware is built using the Silicon Labs Gecko Software Development Kit. Review your build system, dependencies, or firmware bill of materials for references to 'Silabs Gecko SDK', 'EFR32', or related BLE stack libraries.Affected if Your product uses the Silabs Gecko SDK for Bluetooth LE functionality.
-
Determine installed SDK versionLocate the SDK version in your project files, build configuration, or firmware metadata. This may be found in SDK release notes, version headers, or the directory name if the SDK is bundled with your firmware.Affected if The detected version is >= 1.0.0 and < 6.0.0.
-
Verify BLE stack is enabledInspect your runtime configuration or firmware build settings to confirm the Bluetooth LE stack is active. Check for BLE feature flags, service initialization code, or runtime status indicating BLE is powered on.Affected if BLE is enabled and the device accepts BLE connections.
-
Confirm ATT protocol handlers are activeReview your BLE stack configuration to verify that the Attribute Protocol (ATT) is operational, particularly write request/response handling paths.Affected if The BLE stack processes ATT write operations, which is typical for any BLE device exposing writable characteristics.
Your environment is affected if it uses Silabs Gecko SDK versions 1.0.0 through 5.x with BLE functionality enabled, as the vulnerability can be triggered via specially crafted BLE 'prepare write response' packets within radio range.
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.
dbcve · scoped6.0.0
Apply vendor-supplied firmware updates for affected Bluetooth LE implementations. If no patch is available, consider reducing BLE exposure by disabling unnecessary BLE functionality or limiting device proximity to untrusted actors.
Gecko SDK 6.0.0 or later
- Identify the current Gecko SDK version in use by checking project dependencies or build configuration
- Obtain Gecko SDK version 6.0.0 or later from the official Silicon Labs distribution (e.g., Simplicity Studio or Silicon Labs developer portal)
- Backup the current project configuration and dependencies
- Update the SDK reference in the project to point to version 6.0.0 or newer
- Rebuild the project to verify the update was applied correctly
- Perform regression testing on Bluetooth LE functionality, particularly prepare write response packet handling
- Deploy the updated firmware after confirming successful testing
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-3024 — 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-2023-3024 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