SecPod

Learn Search

Search across all Learn content

← Back to Security Research

BlueBorne Attack: Millions of Devices at Risk

Over 5.3 billion devices across Windows, Linux, ios, and Android are affected by a new attack vector called BlueBorne Attack. Unless traditional attacks, this attack vector spreads over the air via Bluetooth, and the hacker does not need to pair with each device. A good Vulnerability Management Tool...

Oct 17, 2017By Kashinath T2 min read

Over 5.3 billion devices across Windows, Linux, ios, and Android are affected by a new attack vector called BlueBorne Attack. Unless traditional attacks, this attack vector spreads over the air via Bluetooth, and the hacker does not need to pair with each device. A good Vulnerability Management Tool can significantly reduce all these attacks and create a safe and secure environment for your organization.

If Bluetooth is turned on, the hacker can get control of the device and spread the malware; all processes will be undetectable by the victim.

Since the attacker only requires Bluetooth to be turned on, with the BlueBorne attack, the infected device can further connect to infect any device, such as a laptop, smartwatch, smartphone, or any other Bluetooth-enabled device. A Vulnerability Management Software can automatically detect any form of vulnerability.

There is no way of detecting or stopping the attack, as it is invisible. But thankfully, there are security patches releasing for all the platforms that are affecting.

How does the Attack work?

The BlueBorne attack vector has several stages. First, the attacker locates active Bluetooth connections around him or her. Devices can be identified even if they are not set to "discoverable" mode. Next, the attacker obtains the device’s MAC address, which is a unique identifier of that specific device. By probing the device, the attacker can determine which operating system his victim is using, and adjust his exploit accordingly. The attacker will then exploit a vulnerability in the implementation of the Bluetooth protocol in the relevant platform and gain the access he needs to act on his malicious objective. At this stage the attacker can choose to create a Man-in-The-Middle attack and control the device's communication, or take full control over the device and use it for a wide array of cybercriminal purposes. - Armis

CVE Details are listing below for the BlueBorne attack:

Platform : Windows (Bluetooth Driver)
CVE’s     : CVE-2017-8628
Severity  : Critical
Impact    : Spoofing Vulnerability

Platform : Linux (Bluetooth stack)CVE’s     : CVE-2017-1000250, CVE-2017-1000251Severity  : CriticalImpact    : Information Leak Vulnerability

Click here to understand how Saner can help organizations to protect against “BlueBorne Attack” and similar threats on Windows.

Featured Posts

Open CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials
CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials

CVE Research

CVE-2023-49105: The ownCloud Authentication Flaw That Exposed Sensitive Credentials

Sep 25, 2026

Open Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: RouterOS SSH Attacks Predate Production Fixes in CISA's September 10, 2026 KEV Additions

Two MikroTik RouterOS CVEs entered CISA KEV seven days after production fixes. Dated reporting places SSH-chain exploitation involving CVE-2026-86060 at least one calendar day before those releases; no comparable start date is established for CVE-2026-67277.

Sep 25, 2026

Open Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch
Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch

CVE Research

Patch Analysis & Exploitation Timeline: A Day-Old Chrome Bug and an Eight-Month-Old Fortinet Flaw Share the Same KEV Batch

Four vulnerabilities added to CISA’s KEV catalog on September 9, 2026 show widely different timelines between public disclosure and formal exploitation-based prioritization, ranging from one day to 239 days.

Sep 24, 2026

Open TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

CVE Research

TA412/APT31: Mapping Threat Actor Patterns to CVE Exploitation Chains

A chronological look at how a long-running China-nexus espionage cluster evolved from server-side exploitation to a chained Chrome/Windows zero-day kit — and what that shift signals.

Sep 24, 2026