CVE Intelligence
Skip to main content
MEDIUMpublic exploit

CVE-2020-10135

CVE-2020-10135 — Bluetooth devices supporting BR/EDR v5.2 and earlier are vulnerable to impersonation attacks

Legacy pairing and secure-connections pairing authentication in Bluetooth BR/EDR Core Specification v5.2 and earlier may allow an unauthenticated user to complete authentication without pairing credentials via adjacent access. An unauthenticated, adjacent attacker could impersonate a Bluetooth BR/EDR master or slave to pair with a previously paired remote device to successfully complete the authentication procedure without knowing the link key.

Published Updated Sources: cvelistV5, certcc

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

2%

chance of exploitation in 30 days

Affects

bluetooth

br_edr

CVSS base

5.4

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

Products (1)

br edr

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.4CVSS 3.1MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-757

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1600Weaken Encryption

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Indexed by

poc in github

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /EDR.

References

7 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.