CVE-2020-10134
Reported by certcc · Published May 19, 2020
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| LE | Bluetooth | 5.2 |
| bluetooth_core | bluetooth | 5.2 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Bluetooth | LE | 5.2 |
| Bluetooth | LE | 5.2 |
Timeline
- May 18, 2020 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Jan 20, 2026 CVE Updated
- Mar 17, 2026 Distribution Patch (8 in total, the first dated here)
- Mar 17, 2026 Security Advisory (13 in total, the first dated here)
- Sep 6, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2020-10134
vulnetix vdb fixes CVE-2020-10134
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-10134/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- VU#534195 third-party-advisoryx_refsource_CERT-VN
- x_refsource_CONFIRM