Security readout for executives and security teams
Plain-English summary
This flaw affects Bluetooth pairing. A nearby attacker could trick a user into completing two mismatched pairing prompts, potentially gaining credentials between two devices. Business urgency is moderate because exploitation requires close physical proximity and user action, but successful abuse could expose sensitive Bluetooth profiles.
Executive priority
Treat this as a moderate operational risk for Bluetooth-heavy environments, especially offices, healthcare, industrial, or field settings. Prioritize asset identification and vendor guidance rather than emergency response unless exposed high-value devices depend on Bluetooth pairing.
Technical view
CVE-2020-10134 is a Bluetooth method confusion issue in Bluetooth Core v5.2 and earlier LE and certain BR/EDR implementations. An adjacent unauthenticated attacker may initiate different pairing methods on peer devices and rely on user prompt confusion, enabling credential acquisition and operations allowed by exposed profiles.
Likely exposure
Exposure is most likely where Bluetooth-enabled devices support affected LE or relevant BR/EDR pairing behavior and users pair devices in attacker-adjacent environments. The source bundle does not identify specific vendors, device models, or affected operating systems beyond Bluetooth Core v5.2 and earlier context.
Exploitation context
The bundle does not show known active exploitation, and KEV status is false. Abuse requires adjacent access and user interaction during pairing. Impact depends on which Bluetooth profiles are enabled and whether the device asks for explicit authorization before sensitive access.
Researcher notes
Evidence supports adjacent, unauthenticated, user-assisted method confusion with high confidentiality and low integrity impact. The provided sources do not establish exploit availability, specific product matrices, or universal remediation, so validation should remain vendor- and implementation-specific.
Mitigation direction
- Check Bluetooth and device vendor guidance for CVE-2020-10134 applicability.
- Apply vendor firmware, OS, or Bluetooth stack updates when available.
- Avoid pairing devices in untrusted or crowded radio environments.
- Reject unexpected, duplicate, or mismatched Bluetooth pairing prompts.
- Disable Bluetooth or pairing mode when not operationally required.
- Require explicit authorization for sensitive Bluetooth profile access where configurable.
Validation and detection
- Inventory Bluetooth LE and BR/EDR-capable assets and stack versions.
- Map devices against Bluetooth Core v5.2 or earlier exposure statements.
- Review vendor advisories for patches or configuration guidance.
- Confirm users receive clear pairing prompts and authorization checks.
- Verify sensitive Bluetooth profiles are disabled or permission-gated where possible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-351: 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 lookupCVE-2020-10134 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N2.14.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- VU#534195CVE reference · third-party-advisory, x_refsource_CERT-VN
- https://www.bluetooth.com/learn-about-bluetooth/bluetooth-technology/bluetooth-security/method-vulnerability/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Type Distinction
Insufficient Type Distinction represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.