Connection hijacking via pairing-method confusion
Published May 19, 2020 · Updated Sep 16, 2024
Pairing method confusion in Bluetooth Core 5.2 and earlier allows physically proximate attackers to hijack connections during pairing. Numeric Comparison and Passkey Entry reuse a six-digit value, while peers fail to authenticate that both sides selected the same association model. The attack requires two devices pairing within wireless range and a user who enters one peer's comparison number as the other's passkey; successful pairing lets the attacker intercept or modify traffic exposed by enabled profiles.
Summary
What happened
Pairing method confusion in Bluetooth Core 5.2 and earlier allows physically proximate attackers to hijack connections during pairing. Numeric Comparison and Passkey Entry reuse a six-digit value, while peers fail to authenticate that both sides selected the same association model. The attack requires two devices pairing within wireless range and a user who enters one peer's comparison number as the other's passkey; successful pairing lets the attacker intercept or modify traffic exposed by enabled profiles.
The record
- CVE
- CVE-2020-10134
- Published
- May 19, 2020
- Updated
- Sep 16, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- Method Confusion Attack on Bluetooth Pairingproof of concept · demonstrated
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