Flaws in how 17 models of headphones and speakers use Google’s one-tap Fast Pair Bluetooth protocol have left devices open to eavesdroppers and stalkers.

Flaws in how 17 models of headphones and speakers use Google’s one-tap Fast Pair Bluetooth protocol have left devices open to eavesdroppers and stalkers.

Link to see devices impacted: https://whisperpair.eu/

  • @fort_burp@feddit.nlEnglish
    0•3 months ago

    GOOGLE DESIGNED THE wireless protocol known as Fast Pair to optimize for ultra-convenient connections: It lets users connect their Bluetooth gadgets with Android and ChromeOS devices in a single tap.

    Bluetooth pairing is not a difficult process, imagine creating a whole new attack vector for that. And of course security was an afterthought. Capitalism is amazing for wasting resources and getting bad results for it.

    • @dance_ninja@lemmy.worldOPEnglish
      0•3 months ago

      I’d agree security needs more attention when developing protocols and products, and I’d also consider Bluetooth simple. That being said, I know plenty of folks that don’t like the Bluetooth pairing process, especially those without a technical background.

      Fast Pair is really convenient, and I’d say it can open the door for a lot of new experiences, but I do wish the developers put more effort into their TARA.

    • @zarenki@lemmy.mlEnglish
      0•3 months ago

      I think it’s far more common for devices to get pairing wrong than to get it right.

      Just a few of the very common issues I’ve seen in various devices:

      • TVs that are constantly in discoverable mode, even when the screen is off. Just in case the owner loses their remote and wants to pair a new one without reaching behind the TV to press a button. No way of avoiding this except disabling Bluetooth entirely, which makes the stock remote lose either partial or all functionality. Pairing requests also interrupt whatever you’re watching.
      • Audio devices that have a very short delay after turning on and waiting for any already-paired devices to connect before switching over to a pairing mode instead. So short that a smartphone in a low-power state (e.g. because you haven’t unlocked it for a few minutes) might not connect in time. Most if not all of the bluetooth-to-3.5mm receivers intended for older cars seem to share this problem.
      • Pairing codes are extremely underused in general, even among input devices. Most things seem to just pair with whoever sends a request first unconditionally.
      • @ragebutt@lemmy.dbzer0.comEnglish
        0•3 months ago

        On this note: if you root your webos tv there’s an app to truly disable Bluetooth, assuming you don’t use it. Imagine my surprise when one day my tv turned on with a request to allow my neighbors phone to connect to it? Modern convenience. I’m sure my neighbor just fat fingered the device list while trying to connect something else but the fact that it was even an option is absurd

    • @Auth@lemmy.worldEnglish
      0•3 months ago

      A lot of people genuinely find Fast Pair to be a big improvement over traditional Bluetooth pairing. So why is it such a bad idea for a company to design a protocol that solves the problem? I dont see that as wasting resources at all. Also Bluetooth pairing has had its own share of vulnerabilities over the years this issue isnt really unique to Fast Pair.

      • @fort_burp@feddit.nlEnglish
        0•3 months ago

        To each their own, no doubt. Personally I’m just in awe at how modern tech actually makes people tech-illiterate, and seemingly at a faster clip each year. Throw in an additional attack surface and that just makes it, for me, net minus. There are social and political implications to being tech-illiterate and tech-dependent (especially dependent on foreign and/or rogue states), which is another minus in my book.