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.

Mobile Security

// // //

BlueBorne Threatens 5 Billion Bluetooth Devices

More than 5 billion devices are vulnerable to a set of eight Bluetooth flaws, even if they aren't in discoverable mode.

Computer and mobile users have long believed that everything is better with Bluetooth. It turns out that criminal hackers may very well agree. A group of eight vulnerabilities -- collectively known as "BlueBorne" -- makes roughly 5.3 billion devices subject to intrusion.

Armis Labs discovered the vulnerabilities and followed the rules of responsible disclosure by giving information to hardware and software vendors prior to public disclosure to allow time for patches to be written and distributed before exploits were likely to appear in the wild. That's the first bit of good news.

The next bit of good news is that some major vendors have taken advantage of the advance notice to patch systems and reduce customer exposure to the flaws. Google and Microsoft have recently issued patches that address the issues and many Linux distros are in the process of releasing patches. Apple managed to fix the vulnerabilities earlier; any users whose devices are on current or near-current versions of operating systems for Apple computers or devices are safe.


You're invited to attend Light Reading's 11th annual Future of Cable Business Services event. Join us in New York on November 30 for the premier independent conference focusing on the cable industry's continuing efforts in the commercial services market – all cable operators and other communications service providers get in free.

Now for the bad news. Many of the devices containing vulnerable Bluetooth implementations cannot or will not be patched. The only way for these devices to be safe is for Bluetooth to be disabled.

That's because of the "silent" nature of the attacks possible through these vulnerabilities. A targeted Bluetooth-equipped device will not have to be in discoverable mode to be vulnerable. Users and security systems won't be able to use connected device lists for protection because the vulnerable devices doesn't have to be paired with the attacker's device to be vulnerable.

Once infected, a single device can be the source of lateral infection for other Bluetooth-equipped systems in the organization. That infection could take place very quickly and just as silently as the original exploit. That's the exploit: What could an attacker do through these vulnerabilities?

The payload carried by these exploits could include botnet, ransomware, spyware or virtually any other malware attack. All delivered silently and quickly to virtually every mobile and desktop device in the organization.

What is a company to do to protect itself? First, make sure that all mobile and personal computing devices are running current software versions. If devices can't be updated to current operating systems, then turn off Bluetooth on any non-current device. If you have devices that can be neither updated nor turned off, then it's time to take a serious look at your refresh cycles: This threat is no joke.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-1142
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use URL decoding to retrieve system files, credentials, and bypass authentication resulting in privilege escalation.
CVE-2023-1143
PUBLISHED: 2023-03-27
In Delta Electronics InfraSuite Device Master versions prior to 1.0.5, an attacker could use Lua scripts, which could allow an attacker to remotely execute arbitrary code.
CVE-2023-1144
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 contains an improper access control vulnerability in which an attacker can use the Device-Gateway service and bypass authorization, which could result in privilege escalation.
CVE-2023-1145
PUBLISHED: 2023-03-27
Delta Electronics InfraSuite Device Master versions prior to 1.0.5 are affected by a deserialization vulnerability targeting the Device-DataCollect service, which could allow deserialization of requests prior to authentication, resulting in remote code execution.
CVE-2023-1655
PUBLISHED: 2023-03-27
Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0.