Cloud Keyless Entry Verification Against Rolljam and DoS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing keyless entry systems for vehicles are vulnerable to denial-of-service (DoS) attacks and 'Rolljam' attacks, where synchronization between the key fob and the vehicle can be lost, and attackers can intercept and replay valid codes to gain unauthorized access.
Innovation Solution
A cloud-based keyless entry system that generates a random number and uses a cryptographic function to create an unlock code, which is stored in a data store associated with the vehicle. The system sends a notification to the key fob, which authenticates and retrieves the number from a messaging service, generating a second unlock code for comparison with the first. If the codes match, the system sends an instruction to unlock the vehicle door.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional keyless entry systems use synchronized code transmission between key fob and vehicle, then keyless entry functionality is achieved, but the system becomes vulnerable to DoS attacks and Rolljam attacks where attackers can intercept and replay valid codes
Solution Approach 1:
The patent introduces a cloud service as an intermediary between the vehicle and remote entry device. The cloud service receives a first number from the vehicle, generates an unlock code, stores it, and later retrieves it after receiving a response from the remote entry device. This intermediary architecture eliminates direct code transmission between vehicle and key fob, preventing DoS and Rolljam attacks while maintaining keyless entry functionality.
2Reliability
If synchronization is maintained between key fob and vehicle for code generation, then unlock functionality works reliably, but attackers can exploit synchronization to perform replay attacks
Solution Approach 1:
The patent extracts the code generation and verification process from the direct vehicle-key fob communication path and relocates it to a cloud service. The vehicle sends only a first number to the cloud, and the remote entry device communicates with the cloud to retrieve and verify the unlock code. This extraction removes the synchronization mechanism that attackers could exploit for replay attacks, while maintaining reliable unlock functionality through cloud-mediated verification.
3Productivity
If unlock codes are transmitted directly between vehicle and key fob, then keyless entry is efficient, but the transmission of valid codes creates security vulnerabilities
Solution Approach 1:
The cloud service acts as an intermediary that generates and manages unlock codes, preventing direct code transmission between vehicle and key fob. The vehicle sends a first number to the cloud, which generates and stores an unlock code. The remote entry device communicates with the cloud to retrieve and verify the code. This intermediary approach maintains efficient keyless entry while eliminating the security vulnerability of direct code transmission.
4Reliability
If a cloud-based system with code generation and verification is implemented, then security against replay attacks is enhanced, but the system complexity and communication overhead increase
Solution Approach 1:
The patent implements a cloud service as an intermediary that centralizes code generation, storage, and verification functions. The vehicle communicates with the cloud to send a first number and receive verification, while the remote entry device communicates with the cloud to retrieve and verify unlock codes. This intermediary architecture enhances security against replay attacks by eliminating direct code transmission, while the cloud service manages the complexity of code generation and verification logic.
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.