CVE-2020-11921
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 issue was discovered in Lush 2 through 2020-02-25. Due to the lack of Bluetooth traffic encryption, it is possible to hijack an ongoing Bluetooth connection between the Lush 2 and a mobile phone. This allows an attacker to gain full control over the device.
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 Lush 2 device transmits Bluetooth communications without encryption, enabling a man-in-the-middle attacker to intercept and hijack the ongoing connection between the device and its mobile phone application, thereby gaining full control over the device.
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 device modelIdentify if the device in question is the Lush 2 Bluetooth-enabled intimate device. Check the physical device, packaging, or associated mobile application for model identification.Affected if The device is a Lush 2 model with Bluetooth capability.
-
Verify Bluetooth is activeEnable Bluetooth monitoring on a nearby device or use a Bluetooth sniffer such as Wireshark with a compatible adapter to detect if the Lush 2 is transmitting BLE advertising or data packets.Affected if Bluetooth is enabled and the device is actively transmitting or advertising.
-
Check for encrypted pairingAttempt to pair with the Lush 2 using a BLE tool like nRF Connect or similar. Observe the pairing process to determine if the device requests or uses encryption (LE Secure Connections, passkey entry, or OOB authentication).Affected if The device pairs without requiring encryption or authentication, or accepts connections without a PIN/passkey.
-
Analyze Bluetooth traffic for encryptionCapture Bluetooth traffic between the Lush 2 and its paired mobile application using a BLE sniffer. Inspect the packets to verify whether the link layer is encrypted (look for LLID and encryption indicators in the ATT/GATT layers).Affected if Captured Bluetooth packets are in plaintext with no encryption layer applied to the communication channel.
A user is affected if they own a Lush 2 device and use it with Bluetooth enabled, as the device transmits unencrypted Bluetooth communications that can be intercepted by a nearby 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 dataThe device manufacturer must implement Bluetooth encryption (e.g., BLE secure connections with authenticated pairing) through a firmware update; users should limit device use to private environments until a patch is released.
- Consultation8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11921 — 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-2020-11921 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