Cloud Keyless Entry Authentication Against Rolljam Attacks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current keyless entry systems for vehicles are vulnerable to denial-of-service attacks and 'Rolljam' attacks, where synchronization between the key fob and vehicle can be lost, and attackers can intercept and reuse valid codes to gain unauthorized access.
Innovation Solution
A cloud-based keyless entry system that uses a random number transmitted to a cloud service for authentication, eliminating the need for synchronized codes and preventing code interception by using a cryptographic hash function to generate and verify unlock codes, ensuring only authorized access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If synchronized codes are used between key fob and vehicle for keyless entry, then ease of operation is improved, but reliability deteriorates due to vulnerability to Rolljam attacks and denial-of-service attacks
Solution Approach 1:
A cloud service acts as an intermediary between the vehicle and the remote entry device. The cloud service receives a random number from the vehicle, generates an unlock code, and communicates with the remote entry device to verify authentication. This intermediary eliminates the need for direct synchronized code exchange between vehicle and key fob, preventing Rolljam attacks while maintaining ease of operation.
Solution Approach 2:
The patent replaces the mechanical synchronization system (where key fob and vehicle maintain synchronized code sequences) with a cloud-based cryptographic system. Instead of relying on synchronized rolling codes, the system uses cloud-based hash function computation to generate and verify unlock codes, substituting the mechanical synchronization mechanism with a more secure information-theoretic approach.
2Ease of operation
If rolling codes are transmitted between key fob and vehicle, then ease of operation is improved, but object-affected harmful factors worsen due to code interception and replay attacks
Solution Approach 1:
The cloud service serves as a trusted intermediary that receives the random number from the vehicle and generates the unlock code. The remote entry device receives authentication verification from the cloud service rather than directly exchanging codes with the vehicle. This intermediary architecture prevents direct code transmission and eliminates the vulnerability to interception and replay attacks.
Solution Approach 2:
The patent converts the potential harm of code transmission into a benefit by using the random number as a seed for cryptographic hash function computation. Instead of transmitting sensitive unlock codes directly, the system transmits a harmless random number that the cloud service transforms into the actual unlock code through secure hash computation, making interception useless to attackers.
3Reliability
If cloud-based authentication with random numbers is used, then reliability is improved by preventing attacks, but device complexity increases due to cloud service integration
Solution Approach 1:
The cloud service acts as a centralized intermediary that handles the complex cryptographic operations. The vehicle and remote entry device maintain relatively simple local logic, while the cloud service performs the computationally intensive hash function computations and code generation. This distributes complexity to a dedicated intermediary system, making the overall architecture more manageable and secure.
Solution Approach 2:
The cloud service performs multiple functions: receiving random numbers from vehicles, generating unlock codes using hash functions, verifying authentication requests from remote entry devices, and managing the authentication protocol. This multi-functional intermediary consolidates complexity into a single system that serves all authentication needs, reducing the burden on individual components.
Data Source
AI summary
Systems and methods for cloud-based keyless entry are generally described. In some examples, a first number is received from a vehicle. A first computing device of the vehicle may be configured to control an electronic door lock. A first unlock code may be generated using the first number. In some examples, a notification is sent to a remote entry device associated with the vehicle. A response to the notification may be received from the remote entry device. In some examples, the first number may be retrieved from a messaging service based at least in part on the receiving the response to the notification. A second unlock code may be generated using the first number. A determination may be made that the first unlock code matches the second unlock code. An instruction may be sent to the first computing device, the instruction effective to cause unlock of the electronic door lock.