# CVE-2020-10134: Bluetooth devices supporting LE and specific BR/EDR implementations are vulnerable to method confusion attacks

> An adjacent attacker can bypass Bluetooth authentication via method confusion, gaining unauthorized access to device operations and data.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 May 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4fx5-wvjj-h2jp, UBUNTU-CVE-2020-10134

## What is CVE-2020-10134?

CVE-2020-10134 is a medium-severity authentication bypass vulnerability in Bluetooth LE, published on 19 May 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Pairing in Bluetooth® Core v5.2 and earlier may permit an unauthenticated attacker to acquire credentials with two pairing devices via adjacent access when the unauthenticated user initiates different pairing methods in each peer device and an end-user erroneously completes both pairing procedures with the MITM using the confirmation number of one peer as the passkey of the other. An adjacent, unauthenticated attacker could be able to initiate any Bluetooth operation on either attacked device exposed by the enabled Bluetooth profiles. This exposure may be limited when the user must authorize certain access explicitly, but so long as a user assumes that it is the intended remote device requesting permissions, device-local protections may be weakened.

Weakness: CWE-436 (Interpretation Conflict), CWE-351 (Insufficient Type Distinction)

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

It affects 1 product.


Products: Bluetooth Bluetooth Core.

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

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

## Is CVE-2020-10134 being exploited?

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

## Other vulnerabilities in Bluetooth LE

- [CVE-2020-10135](https://insights.sbomify.com/CVE-2020-10135/): Bluetooth devices supporting BR/EDR v5.2 and earlier are vulnerable to impersonation attacks (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10134 is a medium-severity authentication bypass vulnerability in Bluetooth LE, published on 19 May 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-10134 in the wild and no public exploit code.

Affected product: Bluetooth LE. 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-10134/ (Markdown: https://insights.sbomify.com/CVE-2020-10134/index.md)
```

## Sources

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

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