LiveActive security incident?Get immediate response
CVE Record

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.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2020-10135 affects Bluetooth Classic BR/EDR pairing and authentication. A nearby unauthenticated attacker may impersonate a previously paired device and authenticate without knowing the shared link key. The risk is localized to Bluetooth range and affects confidentiality and integrity, not availability. Organizations may be exposed where laptops, phones, peripherals, embedded devices, industrial systems, or Linux Bluetooth stacks support BR/EDR v5.2 or earlier and retain trusted pairings. Actual exposure depends on vendor implementation, Bluetooth range, device roles, and whether vendor updates were applied. Treat this as a moderate, proximity-limited risk. Prioritize exposed mobile, endpoint, and embedded fleets in sensitive facilities, then fold remediation into normal firmware and endpoint patch cycles unless critical operations depend on Bluetooth trust relationships. Mitigation focus: Check Bluetooth SIG, OS, firmware, and device vendor guidance for CVE-2020-10135 updates.; Apply vendor Bluetooth stack or firmware updates where available.; Disable Bluetooth BR/EDR where business operations do not require it..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-757: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-10135 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2020-10135Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
BluetoothBR/EDR5.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-757 · source CWE mapping

Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')

Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.