BLE Pairing Security Scenarios
BLE Pairing Security Scenarios
Scenario: A startup launches a Bluetooth smart lock for Airbnb hosts. During beta testing, security researchers demonstrate they can unlock any door during the initial pairing process by sitting in a car 20 meters away with a laptop. The lock uses “Just Works” pairing for “convenience” - no PIN entry required.
Think about:
- How can an attacker unlock the door without physical access?
- What specific vulnerability in “Just Works” pairing enables this attack?
- The lock has AES-128 encryption AFTER pairing - why doesn’t that prevent the attack?
- How would you redesign the lock’s security?
Key Insight: Authentication happens BEFORE encryption. “Just Works” provides:
- No user-authenticated verification step during pairing
- No protection against active MITM or pairing hijack during setup
- Link encryption does not help if the attacker becomes the paired/bonded device
Secure redesign options:
- Numeric Comparison: require the installer to confirm a code shown by the lock and the phone
- OOB commissioning: use an internal QR code / NFC tap so physical access is required to enroll
- Application-layer authorization: even after pairing, require explicit authorization for “unlock” commands
Scenario: You’re managing a fleet of 100 Bluetooth-connected medical devices (insulin pumps) in a hospital. Nurses complain that re-pairing tablets to pumps every shift change (3x/day) wastes 5 minutes per device. IT Security insists that bonding is disabled because “stored keys are a security risk if tablets are lost or stolen.”
Think about:
Work through Knowledge Check: Bonding vs. Pairing Trade-offs as a connected sequence. Start with What’s the actual security difference between pairing-only and bonding?. Next, How much time is wasted without bonding? (100 devices x 3 shifts x 5 min). Then, Can you implement bonding securely with proper key management?. Finally, What’s the risk if a bonded tablet is stolen?.
Key Insight: Bonding = convenience vs. security trade-off, but can be mitigated:
With Bonding (SECURE implementation):
Work through Knowledge Check: Bonding vs. Pairing Trade-offs as a connected sequence. Start with Pair once, but store keys using a hardware/OS-backed keystore (when available). Next, Require user authentication (PIN/biometric) before high-risk actions. Then, Support revocation (remove bonds when a tablet is lost) and remote wipe. Then, Consider a periodic re-authentication policy based on your risk model. Finally, Log pairing/connection events for auditability.
Scenario: A device uses LE Legacy pairing and relies on a short, printed passkey/PIN (“unique per device”) for security. The team assumes “it’s encrypted, so it’s safe.”
Think about:
- Why does low-entropy user input (e.g., a 4-6 digit passkey) matter?
- Why can Legacy pairing be risky if an attacker records the pairing transcript?
- What changes when you use LE Secure Connections?
- Beyond pairing, what authorization checks should still exist for safety-critical commands?
Key Insight: Strong ciphers don’t help if key agreement/authentication is weak.
Risk framing (order-of-magnitude):
- 4-digit PIN: 10,000 guesses
- 6-digit passkey: 1,000,000 guesses (approximately 20 bits)
Safer alternatives:
- Prefer LE Secure Connections with Numeric Comparison or OOB when possible
- Avoid static/shared passkeys; treat printed codes as a usability step, not a long-term secret
- Add application-layer authorization (e.g., signed “unlock” commands, role checks) even after pairing
- Plan for revocation (remove bonds when devices are replaced/lost)