I'll just say that if you value being protected against most vulnerabilities like this you currently have three options: an Android-powered device from Black Berry, an Android-powered device direct from Google, or an i Phone. Instead let's talk about what Blueborne is and how it does it, as well as what you can do about it.

It's a series of simple attacks on various parts of the Bluetooth stack running on almost every smart device in the world. It's not a Mi TM (Man in The Middle) attack, where someone intercepts Bluetooth traffic between you and a thing you're connected to.

That's why it was important that Armis hold the release until Apple, Google, and Microsoft were able to act.

The scary part is what happens after the connection is made.

Bluetooth started out in 1998 as a simple short-range wireless connection.

It's now on more than 8 billion devices worldwide and has grown and grown in features and complexity.

Google change a good bit of the "default" Bluetooth implementation for Linux, as did Apple and Microsoft.

The things you use are well-protected against things like a man in the middle attack or a way to get admin permission over Bluetooth.Of course, almost every Android-powered device doesn't yet have this patch and won't for a while.I'll resist the temptation to make this all about Android's update woes and the million-and-one different reasons that it happens.The people writing an operating system and the security team whose job it is to break it will all take their share of the responsibility here, too.The problem here is that they're dealing with impossibly complex code in the Bluetooth stack and while they are busy trying to patch it against one thing other things could also be exploited.This causes a buffer underflow and bypasses the standard Bluetooth Security Management Protocols to hit the failsafe "just works" connection.