| I dug into the technical details here over the last few days and as usual it's not quite as sinister as the hand wringing: * Automotive head units are just embedded computers. Most run Linux, QNX, or Windows CE, with some proprietary UI system on top. * These machines usually store data in an onboard database in flash (sometimes just SQLite). * Sometimes, phone data is captured using standard Bluetooth mechanisms (Message Access Protocol MAP and Phone Book Access Protocol PBAP) which require authorization on the phone side. Some vendors implement an additional "are you sure you want to share your information" check on the head unit side, and others don't. * This data is cached on the head unit so that finding a contact to call or reading a text message doesn't require 10 minutes worth of Bluetooth nonsense. * Some vendors inadequately purge this cached data when a Bluetooth pairing is removed from the head unit. * Berla sell data extraction exploits to law enforcement, just like other forensics vendors do for mobile phones. Sometimes this can extract latent data and sometimes active data. My advice: * Never authorize a head unit to download your contacts or SMS. * If you use a rental car, Factory Reset the head unit when you leave. That's decent protection for most people. I didn't find any evidence pointing to a central server upload, a conspiracy to build an LE database, etc. It's just typical crappy hardware manufacturer-made software leaving data around that shouldn't be left around, creating an opening for forensic vendor exploits to slurp the data. |
This is such an early 2000s idea. I'd much rather my car act as a dumb display that shows a copy of my phone screen then an intelligent agent that tries to replicate functionality already extant in my phone.