CVE-2024-2104
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 · uneditedDue to improper BLE security configurations on the device's GATT server, an adjacent unauthenticated attacker can read and write device control commands through the mobile app service wich could render the device unusable.
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 · high confidenceThe device has improper BLE GATT server security configurations that allow an adjacent unauthenticated attacker within BLE range to read and write device control commands intended for the mobile app service. This enables the attacker to manipulate device functionality, potentially rendering the device unusable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm BLE GATT server is discoverable and accessibleUse a BLE scanner tool (such as nRF Connect, BLEah, or hcitool) to scan for the device and attempt a GATT connection without any prior pairing or authenticationAffected if The device's GATT server accepts connections from unauthenticated BLE clients within range
-
Identify authentication requirements for GATT accessAfter connecting, attempt to read or write to GATT characteristics without providing any PIN, passkey, or bonding. Observe whether the device rejects or allows the operationAffected if The device permits read or write operations on GATT characteristics without requiring authentication or pairing
-
Examine GATT characteristic permissionsUse a GATT client to enumerate all services and characteristics. Check which characteristics are marked as writable or readable without encryption or authentication requirements, particularly those labeled as control or command servicesAffected if Sensitive control or command characteristics are writable or readable without authentication permissions set
-
Verify BLE link encryption is enforcedUse a BLE sniffer (such as Ubertooth, nRF Sniffer, or similar) to capture BLE traffic between the device and a client. Determine if the link encryption is enabled and data is transmitted encryptedAffected if BLE communication occurs without encryption or uses 'Just Works' pairing with no encryption
-
Check BLE specification and security modeDuring connection, inspect the BLE version negotiated (such as 4.0, 4.2, 5.0) and the security mode advertised. Verify if LE Secure Connections are supported and requiredAffected if The device uses BLE versions below 4.2 or does not implement LE Secure Connections for GATT operations
The environment is affected if the BLE GATT server allows read or write access to device control commands without requiring authentication, pairing, or encryption from an adjacent attacker.
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.
From vendor dataImplement proper BLE security by requiring authentication, encryption (minimum BLE 4.2 with LE Secure Connections), and authorization for sensitive GATT characteristics; disable or protect write operations without proper pairing.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2104 — 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-2024-2104 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