# CVE-2020-11921: Security feature bypass in n/a

> Attackers can hijack Bluetooth connections due to lack of encryption, gaining full control over the Lush 2 device.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-q7m5-chmw-937j

## What is CVE-2020-11921?

CVE-2020-11921 is a high-severity vulnerability in n/a, published on 7 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An 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.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2020-11921?


## How do I fix CVE-2020-11921?

No fix has been published for CVE-2020-11921 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-11921 being exploited?

There is no known exploitation of CVE-2020-11921 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11921 and fix it if it is affected.

What it is: CVE-2020-11921 is a high-severity vulnerability in n/a, published on 7 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11921 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-11921/ (Markdown: https://insights.sbomify.com/CVE-2020-11921/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11921
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11921
- OSV: https://osv.dev/vulnerability/CVE-2020-11921

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-11921/
Summaries are generated and may contain mistakes; the official description above is the record.