Ravindra BagaleCourses & study guides मराठी Track your progress

44. Mobile Device Security – Android, iPhone, Bluetooth and Wi-Fi

44.7 Bluetooth Risks – Pairing Hygiene and BlueBorne Awareness

By Last updated:

Bluetooth = short-range radio. Everyday risks:

  • Pairing to the wrong speaker / headset in a busy café
  • Old phones left discoverable forever
  • Sensitive file / contact share prompts accepted blindly
  • BlueBorne-class bugs (2017, Armis): implementation flaws in Bluetooth stacks on multiple OSes that, as reported, could allow proximity attackers serious impact without classic pairing in some cases – awareness + patch, not a lab exploit recipe in this book

Blue habits:

  1. Turn Bluetooth off when unused (especially in crowds / travel)
  2. Pair only expected device names; remove old pairings
  3. Keep OS / Bluetooth stack patched (BlueBorne lesson)
  4. Do not accept surprise pairing pop-ups
  5. Never run "Bluetooth hack APK" against classmates
Red team (attacker) does Blue team (defender) detects / stops
Social-engines pairing to attacker gadget User verifies device name; rejects unknown
Abuses unpatched BlueBorne-class flaws (concept) Vendor security updates; replace EOL phones
Leaves malware listening via paired link Remove unused pairings; BT off when idle

Ravindra Bagale's Tip

Students download a BlueBorne PDF and try the exploit. That is not in the book. Interview: "I patch Bluetooth stacks and minimise discoverability; I do not practise airborne exploits on strangers." Remember this.

Lab

On OWN phone / emulator: list paired devices; remove one unused. Toggle BT off. Write 5-line BlueBorne awareness note (Armis 2017, patch, no recipe). Pair with Salman – ethics: no scanning adjacent seats.

Real incident: BlueBorne Bluetooth vulnerabilities (2017)

In September 2017, Armis disclosed a set of Bluetooth implementation vulnerabilities nicknamed BlueBorne, affecting Android, Windows, Linux, and older iOS (pre-iOS 10 in Armis reporting). CERT and vendor advisories described serious outcomes including remote code execution or man-in-the-middle themes on affected stacks, often discussed as workable from proximity without normal user pairing in some scenarios. Google, Microsoft, and others issued patches; Armis and follow-on reporting stressed that unpatched and EOL devices remained a long tail. Defence: apply OS security updates, disable Bluetooth when unused, inventory SME phones that never patch. Source: Armis BlueBorne disclosure (2017); CERT VU#240311; vendor security bulletins (verify; say "reported" for device-count estimates).

Extended teaching notes

Why this lesson matters

Cameras, sensors and plant controllers often ship with weak defaults. Segment them from IT, change passwords, block inbound internet, and watch outbound traffic.

Real examples

Global: Mirai showed what default passwords on routers/cameras can do at scale. Indian SME (sample): a factory puts PLCs on a separate VLAN reachable only via a jump host.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.