Tesla Model X

This vulnerability allows physical attackers to execute arbitrary code on affected Tesla vehicles. Authentication is not required to exploit this vulnerability. The specific flaw exists within the ice_updater update mechanism. The issue results from the lack of proper validation of user-supplied firmware. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-17463.

Published: 2023-03-29T00:00:00.000Z
Updated: 2025-02-14T16:35:03.426Z

Certain Tesla vehicles through 2022-03-26 allow attackers to open the charging port via a 315 MHz RF signal containing a fixed sequence of approximately one hundred symbols. NOTE: the vendor's perspective is that the behavior is as intended

Published: 2022-03-27T12:07:15.000Z
Updated: 2024-08-03T05:41:10.815Z

Tesla Model X vehicles before 2020-11-23 do not perform certificate validation during an attempt to pair a new key fob with the body control module (BCM). This allows an attacker (who is inside a vehicle, or is otherwise able to send data over the CAN bus) to start and drive the vehicle with a spoofed key fob.

Published: 2020-11-30T21:23:12.000Z
Updated: 2024-08-04T16:55:09.684Z

Tesla Model X vehicles before 2020-11-23 have key fobs that rely on five VIN digits for the authentication needed for a body control module (BCM) to initiate a Bluetooth wake-up action. (The full VIN is visible from outside the vehicle.)

Published: 2020-11-30T21:23:41.000Z
Updated: 2024-08-04T16:55:09.269Z

Tesla Model X vehicles before 2020-11-23 have key fobs that accept firmware updates without signature verification. This allows attackers to construct firmware that retrieves an unlock code from a secure enclave chip.

Published: 2020-11-30T21:24:03.000Z
Updated: 2024-08-04T16:55:09.669Z