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

Exp

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: 2020-05-19 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-10135 is rated High Exploit Risk (68.7/100): CVSS Medium severity, with high exploitation likelihood (EPSS 20.20%, 96th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-10135

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-10135

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-29 21.53% 20.20% -1.34%
2 2026-04-21 20.20% 21.53% +1.34%
3 2026-04-11 — 20.20% —

Full EPSS history (28 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-10135

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.4 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.5 [email protected]
5.4 3.1 MEDIUM
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.5 [email protected]
4.8 2.0 MEDIUM
AV:A/AC:L/Au:N/C:P/I:P/A:N Click to expand
Access vector (AV:A)
Requires access to an adjacent network segment.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 6.5 4.9 [email protected]

Weakness enumeration for CVE-2020-10135

OS Trackers for CVE-2020-10135

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2020-10135
suse medium CVE-2020-10135 severity moderate: SUSE including 699 source package names (amazon/suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, amazon/suse-sles-15-sp1-chost-byos-v20220127-hvm-ssd-x86_64, …), 1078 product×package rows across 121 product lines (HPE Helion OpenStack 8, Image SLES12-SP5-Azure-BYOS, … (121 product lines)): Fixed 907, Known Affected 157, Known Not Affected 14. https://www.suse.com/security/cve/CVE-2020-10135/
ubuntu medium CVE-2020-10135 medium priority: Ubuntu including 169 source packages (linux, linux-allwinner, …), 2213 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1719, not-affected 235, released 211, ignored 47, needed 1. https://ubuntu.com/security/CVE-2020-10135

Affected software / configurations for CVE-2020-10135

Vendor Product Version Raw CPE
bluetooth bluetooth_core <= 5.2 cpe:2.3:a:bluetooth:bluetooth_core:*:*:*:*:br:*:*:*
bluetooth bluetooth_core <= 5.2 cpe:2.3:a:bluetooth:bluetooth_core:*:*:*:*:edr:*:*:*
opensuse leap 15.1 cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*

References for CVE-2020-10135

cvelogic Threat Intelligence