well, at least now we know why 17.26 rolled out so quickly.
This is the same group that forced Tesla to implement code signing last year. Apparently, they were able to bypass it. Don't expect any details from these folks, though. They won't share anything even after all the vulnerabilities have been patched due to the NDA.
New Car Hacking Research: 2017, Remote Attack Tesla Motors Again
"Keen Lab discovered new security vulnerabilities on Tesla motors and realized full attack chain to implement arbitrary CAN BUS and ECUs remote controls on Tesla motors with latest firmware.
Several highlights for 2017 Tesla Research:
This is the same group that forced Tesla to implement code signing last year. Apparently, they were able to bypass it. Don't expect any details from these folks, though. They won't share anything even after all the vulnerabilities have been patched due to the NDA.
New Car Hacking Research: 2017, Remote Attack Tesla Motors Again
"Keen Lab discovered new security vulnerabilities on Tesla motors and realized full attack chain to implement arbitrary CAN BUS and ECUs remote controls on Tesla motors with latest firmware.
Several highlights for 2017 Tesla Research:
- Realized full attack chain as we did in year 2016 to implement arbitrary CAN BUS and ECUs remote controls.
- Discovered multiple 0Days in different modules. Currently, Keen Lab is working with Tesla and related manufactures on assigning CVE number of the vulnerabilities.
- Tesla implemented a new security mechanism “code signing” to do signature integrity check of system firmware that will be FOTAed to Tesla motors in Sept 2016. The code signing was bypassed by Keen Lab.
- The “Group lighting show of Model X” in our demonstration is technically arbitrary remote controls on multiple ECUs at the same time. It shows Keen Lab’s research capability on CAN BUS and ECUs."
