Security readout for executives and security teams
Plain-English summary
This is a Bluetooth pairing weakness affecting passkey-based pairing in Core Specifications 2.1 through 5.3. A nearby attacker positioned in the pairing process may be able to learn the session passkey and finish pairing with the target device. The business risk is unauthorized trusted-device pairing, not remote internet compromise.
Executive priority
Treat this as a moderate operational risk for environments relying on Bluetooth pairing for sensitive workflows, access, or device trust. Prioritize inventory and vendor update tracking over emergency response unless local pairing abuse is suspected.
Technical view
The issue involves Bluetooth LE and BR/EDR Secure Connections pairing and Secure Simple Pairing using Passkey Entry. The described attack reflects a crafted public key with the same X coordinate and reflects initiating-device authentication evidence, potentially revealing the passkey and allowing authenticated pairing with the responding device. It is related to CVE-2020-26558.
Likely exposure
Exposure is likely limited to Bluetooth-capable devices or stacks supporting affected Bluetooth Core Specifications 2.1 through 5.3 and using Passkey Entry pairing. The source bundle does not identify specific vendors, products, operating systems, chipsets, or fixed versions.
Exploitation context
The CVE is not marked in KEV, and the provided sources do not state active exploitation. The CVSS vector indicates local attack conditions, required user interaction, and high confidentiality and integrity impact if pairing is abused.
Researcher notes
Evidence is strongest at the Bluetooth specification behavior level. The bundle lacks named affected implementations, exploit-in-the-wild claims, or concrete patch identifiers. Validation should focus on whether products implement the affected pairing modes and whether vendors issued product-specific guidance.
Mitigation direction
- Check Bluetooth SIG and device vendor guidance for supported fixes or workarounds.
- Update Bluetooth firmware, operating systems, and device software when vendor fixes are available.
- Avoid passkey pairing for sensitive devices when stronger vendor-supported pairing options exist.
- Perform pairing only in trusted physical locations with unexpected nearby devices minimized.
- Review device trust lists and remove unknown or unnecessary paired devices.
Validation and detection
- Inventory devices and stacks using Bluetooth Passkey Entry pairing.
- Map Bluetooth versions against Core Specifications 2.1 through 5.3 exposure.
- Review vendor advisories for CVE-2021-37577 or passkey impersonation language.
- Confirm firmware and OS versions include relevant Bluetooth security updates.
- Audit paired-device lists for unexpected or unauthorized trusted devices.
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-639: 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-2021-37577 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
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:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L1.35.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
Source materials
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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.