CVE-2023-0775
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 invalid ‘prepare write request’ command can cause the Bluetooth LE stack to run out of memory and fail to be able to handle subsequent connection requests, resulting in a denial-of-service.
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 confidenceThe vulnerability exists in the Bluetooth LE stack where an invalid 'prepare write request' command causes memory exhaustion. This prevents the device from properly handling subsequent Bluetooth LE connection requests, resulting in a persistent denial-of-service condition.
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= 5.1.0= 5.1.1CVSS 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 installationCheck your project dependencies or firmware build configuration for 'silabs gecko sdk' or 'gecko sdk' references. Look in build scripts, SDK manifest files, or firmware metadata.Affected if The Silabs Gecko SDK is present in your build environment
-
Determine the installed SDK versionLocate the SDK version file or build configuration that specifies the exact version number. Common locations include sdk_version.h, manifest.xml, or build configuration files.Affected if The version is exactly 5.1.0 or exactly 5.1.1
-
Verify Bluetooth LE stack is enabledCheck your firmware configuration for Bluetooth LE (BLE) stack initialization. Look for BLE-specific compilation flags, configuration macros like BLE_ENABLED, or BLE stack component inclusion in your build.Affected if Bluetooth LE functionality is compiled into or running on the device
-
Confirm ATT Protocol handling is activeVerify that the Bluetooth LE Attribute Protocol (ATT) is active on the device. This is typically present if the device acts as a GATT server or client, handling read/write/notify operations.Affected if The device handles BLE GATT/ATT operations
You are affected if your firmware uses Silabs Gecko SDK version 5.1.0 or 5.1.1 with the Bluetooth LE stack enabled and handling ATT/GATT operations.
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 · scopedApply vendor-provided firmware/security patches for the Bluetooth LE stack that properly validate prepare write request commands and implement adequate memory management to prevent exhaustion.
Gecko SDK version > 5.1.1 (latest stable release)
- 1. Identify all products using the Silicon Labs Gecko SDK versions 5.1.0 or 5.1.1
- 2. Check for and download the latest Gecko SDK release from Silicon Labs (siliconlabs.com)
- 3. Upgrade the Gecko SDK in your development environment to the latest stable version
- 4. Rebuild and test your firmware/application with the updated SDK
- 5. Deploy the updated firmware to affected devices
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-0775 — 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-0775 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