CVE-2020-10135

What it actually does

Allows an unauthenticated adjacent attacker to complete Bluetooth BR/EDR pairing authentication without valid credentials or the link key, enabling impersonation of a previously paired master or slave device.

Why it matters to the business

Nearby attackers can establish unauthorized Bluetooth connections to affected devices, leading to potential data interception or unauthorized control in environments relying on legacy pairing; no widespread ransomware use or urgent CISA deadlines apply.

How an attack unfolds

An attacker positioned within Bluetooth range initiates pairing requests that bypass credential checks in legacy or secure-connections modes, completing authentication against a previously paired remote device without knowledge of the link key.

How to fix it

Apply the fixed commit 39d95ab8122c5d9ed18e69dc024870cae08d2d60 in theonedev/onedev (GIT); disable legacy Bluetooth pairing where feasible and enforce secure connections with updated implementations.

How to confirm the fix worked

Confirm devices are updated to the fixed commit or later; test pairing attempts from unauthenticated adjacent positions to verify rejection without credentials.

Typical attack path

1. Obtain adjacent physical or wireless proximity to the target Bluetooth device
2. Send crafted pairing initiation packets impersonating a trusted master or slave
3. Trigger authentication completion without supplying the link key
4. Establish an active connection for data access or further interaction

How to detect it

Review Bluetooth stack logs and pairing event records for failed or anomalous authentication attempts from unknown addresses; no specific threat actor campaigns noted.

What your security team should do

• Prioritize patching theonedev/onedev instances to the listed fixed commit
• Review and disable legacy Bluetooth pairing modes across the environment
• Monitor for unusual adjacent Bluetooth pairing events
• Assess EPSS and exploit availability trends for ongoing risk evaluation