Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

vuln blueborne

Scans for nearby Bluetooth devices and assesses each one against the BlueBorne vulnerability set disclosed in September 2017.

BlueBorne is a collection of eight vulnerabilities affecting Bluetooth stacks across Linux, Android, Windows and iOS. Unlike most Bluetooth attacks, BlueBorne requires no pairing, no user interaction and no prior association with the target device. Any device with Bluetooth enabled and within radio range is potentially within the attack surface.

CVE coverage

CVEPlatformImpactCVSS
CVE-2017-0781AndroidRCE via BNEP heap overflow8.8
CVE-2017-0782AndroidRCE via AVDTP heap overflow8.8
CVE-2017-0783AndroidInformation disclosure via PAN6.5
CVE-2017-0785AndroidInformation disclosure via SDP6.5
CVE-2017-1000250Linux (BlueZ)Information disclosure via SDP6.5
CVE-2017-1000251Linux kernelRCE via L2CAP stack overflow8.0
CVE-2017-8628WindowsMitM attack via PAN/BNEP8.1

How detection works

The plugin cannot confirm patch status remotely. It uses observable Bluetooth properties to identify devices likely affected by each CVE:

SignalSourceInfers
Device name contains “Galaxy”, “Pixel”, “Huawei”, etc.Name propertyAndroid
Device name contains “ubuntu”, “raspberry”, “debian”, etc.Name propertyLinux
Bluetooth major class = Computer (0x01)Class propertyLinux
Bluetooth major class = Phone (0x02)Class propertyAndroid/mobile
Icon type = phoneIcon propertyAndroid/mobile
Advertises A2DP/AVDTP UUIDUUIDs propertyCVE-2017-0781/0782 target
Advertises BNEP/PAN UUIDUUIDs propertyCVE-2017-0783/0783/8628 target

All findings are advisory. A device that receives no specific CVE mapping is still reported as “in range” because BlueBorne can target any reachable device with Bluetooth Classic enabled.

Status

ResultMeaning
passScan completed (findings may still indicate exposure)
failBluetooth unavailable or no adapter found

Severity

SeverityCondition
HighPlatform identified (Android/Linux) and matching vulnerable profile present
MediumPlatform identified or vulnerable profile present
LowGeneric Bluetooth device with no specific indicators
InfoDevice discovered but no BlueBorne indicators found

Requirements

  • BlueZ daemon (bluetoothd) must be running.
  • The D-Bus system bus must be accessible.
  • Devices must be advertising and within radio range.

Usage

iottack vuln blueborne [OPTIONS]

Options

FlagShortDefaultDescription
--timeout <SECS>-t15Scan duration in seconds
--adapter <NAME>-afirst availableBluetooth adapter to use, e.g. hci0
--output <FILE>-o-Save result to a file
--format <FORMAT>-texttext or json
--verbose-v-Increase log verbosity

Examples

Scan with the default 15 second window:

iottack vuln blueborne

Extended scan with a specific adapter and JSON output:

iottack vuln blueborne --timeout 30 --adapter hci1 --format json --output report.json

Mitigation

Apply all Bluetooth security patches from September 2017 or later. Where possible, disable Bluetooth when not in use.

PlatformAction
AndroidApply the September 2017 Android Security Bulletin
LinuxUpdate kernel ≥ 4.14 and BlueZ ≥ 5.47
WindowsApply MS17-013 / KB4038788
iOSUpgrade to iOS 10 or later