203
Android 15 really doesn't want you to turn off Bluetooth - Android Authority
(www.androidauthority.com)
this post was submitted on 05 Apr 2024
203 points (97.2% liked)
Android
28040 readers
165 users here now
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In what ways is having bluetooth on but not doing anything insecure?
I mean it was not too long ago there was a bug which could lead to an unauthenticated RCE against Bluetooth on Android.
https://nvd.nist.gov/vuln/detail/CVE-2022-20345
So yea, reducing surface area of attack when a feature is not needed is kinda important.
When we do defcon, Bluetooth is one of the easiest protocols to take control of. It's funny. It's also easy to spoof, easy to mess with, and generally very insecure.
was at 37c3 and people were constantly spamming BLE pairing requests lmao
I'm curious, what about Bluetooth makes it insecure? Is it that vendors create insecure implementations, like Android, or is it a human issue like connecting to things by default? I recall the Bluetooth spec being unbelievably complex and verbose, which obviously increases risk and makes it harder to audit, but it doesn't get many updates, and I don't recall seeing many issues with the spec itself. I mean it's not like it's fixing a CVE every quarter like with netty packages.
It’s too complicated. Bluetooth is complicated. It tries to do way too much, and not even the experts can implement it in a consistent fashion because different Bluetooth stacks are forced to make assumptions where the specification is unclear.
When you have a large, complex, and poorly designed specification, you’re going to get bugs. The main limiting factor has been the short range of Bluetooth preventing widespread exploitation.
Its more complex than I can talk about here in any kind of depth, but it comes down to it being a very old protocol. It has known security issues that are just not fixed as it would break backwards compatibility with a lot of devices. So the same issues that were chosen to not be fixed are still out there. You can, with very little effort, take control of just about any Bluetooth device(or partial). Or at least knock it out if commission.
There's a ton of Honeypot projects. Just the first Google result: https://github.com/andrewmichaelsmith/bluepot
tracking!
People lock their door when lock picks and axes exist. Making criminals work harder to access your belongings is pretty important in a lot of aspects.
I mean, just look at what happened over in ios land. Every time there is a new security issue or denial of service attack on their bluetooth stack, apple has to scramble to fix it because bluetooth is always on in their devices. Android at least has some respite by turning off bluetooth, especially on old devices that no longer receiving security updates.
My bad for exaggerating. Yes, you can permanently disable bluetooth on iphone, but iphone users are less likely to do so compared to android users. This is by design because apple needs the majority of users to have their bluetooth turned on for their find my network. This made bluetooth-based security issue more impactful in apple ecosystem than in android.
Now that Google is planning to do the same in android, I'm worried that it'll be even worse than in apple ecosystem simply because most android phones have much shorter support period. This means future bluetooth vulnerabilities might remain unpatched in some phones and those phones will be more likely to have bluetooth turned on.
So many assumptions here, I bet you think you're smart 😂 with your ggoogly phone ttracker marketing device.
Why can't we discuss some topics without resorting to personal attack? If you disagree with something, you can always refute it without being a dick.
Bluetooth has one of the largest network stacks. It's bigger than Wifi. This means some parts of the stack probably aren't tested and may have bugs or vulnerabilities. It has duplicate functionality in it. This opens up the possibility that flaws in how different parts interact could lead to vulnerabilities or exploits.
A number of years ago some security researchers did an analysis of the Windows and Linux stacks. They found multiple exploitable vulnerabilities in both stacks. They called their attack blue borne, but it was really a series of attacks that could be used depending on which OS you wanted to target. Some what ironically, Linux was more vulnerable because the Linux kernel implemented more of the protocol than Windows.
What? The kernel only implements HCI - a way to talk to hardware
The Bluetooth stack and its protocols are implemented in BlueZ or on Android in Gabeldorsche
Yeeeaaah, that makes more sense. 😅 That would be a giant gaping vulnerability if everything was in kernel space.
The Google Nearby feature thing (Google's coming version of Apple Air Tags) will require a constant background Bluetooth scanner to listen for the tags.
My opinion: that stays off. Looking for your lost phone, luggage, or ex-wife? Im not going to help you if i dont know you. Buy a new item, take better care of it.