Incident: Tesla Model X Keyless Entry System Vulnerability Exploited for Theft

Published Date: 2020-11-23

Postmortem Analysis
Timeline 1. The software failure incident involving Tesla Model X keyless entry system vulnerabilities happened in August 2020 [107561]. 2. The incident was reported in November 2020 [107561, 107602, 107600].
System 1. Tesla Model X keyless entry system 2. Tesla Model X key fobs 3. Tesla Model X body control module (BCM) [107561, 107602, 107600]
Responsible Organization 1. Security researcher Lennert Wouters at Belgian university KU Leuven [107561, 107602] 2. COSIC research group of Imec and the University of Leuven in Belgium [107600]
Impacted Organization 1. Tesla Model X owners were impacted by the software failure incident [107561, 107602, 107600].
Software Causes 1. Lack of cryptographic signatures in the firmware update process for the key fobs, allowing for unauthorized firmware updates and manipulation of the key fobs [107561, 107600]. 2. Insecure pairing protocol that allowed a new, modified key fob to be paired with a Tesla Model X, bypassing security measures [107600].
Non-software Causes 1. Lack of cryptographic signatures in the firmware update process for the key fobs, allowing for uncertified updates [107600]. 2. Insecure pairing protocol that allowed a new, modified key fob to be paired with a Model X [107600]. 3. Vulnerabilities in the keyless entry system of the Tesla Model X and its key fobs, such as the lack of code signing for firmware updates and the BCM deriving its unique code from the car's VIN number [107561].
Impacts 1. The software failure incident allowed a hacker to steal a Tesla Model X in just a matter of minutes by exploiting vulnerabilities in the keyless entry system, rewriting the firmware of a key fob via Bluetooth connection, and pairing their own key fob with the victim's vehicle to drive it away [107561, 107602]. 2. The incident highlighted significant security oversights in Tesla's Model X key fobs, leading to the need for a patch to address the vulnerabilities [107602]. 3. The vulnerabilities in the keyless entry system of the Model X allowed unauthorized access to the vehicle within 90 seconds and the ability to start and drive the car with minimal effort [107561, 107602]. 4. The incident showcased a disconnect between the security design of the Model X's keyless entry system and its implementation, allowing a hacker to circumvent security measures with a few small mistakes in the software [107561]. 5. The software failure incident demonstrated the need for software updates for both the car and key fobs to prevent similar attacks in the future [107602, 107600].
Preventions 1. Implementing cryptographic signatures in the firmware update process for key fobs to ensure the legitimacy of updates could have prevented the software failure incident [107600]. 2. Strengthening the pairing protocol to prevent the pairing of new, modified key fobs to a Model X could have also prevented the software failure incident [107600]. 3. Enhancing the security measures in the keyless entry system, such as validating key fob firmware updates and preventing unauthorized pairing of key fobs with the vehicle, could have mitigated the vulnerabilities exploited in the incident [107561, 107602].
Fixes 1. Implementing a software update to the key fobs and possibly components of the cars to prevent the hacking technique used to steal a Tesla Model X [107561]. 2. Rolling out an update to address the vulnerability in the key fobs by better locking them down [107600]. 3. Closing the loopholes in the current software of the Tesla Model X and key fobs to prevent the exploitation of the security vulnerabilities [107602].
References 1. Lennert Wouters, security researcher at Belgian university KU Leuven [Article 107561, Article 107602] 2. Tesla [Article 107561, Article 107602, Article 107600] 3. COSIC, a research group of Imec and the University of Leuven in Belgium [Article 107600]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident related to hacking and stealing Tesla vehicles through vulnerabilities in the keyless entry system has happened before with Tesla's products. Security researcher Lennert Wouters previously found cryptographic vulnerabilities in Tesla Model S keyless entry systems that would have allowed radio-based car theft, similar to the recent incident with the Model X keyless entry system. Wouters mentioned that the vulnerabilities he exploited in the Model X keyless entry system were not unique to Tesla and that other key fobs with insecure firmware update mechanisms could also be vulnerable to similar attacks [Article 107561, Article 107600]. (b) The software failure incident involving hacking Tesla vehicles through vulnerabilities in the keyless entry system has also occurred with other organizations or their products. The COSIC research group of Imec and the University of Leuven in Belgium, which previously found a similar vulnerability with Tesla's Model S keyless entry system, conducted the latest security experiment on the Tesla Model X SUV. This indicates that similar vulnerabilities may exist in keyless entry systems of other vehicles or products from different organizations [Article 107600].
Phase (Design/Operation) design, operation (a) In the reported software failure incident related to the Tesla Model X keyless entry system vulnerability, the failure can be attributed to the design phase. The incident was caused by vulnerabilities in the design of the key fobs and the keyless entry system of the Model X. Security researcher Lennert Wouters discovered security issues in the Model X's keyless entry system, such as the lack of code signing for key fob firmware updates and an insecure pairing protocol that allowed a hacker to pair their own key fob with the victim's vehicle [107561, 107602, 107600]. (b) Additionally, the software failure incident can also be linked to the operation phase. The vulnerability exploited by the hacker required specific operations to be carried out, such as intercepting the key fob or the body control module in the car using a computer with a Bluetooth receiver. The hacker could then plug their computer into a port accessible from the dashboard to trick the car into thinking the false key fob was the correct one, enabling them to start and drive off with the Model X [107602, 107600].
Boundary (Internal/External) within_system, outside_system (a) within_system: The software failure incident related to the Tesla Model X keyless entry system vulnerability was primarily due to contributing factors that originated from within the system itself. Security researcher Lennert Wouters discovered vulnerabilities in both the Tesla Model X cars and their keyless entry fobs, which could be exploited by any car thief who manages to read a car's vehicle identification number and come within close proximity of the victim's key fob [107561]. The vulnerabilities included issues such as lack of code signing for key fob firmware updates, insecure pairing protocols, and lack of cryptographic signatures in the firmware update process, all of which were internal to the Tesla Model X keyless entry system [107600]. (b) outside_system: The software failure incident also had contributing factors that originated from outside the system. For example, the hardware kit necessary to exploit the vulnerabilities in the keyless entry system cost Wouters around $300 and could fit inside a backpack, allowing the attack to be carried out remotely from a distance [107561]. Additionally, the attack involved intercepting the car's actual key fob or the body control module in the car using a computer with a Bluetooth receiver, which could work from up to 50 feet away, indicating an external proximity factor [107602].
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident occurring due to non-human actions: - The software failure incident in the Tesla Model X keyless entry system was due to vulnerabilities in the key fobs and the lack of proper security measures in the firmware update process, allowing a hacker to exploit the system and steal a Model X in just a few minutes [107561, 107602, 107600]. - The vulnerabilities included the lack of cryptographic signatures in the firmware update process, insecure pairing protocols, and the ability to wirelessly compromise a key fob and take control over it, leading to unlocking and stealing the vehicle [107600]. (b) The software failure incident occurring due to human actions: - The security researcher, Lennert Wouters, discovered and demonstrated the vulnerabilities in the Tesla Model X keyless entry system, highlighting the flaws in the security design and implementation of the system [107561, 107602, 107600]. - Wouters informed Tesla about the hacking technique he developed, which exploited the vulnerabilities in the system, leading to the company planning to roll out software updates to address the issues [107561, 107602].
Dimension (Hardware/Software) hardware, software (a) The software failure incident occurring due to hardware: - The software failure incident reported in the articles is related to hardware vulnerabilities in the Tesla Model X's keyless entry system. A security researcher discovered vulnerabilities in both the Tesla Model X cars and their keyless entry fobs that could be exploited by car thieves. The hardware kit necessary to carry out the heist cost the researcher around $300 and included components like a Model X body control module, a disassembled key fob, a Raspberry Pi minicomputer, and a battery [107561]. - The vulnerability allowed the hacker to rewrite the firmware of a key fob via Bluetooth connection, extract a radio code that unlocks the owner's Model X, pair their own key fob with the victim's vehicle, and drive the car away. The hacker could exploit hardware components like the body control module (BCM) and the key fob to carry out the attack [107561]. - The hardware components used in the attack included a Raspberry Pi minicomputer, a secondhand Model X BCM, a key fob, a power converter, and a battery. The hacker could control these components wirelessly from inside a backpack, enabling them to input the car's VIN number, retrieve an unlock code, and pair a new key [107561]. (b) The software failure incident occurring due to software: - The software failure incident reported in the articles is related to software vulnerabilities in the Tesla Model X's keyless entry system. The vulnerabilities allowed a security researcher to exploit flaws in the key fob firmware updates and the pairing of new key fobs with the car. The lack of validation for key fob firmware updates and pairing new key fobs with the car were identified as software vulnerabilities that could be exploited [107602]. - The software vulnerabilities in the keyless entry system of the Model X included the lack of cryptographic signatures in the firmware update process and an insecure pairing protocol that allowed a modified key fob to be paired with the vehicle. The software in Tesla's key fobs could be updated without proper security measures to verify authenticity, leading to the vulnerability [107600].
Objective (Malicious/Non-malicious) malicious (a) The software failure incident reported in the articles is malicious in nature. Security researcher Lennert Wouters discovered vulnerabilities in the Tesla Model X's keyless entry system that could be exploited by hackers to steal a Model X in just a matter of minutes. The vulnerabilities allowed a hacker to rewrite the firmware of a key fob via Bluetooth connection, extract a radio code, pair their own key fob with the victim's vehicle, and drive the car away [107561, 107602, 107600]. (b) The software failure incident is non-malicious in the sense that the vulnerabilities were not intentionally introduced to harm the system. The flaws in the keyless entry system were not designed with malicious intent but were oversights in the security design and implementation of the system. Tesla is taking the findings seriously and plans to issue a patch to address the vulnerabilities [107602].
Intent (Poor/Accidental Decisions) poor_decisions (a) The intent of the software failure incident was poor_decisions. The incident involved vulnerabilities in Tesla Model X's keyless entry system that allowed a hacker to rewrite the firmware of a key fob via Bluetooth connection, extract an unlock code, pair their own key fob with the victim's vehicle, and drive the car away within minutes. The vulnerabilities were a result of poor decisions in the design and implementation of the keyless entry system, such as the lack of code signing for key fob firmware updates, insecure pairing protocols, and failure to validate key fob certificates, which allowed the hacker to exploit the system [107561, 107602, 107600].
Capability (Incompetence/Accidental) development_incompetence (a) The software failure incident occurring due to development incompetence: - The software failure incident involving Tesla Model X's keyless entry system was due to vulnerabilities in the system that were exploited by a security researcher, Lennert Wouters, highlighting a lack of professional competence in the design and implementation of the keyless entry system [107561, 107602]. - Wouters discovered security vulnerabilities in both Tesla Model X cars and their keyless entry fobs, which allowed a hacker to rewrite the firmware of a key fob via Bluetooth connection, extract an unlock code, pair their own key fob with the victim's vehicle, and drive the car away within minutes [107561]. - The vulnerabilities included the lack of "code signing" for key fob firmware updates, insecure pairing protocols, and the absence of cryptographic signatures in the firmware update process, indicating a failure in ensuring secure design and implementation practices [107561, 107600]. (b) The software failure incident occurring accidentally: - The software failure incident involving the Tesla Model X's keyless entry system was not accidental but rather a result of deliberate exploitation of vulnerabilities by a security researcher to demonstrate weaknesses in the system [107561, 107602]. - The vulnerabilities exploited by Wouters were not accidental but were intentionally identified and leveraged to showcase the security flaws in the Model X's keyless entry system [107561, 107602]. - The incident was a result of intentional research and testing by Wouters to uncover weaknesses in Tesla's keyless entry system, rather than accidental errors or faults in the system [107561, 107602].
Duration temporary (a) The software failure incident in the articles is temporary. The vulnerability in the Tesla Model X's keyless entry system that allowed hackers to steal a Model X was due to specific contributing factors introduced by certain circumstances, such as flaws in the key fob firmware update mechanism and insecure pairing protocols. Tesla was made aware of the vulnerabilities and is rolling out software updates to address the issue [Article 107561, Article 107602, Article 107600]. (b) The software failure incident is not permanent as Tesla is actively working on fixing the vulnerabilities through software updates for the key fobs and the car itself. The vulnerabilities were identified by security researchers, and Tesla is taking the findings seriously by issuing patches to prevent the exploitation of the vulnerabilities. This indicates that the software failure is not a permanent issue but rather a temporary one that can be mitigated through software updates [Article 107561, Article 107602, Article 107600].
Behaviour other (a) crash: The software failure incident in the articles does not involve a crash where the system loses state and does not perform any of its intended functions. The incident is more related to security vulnerabilities in Tesla's Model X keyless entry system that allow hackers to steal the vehicle [Article 107561, Article 107602, Article 107600]. (b) omission: The incident does not involve the system omitting to perform its intended functions at an instance(s). Instead, it revolves around security flaws that allow unauthorized access and theft of the vehicle [Article 107561, Article 107602, Article 107600]. (c) timing: The failure is not related to the system performing its intended functions correctly but too late or too early. It is more about exploiting vulnerabilities in the system to gain unauthorized access and control of the vehicle [Article 107561, Article 107602, Article 107600]. (d) value: The incident does not involve the system performing its intended functions incorrectly in terms of providing incorrect outputs or results. It is more about security weaknesses that allow unauthorized individuals to manipulate the system to steal the vehicle [Article 107561, Article 107602, Article 107600]. (e) byzantine: The incident does not exhibit the characteristics of a byzantine failure where the system behaves erroneously with inconsistent responses and interactions. It is primarily about security vulnerabilities that can be exploited to gain unauthorized access to the vehicle [Article 107561, Article 107602, Article 107600]. (f) other: The behavior of the software failure incident in the articles can be categorized as a security vulnerability exploit leading to unauthorized access and potential theft of the Tesla Model X vehicles. The incident involves exploiting flaws in the keyless entry system rather than a traditional software failure in terms of system malfunction or incorrect operation [Article 107561, Article 107602, Article 107600].

IoT System Layer

Layer Option Rationale
Perception processing_unit, network_communication, embedded_software (a) sensor: The software failure incident related to the Tesla Model X keyless entry system hack did not involve a sensor error. The vulnerabilities exploited by the hacker were primarily related to the key fobs and the keyless entry system, rather than sensor-related issues [107561, 107602, 107600]. (b) actuator: The incident did not involve an actuator error. The vulnerabilities exploited by the hacker did not directly involve any actuator components of the Tesla Model X [107561, 107602, 107600]. (c) processing_unit: The software failure incident did involve issues related to the processing unit of the Tesla Model X. The hacker was able to manipulate the processing unit, specifically the body control module (BCM), to perform actions like waking up the key fob's Bluetooth radio and pairing a rogue key fob with the vehicle [107561, 107602]. (d) network_communication: The incident also involved failures related to network communication. The hacker exploited vulnerabilities in the Bluetooth communication between the key fob, the car's BCM, and the hacker's computer to carry out the attack remotely [107561, 107602, 107600]. (e) embedded_software: The software failure incident was primarily related to vulnerabilities in the embedded software of the Tesla Model X key fobs. The lack of cryptographic signatures in the firmware update process and insecure pairing protocols were key factors that allowed the hacker to compromise the key fobs and gain control over them [107561, 107602, 107600].
Communication connectivity_level [a107561, a107602, a107600] The software failure incident related to the communication layer of the cyber physical system that failed was at the connectivity level. The vulnerability exploited in the Tesla Model X's keyless entry system involved flaws in the key fobs' firmware update mechanism and insecure pairing protocols, allowing a hacker to manipulate the key fob and gain unauthorized access to the vehicle [a107561]. The hack involved intercepting the key fob or the body control module in the car using a computer with a Bluetooth receiver, which could work from up to 50 feet away [a107602]. The lack of cryptographic signatures in the firmware update process and the insecure pairing protocol were key vulnerabilities that were exploited, indicating issues at the network or transport layer of the communication system [a107600].
Application TRUE The software failure incident reported in the provided articles was related to the application layer of the cyber physical system. The incident involved vulnerabilities in the Tesla Model X's keyless entry system that allowed a hacker to exploit flaws in the key fobs and the car's systems to steal a Model X within minutes. The vulnerabilities included issues with the key fob firmware updates lacking cryptographic signatures, an insecure pairing protocol allowing a modified key fob to be paired with the vehicle, and a lack of proper security in the key fob update mechanism, enabling wireless compromise of the key fob and gaining full control over it [107561, 107602, 107600].

Other Details

Category Option Rationale
Consequence property, theoretical_consequence (a) death: People lost their lives due to the software failure (b) harm: People were physically harmed due to the software failure (c) basic: People's access to food or shelter was impacted because of the software failure (d) property: People's material goods, money, or data was impacted due to the software failure (e) delay: People had to postpone an activity due to the software failure (f) non-human: Non-human entities were impacted due to the software failure (g) no_consequence: There were no real observed consequences of the software failure (h) theoretical_consequence: There were potential consequences discussed of the software failure that did not occur (i) other: Was there consequence(s) of the software failure not described in the (a to h) options? What is the other consequence(s)? The articles do not mention any consequences related to death, physical harm, impact on access to food or shelter, or impact on non-human entities due to the software failure incident. The main consequence discussed in the articles is related to property, where the vulnerability in Tesla Model X's keyless entry system could allow a hacker to steal a Model X in just a matter of minutes by exploiting security vulnerabilities in the key fobs and the car's systems [107561, 107602, 107600]. The potential consequences discussed include the ability of a hacker to steal a Tesla Model X by rewriting the firmware of a key fob, lifting an unlock code, and driving the car away [107561].
Domain transportation, utilities (a) The software failure incident reported in the articles is related to the transportation industry. The incident involves vulnerabilities in the Tesla Model X's keyless entry system, allowing hackers to steal a Model X in just a matter of minutes by exploiting security flaws in the key fobs and the car's systems [Article 107561, Article 107602, Article 107600]. (g) The failed system was intended to support the utilities industry. The incident involves the security vulnerabilities in the Tesla Model X's keyless entry system, which is a crucial component of the vehicle's functionality [Article 107561, Article 107602, Article 107600]. (m) The system failure is not related to any other industry outside of transportation and utilities, as the incident specifically pertains to the security vulnerabilities in the Tesla Model X's keyless entry system [Article 107561, Article 107602, Article 107600].

Sources

Back to List