3 ms·

Bluetooth stacks are very complex due to the initially-vague 1.1 spec and the need for thousands of per-device quirks handlers. Even as specs were tightened, ol

Bluetooth stacks are very complex due to the initially-vague 1.1 spec and the need for thousands of per-device quirks handlers. Even as specs were tightened, old device interop remains needed. If you implement a stack precisely as per spec, about half the devices out there won’t work with it (no exaggeration). This situation is not a recipe for good code. Now that BLE has audio (the last thing from classic that it lacked), we can begin phasing out BT classic and this mess. However, it will be a decade before anyone can safely drop bt classic interop. Basically: anywhere you have a Bluetooth stack that supports bt classic, feel free to ASSUME there are RCEs and DOSs lurking. You will not be wrong. Source: a full blown case of PTSD from having written and debugged a few BT stacks

Gigachad 1y ago
Could still contain it though. Bluetooth would only be needed for the non critical sound/calls/navigation stuff which should be it's own separate subsystem, on a read only OS with boot chain security so even if you did find an exploit in the bluetooth stack, it would only give you access to very unimportant things, and only until the car reboots. Of course I don't expect it's implemented anywhere near securely, but in theory it's very possible. Game console companies have this stuff pretty solved.