Method, system, device and storage medium for preventing vehicle ADB from being maliciously used

Abstract

The present invention requests protection for a method and system for preventing the malicious use of the vehicle computer ADB. The web page login management unit uses the vehicle computer's TUID as a unique identifier, specifies the ADB to open the object, and feeds back the result to the background management control system. The background control system issues instructions according to the TBOX network status. For the online TBOX, it directly issues instructions to open the ADB, and the TBOX feeds back the execution of the instructions to the background control system. For the offline TBOX, the ADB task cache is opened and connected to the background management control system. When the TBOX is online, it automatically obtains and times the cached tasks. If it is not accepted within the predetermined time, the task is canceled. In the case where the old task is not accepted and a new task comes, the new task covers the old task. The vehicle end does not reserve an interface for soft-cutting ADB to prevent malicious use.

Description

Technical Field

[0001] The present invention belongs to the field of automobile control technology, and in particular relates to a technology for protecting an ADB of a vehicle computer. Background Art

[0002] ADB is a versatile command-line tool that allows users to communicate with devices, perform various device operations (such as installing and debugging applications), and run various commands on the device. People who use ADB should be developers and debuggers, not users.

[0003] Patent application number: CN202010493578.0, name: Debug interface management method, device and electronic device, describes a debug interface management method, which obtains a verification code through the communication number of the debug interface management function bound by the user, and matches the verification code to enable ADB. This method reflects the current common use of verification codes to ensure the legal acquisition of ADB permissions for use on the car computer. This method has the advantages of developing ADB permissions to users, so that users can also obtain verification codes by themselves, increasing security risks; without verifying the identity of the user, anyone can bind the device, and it cannot prevent malicious use; it requires the cooperation of the device side, background, user mobile phone or other communication equipment, involving many changes; using the verification code provided by the operator may involve charges, increasing cost consumption. Summary of the invention

[0004] The present invention aims at the problem that after the Android Debug Bridge (ADB) is opened to users in the prior art, it is impossible to effectively determine whether the user's identity is legal. Anyone can bind a number to obtain ADB, and a third party can obtain ADB to maliciously damage or obtain sensitive data. Therefore, a system and method for preventing the malicious use of the vehicle ADB are proposed, which adopts the vehicle internal communication and vehicle-cloud connection to ensure the internal communication security and realize the communication security between the vehicle end and the background.

[0005] Internal communication of the vehicle: The vehicle does not reserve an interface for soft-cutting ADB to prevent it from being discovered and used. Currently, most illegal use of the ADB port is because the developer has reserved a soft-cut interface. Once discovered, it may be used maliciously. In order to avoid the problem of malicious use and meet the needs of developers and debuggers, the soft-cutting ADB interface is directly cancelled and only remote opening is used. Among them, the module that actually controls ADB inside the vehicle is the module that controls the conversion between ADB and USB. For example, the multi-control unit MCU (multi control unit) inside the vehicle controls the conversion between ADB and the universal serial bus USB (Universal SerialBus). To ensure the security of internal transmission of the vehicle, after the vehicle receives the remote command, the communication module encrypts the conversion signal and transmits it to the MCU. The communication module and the MCU negotiate the communication key (such as a symmetric key, etc.) before data transmission, and the communication key needs to be encrypted for transmission. The specific process can be: the communication module randomly generates a communication key and uses the MCU public key to encrypt the communication key and send it to the MCU, and the MCU then uses its own private key to decrypt and obtain the communication key plaintext. After obtaining the communication key, both parties use the communication key for encryption and decryption. Car-cloud connection: The car-computer and backend communication uses HTTPS (TLS1.2 and above) to ensure the security of the communication process; a two-way authentication mechanism is used to ensure the legitimacy of the communication end. Specifically:

[0006] A method for preventing the malicious use of vehicle ADB, including: a web login management unit uses the vehicle TUID as a unique identifier, specifies the ADB to open the object, and feeds back the result to the background management control system. The background control system issues instructions according to the TBOX network status. For the online TBOX, it directly issues instructions to open ADB, and the TBOX feeds back the execution of the instructions to the background control system; for the offline TBOX, the ADB task cache is opened and connected to the background management control system. When the TBOX is online, it automatically obtains and times the cached tasks, and cancels the tasks if they are not accepted within the predetermined time. In the case where the old task is not accepted and a new task comes, the new task covers the old task.

[0007] Furthermore, the communication between the backend control management system and TBOX uses a two-way authentication method to confirm that both parties are trustworthy, and uses HTTPS to protect the communication channel.

[0008] Furthermore, when TBOX is online, TBOX determines the validity of the instructions sent by the background control system. If the instructions are valid, TBOX changes its initial state, HU keeps the USB routing open and accesses UCS to obtain new message content, returns to the task background to turn on the car computer ADB, and when no message signal is received from the car computer HU within the predetermined time, TBOX returns to the initial state; TBOX notifies the car computer to obtain new messages; the car computer obtains UCS from TBOX, accesses and obtains the task, and the car computer opens ADB and feeds back the processing results to the background control system.

[0009] Furthermore, when TBOX is not online, the vehicle computer starts for the first time and connects to the Internet to obtain UCS, opens ADB, automatically obtains UCS, accesses and obtains tasks, opens ADB, and automatically closes ADB when the vehicle computer is shut down.

[0010] Furthermore, if the preset time is exceeded, the message is automatically discarded and the timeout is recorded in the web management unit. When the HU is turned on and connected to the network for the first time, the UCS is automatically accessed to obtain the message content, the HU obtains the task, and the ADB is turned on.

[0011] The present invention also proposes a system for preventing a vehicle computer ADB from being used maliciously, comprising a web page login management unit, a background control system, a vehicle networking system TBOX (Telematics BOX), and a vehicle computer HU (vehicle entertainment system), wherein each part is connected by a wireless network, the web page login management unit implements login authority management, uses the TUID of the vehicle computer as a unique identifier, specifies an ADB opening object, and feeds back the result to the background management control system, the background control system sends instructions according to the TBOX network status, the HU implements USB connection, provides a hardware interface, obtains background instructions, and controls automatic closing of the ADB; for an online TBOX, an instruction is directly issued to open the ADB, and the TBOX feeds back the execution status of the instruction to the background control system; for an offline TBOX, an ADB task cache is opened and connected to the background management control system, and when the TBOX is online, the cached tasks are automatically obtained and timed, and the tasks are canceled if they are not accepted within a predetermined time; in the case where an old task is not accepted and a new task comes, the new task covers the old task.

[0012] .The present invention also requests protection for an electronic device, which includes: one or more processors; a memory; one or more applications, which are stored in the memory and configured to be loaded and run by the one or more processors to execute the method of preventing the malicious use of the vehicle ADB described in the present invention.

[0013] The present invention also seeks to protect a computer-readable storage medium having a computer program stored thereon, which can be loaded and run by a processor to implement the method of preventing the malicious use of the vehicle ADB as described in the present invention.

[0014] Web page login management unit, account login, verification code verification and other basic protection measures to prevent the web page from being used by anyone. At the same time, it is necessary to have a simple security detection and defense mechanism. If it is account password login, the password strength needs to be limited. At the same time, the login process is delayed or prohibited for multiple incorrect logins to prevent others from blasting, dictionary and other attacks to guess the password, thereby performing illegal operations. Web page passwords should not be stored or transmitted in plain text. The passwords need to be hashed or encrypted. The same mechanism is used to process the passwords entered by the user during login verification, and then verified with the stored value to avoid direct use of plain text password verification and prevent third parties from intercepting data to obtain passwords.

[0015] After completing the web login, enter the permission management. Use the terminal IDTUID (Terminal Unit Identity) of the vehicle computer as the unique identifier, specify the ADB to open the object, and feedback the result to the background control system.

[0016] The background control system issues instructions according to the network status of TBOX. TBOX includes two network statuses, online and offline. For online TBOX, instructions can be issued directly, and then the feedback from TBOX is used to determine whether the issuance is successful; for offline TBOX, ADB tasks are opened for caching and hung in the background control system. After TBOX goes online, it is automatically obtained and the cached tasks are timed. If they are not accepted within the scheduled time, the tasks are canceled. In the case where the old tasks are not accepted and new tasks are received, the new tasks should overwrite the old tasks. The communication process between the background control system and TBOX should use a two-way authentication method to confirm that both parties in communication are trustworthy, and use HTTPS to protect the communication channel to prevent third parties from forging, eavesdropping or tampering with the communication content.

[0017] After that, if after-sales personnel, customer service personnel, and security administrators need to call ADB, the security administrator will manage the ADB permission to enable it, and the security administrator will issue the ADB enablement command and related work to the corresponding vehicle computer.

[0018] Each end needs to implement the following functions: web page, realize UI interface display, realize ADB permission management visualization, and login identity authentication; the background management system realizes ADB command issuance, opens ADB task cache, receives administrator commands, and communicates securely with TBOX; TBOX realizes secure network communication and command validity judgment; HU realizes USB connection, hardware interface provision, automatically obtains background commands, and automatically closes ADB.

[0019] By closing ADB by default, malicious personnel are restricted from using the ADB of the vehicle computer, so that malicious personnel cannot obtain ADB through conventional means, thereby preventing ADB from being used maliciously. The web page uses identity authentication to log in to the ADB permission management interface, and adopts a more reliable identity authentication method to prevent illegal personnel from using it. From the background to the vehicle computer, security measures are added, such as https and message authentication, etc. These security mechanisms are used to improve the security of this method. Finally, corresponding roles are added for systematic management to complete the operation of the entire system. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 Remotely open the ADB overall relationship diagram;

[0021] Figure 2 Flowchart of opening ADB when TBOX is online;

[0022] Figure 3 Flowchart of opening ADB when TBOX is offline. DETAILED DESCRIPTION

[0023] In order to further understand the present invention, the implementation of the present invention is further described in detail below with reference to the accompanying drawings and specific examples.

[0024] Car-cloud connection: The server presets the terminal certificate and root certificate inside the car computer, and uses a symmetric key to encrypt and store the certificate, and stores the private key in the encryption module (SE or HSM). The communication module between the vehicle control system and the car computer uses the preset certificate and private key for two-way authentication, and uses the HTTPS protocol to ensure the security of the entire communication. Internal communication within the car computer: After receiving the command to open ADB, the communication module of the car computer negotiates the key with the MCU. The communication module uses the negotiated communication key to encrypt the command and transmits it to the multi-point control unit MCU (multi controlunit) through the serial peripheral interface SPI (Serial Peripheral Interface); after the MCU receives the command, the client uses the communication key to decrypt it, executes the decrypted command, and opens ADB.

[0025] The solution for remotely opening ADB may specifically include the following two situations: when TBOX is online, after the background control system issues the command to open ADB, TBOX judges the validity of the received command; if the command is valid, TBOX changes the initial state, the USB router continues to be turned on and accesses the domain name UCS for obtaining messages to obtain new message content. When the vehicle computer does not receive a successful message acquisition signal within the predetermined time, TBOX returns to the initial state; TBOX notifies the vehicle computer to obtain new messages; the vehicle computer obtains UCS from TBOX, accesses and obtains tasks; after obtaining, the vehicle computer successfully opens ADB and feeds back the processing results to the background control system. When TBOX is not online, the vehicle computer starts for the first time and connects to the Internet to obtain UCS and open ADB. After the vehicle computer is turned on and connected to the Internet, it automatically obtains UCS, then accesses and obtains tasks and opens ADB. The vehicle computer has the function of automatically closing ADB to prevent it from being used by others after authorized use. The following is a specific description of the online and offline situations of TBOX:

[0026] Open ADB when TBOX is online.

[0027] like Figure 2 The flowchart shown is for turning on ADB when TBOX is online. Send the start ADB command to check whether TBOX is online. If so, TBOX accepts the start command and verifies whether the command is valid. If so, keep the USB routing open and send a request signal. HU keeps the USB network and accesses UCS to obtain new message content. Return to the task background to turn on the vehicle ADB. HU immediately turns on the ADB mode after receiving the start command. If no confirmation signal is received from HU within the scheduled time, HU completes turning on ADB, automatically turns off after shutdown, and returns to the initial state, and the process ends.

[0028] If TBOX is online, open the ADB command cache. Specifically, the following steps are included: the server completes the authentication by using the account, password, verification code and other identity authentication methods, and remotely opens ADB according to the client's request to TUID; the server sends the ADB opening command to the vehicle control system; after receiving the request command, the vehicle control system determines whether TBOX is online. If TBOX is online, it will hang the adb opening task to HU (for example, specify a certain interface address as the new information storage address, and the vehicle computer obtains the task at this specific address to ensure that the vehicle computer can receive the task at a legal location) and send the "other terminal new message notification command" command to TBOX; after receiving the "other terminal new message notification command" command, TBOX determines whether the command is valid. If the command is invalid, TBOX feeds back the error code to the background, and the background feeds back to the web page. The page interface prompts the security administrator: setting failed; if valid, keep or change the USB routing channel to open (if the initial state of the USB routing channel is open, it remains unchanged; if the initial state is closed, it is changed to open) and send periodic request CAN messages to HU; after HU receives the message from TBOX, it connects to the router and accesses UCS to obtain the new message content; HU obtains the task (opens adb), if it does not obtain the task within the scheduled time t, it cannot connect to the background, because TBOX will recover after this time; after HU receives the data, it immediately opens ADB and feeds back the status message to TBOX; after TBOX receives the message from HU, it returns to the initial state; if TBOX does not receive the status message fed back by HU within t time, it will automatically return to the initial state;

[0029] Open ADB when TBOX is offline

[0030] like Figure 3 The figure shows the flow chart of opening ADB when TBOX is not online. When TBOX is not online, ADB is opened. HU actively connects to the network when it is turned on, accesses UCS to obtain new messages, and the background system returns the task and sends the command to open ADB on the vehicle. It is opened immediately after receiving the command to open ADB, and is automatically closed after being shut down.

[0031] The security administrator enters the login page, logs into the management unit to complete the authentication of account, password, verification code, etc., enters the permission management webpage, and remotely opens ADB according to the TUID notified by the customer service staff; after receiving the request from the login management unit, the background control system determines whether TBOX is online; if TBOX is not online, the background management control system feeds back the corresponding error code to the login management unit, and the login management unit prompts the security administrator that the setting failed and please detect HU failure. At the same time, the ADB task cache will be opened. The cache should have a task limit of a preset time. If it exceeds the preset time, it will be automatically discarded and the opening timeout will be recorded in the webpage management unit. After the HU is turned on and connected to the network for the first time, it will automatically access UCS to obtain the message content, HU obtains the task and opens ADB; after receiving the data, HU immediately opens ADB; other operations are the same as opening ADB when TBOX is online; when the old task is not issued and a new task is received, the new instruction should directly overwrite the old instruction.

Claims

1. A method for preventing vehicle ADB from being used maliciously, characterized in that: Including, the web login management unit uses the TUID of the vehicle computer as a unique identifier, cancels the soft-cut ADB interface, specifies the ADB opening object, and feeds back the ADB opening instruction to the background management control system. The background management control system issues instructions according to the TBOX network status. For the online TBOX, it directly issues instructions to open ADB, and TBOX feeds back the execution status of the instructions to the background control system; for the offline TBOX, the ADB task cache is opened and the task is attached to the background management control system. When the TBOX is online, it automatically obtains the ADB opening task cached in the background management control system and times the cached task. If it is not accepted within the scheduled time, the task is canceled. In the case where the old task is not accepted and a new task comes, the new task covers the old task. When TBOX is not online, the vehicle computer starts up and connects to the Internet for the first time, automatically obtains UCS, accesses and obtains tasks, opens ADB, and automatically closes ADB when the vehicle computer is shut down; If the cached task timing exceeds the scheduled time, the background management system automatically discards the task and records the start timeout in the web management unit. When the vehicle HU is turned on and connected to the network for the first time, it automatically obtains UCS, accesses and obtains the task, and opens ADB.

2. The method according to claim 1, characterized in that The communication between the backend control management system and TBOX uses two-way authentication to confirm that both parties are trustworthy, and uses HTTPS to protect the communication channel.

3. The method according to claim 1, characterized in that When TBOX is online, TBOX determines the validity of the command sent by the background control system. If the command is valid, TBOX changes its initial state, HU keeps USB routing open and accesses UCS to obtain new message content, returns to the task background to open the vehicle ADB, and returns to the initial state if no message signal is received from the vehicle HU within the predetermined time. TBOX notifies the vehicle computer to obtain new messages; the vehicle computer obtains UCS from TBOX, accesses and obtains tasks, and the vehicle computer opens ADB and feeds back the processing results to the background control system.

4. A system for preventing vehicle ADB from being used maliciously, characterized in that: It includes a web page login management unit, a background control system, TBOX, and a vehicle HU. Each part is connected by a wireless network. The web page login management unit implements login authority management, uses the vehicle HU's TUID as a unique identifier, specifies the ADB opening object, and feeds back the ADB opening command to the background management control system. The background control system sends commands according to the TBOX network status, and the vehicle HU realizes USB connection, provides hardware interface, obtains background commands, and controls the automatic closing of ADB. For the online TBOX, it directly sends commands to open ADB, and TBOX feeds back the command execution status to the background control system. For the offline TBOX, the ADB task cache will be opened, and the task will be hung on the background management control system. When the TBOX is online, it will automatically obtain and time the cached tasks, and cancel the tasks if they are not accepted within the scheduled time. In the case where the old tasks are not accepted and new tasks come, the new tasks cover the old tasks. When the TBOX is not online, the vehicle HU automatically obtains UCS for the first time when it is started and connected to the Internet, accesses and obtains tasks, opens ADB, and automatically closes ADB when the vehicle end is closed. If the cached task timing exceeds the scheduled time, the background management system automatically discards the task and records the start timeout in the web management unit. After the HU is turned on and connected to the network for the first time, it automatically obtains UCS, accesses and obtains the task, and opens ADB.

5. The system according to claim 4, characterized in that The communication between the backend control management system and TBOX uses two-way authentication to confirm that both parties are trustworthy, and uses HTTPS to protect the communication channel.

6. The system according to claim 4, characterized in that The vehicle computer does not reserve an interface for soft-cutting ADB. The conversion between ADB and USB is controlled by the MCU inside the vehicle computer. After the vehicle computer receives the remote command, the communication module encrypts the conversion signal and transmits it to the MCU. The communication module and the MCU use the negotiated communication key for data transmission.

7. An electronic device, characterized in that: The electronic device includes: one or more processors; a memory; and one or more applications, which are stored in the memory and configured to be loaded and run by the one or more processors to execute the method for preventing the malicious use of the vehicle ADB as described in any one of claims 1 to 3.

8. A computer-readable storage medium, characterized in that: A computer program is stored thereon, which can be loaded and run by a processor to execute the method for preventing the vehicle ADB from being maliciously used as described in any one of claims 1 to 3.

Images