manis
Member
In addition, firmware updates aren't signed, but must come from Tesla - so at least there's not any obvious way for someone to push malicious firmware without compromising Tesla's infrastructure:
"Must come from Tesla" is pretty loose though because without air-gapped signing there's no guarantee of that. The credentials for VPN were on the SD cards so just by being a Model S owner they can try to attack the VPN server and the infrastructure behind it, which could let them push bad firmware if successful. They can try to obtain access of an employee and escalate permissions. And the list goes on. Having a 4yr old WebKit vulnerability shows that not everything is carefully patched. I'm not trying to bash Tesla, they have done far better than a lot of car makers in a lot of areas. Just saying that it isn't great the firmware wasn't signed or that a known vulnerability hadn't been patched.