Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


05:55 PM

Bluetooth Security Weaknesses Pile Up, While Patching Remains Problematic

Turns out, creating wireless ecosystems for a vast number of different architectures, configurations, and use cases is hard.

The complex nature of Bluetooth continues to cause security problems for the low-powered, short-range wireless technology, with academic researchers releasing a parade of new attacks against the technology in the past few months.

On Sept. 9, the Bluetooth Special Interest Group (SIG) issued a statement regarding two papers released by university researchers that described ways of undermining the security of paired Bluetooth devices in specific circumstances. Last month at the Workshop on Offensive Technologies (WOOT) conference, a group of researchers from Purdue University also showed off several weaknesses that could allow attackers to spoof a device that had previously been paired using the Bluetooth Low Energy (BLE) protocol. And in May, researchers presenting at the IEEE Symposium on Security and Privacy showed off a similar attack that abuses a flaw in the specification to allow the impersonation of a paired device. 

Related Content:

New Bluetooth Vulnerabilities Exposed in Aruba, Cisco, Meraki Access Points

Special Report: Computing's New Normal, a Dark Reading Perspective

New on The Edge: Making the Case for Medical Device Cybersecurity

The complexity of the Bluetooth ecosystem and the large number of implementations have made security hard to achieve, while the rise in easier-to-use Bluetooth auditing tools, such as the InternalBlue open source toolkit, has made it easier for vulnerability researchers to do their work, says Yossi Oren, a senior lecturer at Ben-Gurion University in Israel and a researcher in the school's Implementation Security Lab.

"It used to be difficult to research Bluetooth because the hardware was closed and tightly controlled," Oren says. "Recently it's been getting much easier to hack Bluetooth ... [because] you don't need any customer radio platform or special technical skills."

The three different attacks — dubbed the Bluetooth Low Energy Spoofing Attack (BLESA), the Bluetooth Impersonation Attacks (BIAS), and BLURtooth — demonstrate that the complexity of ensuring security across the diverse connected-device ecosystem has resulted in many potential implementation problems and, in some cases, specification weaknesses.

"This is just the latest discovery to involve security issues with Bluetooth connections," said Chris Hauk, consumer privacy champion at PixelPrivacy, a consumer privacy information site, in a statement to Dark Reading. "It is a constant back and forth between Bluetooth radio manufacturers, who scramble to fix flaws via firmware updates, and bad actors that scramble to exploit the flaws before they're fixed."

In a paper published at the USENIX Security WOOT 2020 symposium, for example, researchers from Purdue University found a way to exploit vulnerabilities in some implementations of the Bluetooth Low Energy (BLE) protocol and spoof a previously paired device. The attacker's device can connect to a Bluetooth-capable device, such as a fitness tracker or wireless earbuds, to gather information on the targeted device's attributes. Using those attributes — and exploiting a weakness in the specification in some cases and implementation issues in others — attackers can masquerade as one of the paired devices.

"[E]ven BLE stack implementations correctly following the specification can potentially be susceptible to spoofing attacks," the researchers stated in their paper. "For instance, we found that the BLE protocol stack ... used in Linux client devices ... while following the BLE specification correctly, is susceptible to the identified spoofing attack."

The security vulnerabilities found to date can have serious consequences, but because of Bluetooth technology's short range, attacks are usually limited, says Ben-Gurion University's Oren.

"Using these attacks, you can impersonate Bluetooth devices, inject data into connections between Bluetooth devices and their controllers — for example, fool a motion detector — and take devices offline, making them unusable until you reboot them," he said. "All of the attacks assume physical proximity, so they can't be launched across the Internet, but certainly if your adversary can get near you you should be careful."

Unfortunately, patching Bluetooth vulnerabilities remains difficult because security issues need to first be patched by device makers, and then those patches have to be distributed to and applied by every device owner. The result is that many devices are never patched, even if the providers issue an update, PixelPrivacy's Hauk said.

"Unfortunately, as it has been with previous Bluetooth bugs, sys admins face a nightmare of attempting to patch all vulnerable devices, and that's only if there is a patch available," he said in a statement. "It is also unfortunate that standard users of mobile and other devices will not patch their devices if and when a patch becomes available." 


Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Russian Military Officers Unmasked, Indicted for High-Profile Cyberattack Campaigns
Kelly Jackson Higgins, Executive Editor at Dark Reading,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-10-23
A Cross-Site Request Forgery (CSRF) vulnerability is identified in FruityWifi through 2.4. Due to a lack of CSRF protection in page_config_adv.php, an unauthenticated attacker can lure the victim to visit his website by social engineering or another attack vector. Due to this issue, an unauthenticat...
PUBLISHED: 2020-10-23
FruityWifi through 2.4 has an unsafe Sudo configuration [(ALL : ALL) NOPASSWD: ALL]. This allows an attacker to perform a system-level (root) local privilege escalation, allowing an attacker to gain complete persistent access to the local system.
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to, contains a vulnerability in the ShadowPlay component which may lead to local privilege escalation, code execution, denial of service or information disclosure.
PUBLISHED: 2020-10-23
An arbitrary command execution vulnerability exists in the fopen() function of file writes of UCMS v1.4.8, where an attacker can gain access to the server.
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to, contains a vulnerability in NVIDIA Web Helper NodeJS Web Server in which an uncontrolled search path is used to load a node module, which may lead to code execution, denial of service, escalation of privileges, and information disclosure.