Skip to main content
Public proof of conceptFix available

CVE-2020-15802

A public proof of concept exists; no exploitation attested.

  • Published2020-09-11
  • Fixed in5.1
  • WeaknessCWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Devices supporting Bluetooth before 5.1 may allow man-in-the-middle attacks, aka BLURtooth. Cross Transport Key Derivation in Bluetooth Core Specification v4.2 and v5.0 may permit an unauthenticated user to establish a bonding with one transport, either LE or BR/EDR, and replace a bonding already established on the opposing transport, BR/EDR or LE, potentially overwriting an authenticated key with an unauthenticated key, or a key with greater entropy with one with less.

Timeline

dates in UTC
  1. 2020-09-1114:15CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Versions per branch

NVD
Bluetooth bluetooth core specification
BranchAffectedFixed in
5.1< 5.15.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • linuxUbuntu:Pro:20.04:LTSall versions · no fixed version listedand 22 other packages
  • linuxUbuntu:Pro:18.04:LTSall versions · no fixed version listedand 13 other packages
  • linuxUbuntu:Pro:16.04:LTSall versions · no fixed version listedand 8 other packages
  • linuxUbuntu:Pro:14.04:LTSall versions · no fixed version listedand 3 other packages
  • linuxUbuntu:25.10all versions · no fixed version listedand 9 other packages
  • linuxUbuntu:24.04:LTSall versions · no fixed version listedand 44 other packages
  • linuxUbuntu:22.04:LTSall versions · no fixed version listedand 60 other packages
  • linuxRoot:Ubuntu:22.04all versions · fixed in 5.15.0-203.213.aikido.119and 1 other package

20 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Bluetooth bluetooth core specification to 5.1

Advisories and patches

Detection

read 2026-11-01 01:02 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2020-09-11
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-2ffq-f4m4-q248

Frequently asked questions

What is CVE-2020-15802?

Devices supporting Bluetooth before 5.1 may allow man-in-the-middle attacks, aka BLURtooth. Cross Transport Key Derivation in Bluetooth Core Specification v4.2 and v5.0 may permit an unauthenticated user to establish a bonding with one transport, either LE or BR/EDR, and replace a bonding already established on the opposing transport, BR/EDR or LE, potentially overwriting an authenticated key with an unauthenticated key, or a key with greater entropy with one with less.

Is CVE-2020-15802 actively exploited?

Active exploitation of CVE-2020-15802 has not been confirmed. Its EPSS score was 7.1% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-15802?

CVE-2020-15802 has a CVSS v3 base score of 5.9 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record