CVE-2020-10135Public exploit

Adjacent device impersonation via unauthenticated pairing

Published May 19, 2020 · Updated Sep 17, 2024

Authentication bypass in Bluetooth BR/EDR 5.2 and earlier allows physically proximate attackers to impersonate a previously paired device. The protocol accepts a spoofed trusted-device address, permits Secure Connections downgrade, and can complete one-way authentication after a role switch without verifying the link key. The attacker must know a trusted device address and be within Bluetooth range; success makes the rogue device appear authenticated, while full access requires a successful KNOB follow-on attack.

CVSS severity4.8
Medium
EPSS probability2.37%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in Bluetooth BR/EDR 5.2 and earlier allows physically proximate attackers to impersonate a previously paired device. The protocol accepts a spoofed trusted-device address, permits Secure Connections downgrade, and can complete one-way authentication after a role switch without verifying the link key. The attacker must know a trusted device address and be within Bluetooth range; success makes the rogue device appear authenticated, while full access requires a successful KNOB follow-on attack.

The record

CVE
CVE-2020-10135
Published
May 19, 2020
Updated
Sep 17, 2024
Vendor
Bluetooth SIG, Inc.
Product
Bluetooth Basic Rate/Enhanced Data Rate (BR/EDR)
Classifications
CWE-290, CAPEC-667, T1036
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 19, 2020CVE publishedPublication date reported by the CVE source.
  2. Sep 17, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.2 <=5.2

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Bluetooth SIG, Inc. · Bluetooth Basic Rate/Enhanced Data Rate (BR/EDR)version=5.2 <=5.2

Published CVSS scores

4.8CERT/CCAV:A/AC:L/Au:N/C:P/I:P/A:N
5.4OracleCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-290Authentication Bypass by Spoofing
CAPEC-667Bluetooth Impersonation AttackS (BIAS)
T1036Masquerading

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo