Vehicle controller vulnerability management method, system, electronic device, storage medium

Abstract

The application provides a vehicle controller vulnerability management method, system, electronic equipment and storage medium, and the method comprises the following steps: acquiring suspected weaknesses related to a vehicle controller; verifying the suspected weaknesses through the vehicle controller, and acquiring first weaknesses after verification; performing attack feasibility analysis on the first weaknesses, screening out second weaknesses with attack feasibility greater than a first threshold as first vulnerabilities of the vehicle controller; performing risk analysis on the first vulnerabilities, screening out second vulnerabilities with risk greater than a second threshold as to-be-repaired vulnerabilities of the vehicle controller; and acquiring a corresponding first repair strategy for the second vulnerabilities and applying the first repair strategy to the vehicle controller. By collecting suspected weaknesses, forming vulnerability analysis on the vehicle controller, and performing corresponding vulnerability repair, automatic discovery of potential vulnerabilities of the vehicle controller and automatic repair strategies are realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of intelligent networked vehicles, and particularly relates to a vehicle controller vulnerability management method and system, an electronic device, and a storage medium. BACKGROUND

[0002] With the application of technologies such as the Internet, artificial intelligence, cloud computing, and big data, the degree of intelligence and networking of vehicles is increasingly high, and vehicles have become intelligent terminal devices in the era of Internet of Everything. Under the current background of intelligent networked vehicles, cases of vehicles being attacked due to information security vulnerabilities have been emerging in the past few years, and information security has become a basic requirement for intelligent networked vehicles.

[0003] In order to ensure the safety of intelligent networked vehicles, vulnerability management needs to be implemented on vehicle controllers to ensure that the safety risks of vehicles are within a controllable range and to reduce the possibility of vehicles being attacked.

[0004] The information disclosed in this BACKGROUND section is only intended to enhance the understanding of the general background of the present application, and should not be construed as recognition or implication that this information constitutes prior art that is known to those of ordinary skill in the art. SUMMARY

[0005] In view of the problems in the prior art, the present application provides a vehicle controller vulnerability management method and system, an electronic device, and a storage medium.

[0006] The present application provides a vehicle controller vulnerability management method, which comprises:

[0007] Obtaining suspected weaknesses related to a vehicle controller;

[0008] Verifying the suspected weaknesses through the vehicle controller, and obtaining first weaknesses after verification;

[0009] Performing attack feasibility analysis on the first weaknesses, and screening out second weaknesses with attack feasibility greater than a first threshold as first vulnerabilities of the vehicle controller;

[0010] Performing risk analysis on the first vulnerabilities, and screening out second vulnerabilities with risk greater than a second threshold as to-be-repaired vulnerabilities of the vehicle controller;

[0011] For the second vulnerabilities, obtaining corresponding first repair strategies and applying them to the vehicle controller.

[0012] According to the vehicle controller vulnerability management method provided by the present application, suspected weaknesses related to a vehicle controller are obtained, which comprises:

[0013] Obtaining internal source information and external source information related to a vehicle controller;

[0014] Based on the internal source information, extracting keywords, establishing a network security event trigger library;

[0015] Matching the external source information and the keywords in the network security event trigger library;

[0016] Based on the matched external source information, obtaining the suspected weakness.

[0017] According to the vehicle controller vulnerability management method provided by the application, the internal source information includes at least one of the following information related to the vehicle controller:

[0018] Threat analysis report, architecture design document, verification test report, penetration test report;

[0019] The external source information includes at least one of the following information related to the vehicle controller:

[0020] Weakness or vulnerability information of vehicle controller provided by original equipment manufacturer, commercial or non-commercial security information, external research security information.

[0021] According to the vehicle controller vulnerability management method provided by the application, for the first weakness, attack feasibility analysis is carried out, including:

[0022] Matching the first weakness with the weakness in the preset attack library, wherein the attack library is provided with a first association table of weakness and attack feasibility;

[0023] For the matched first weakness, based on the first association table, the attack feasibility corresponding to the matched first weakness is obtained;

[0024] For the first weakness that fails to match, after attack feasibility analysis, the first weakness that fails to match and the analysis result of its attack feasibility are updated into the first association table.

[0025] According to the vehicle controller vulnerability management method provided by the application, for the first vulnerability, risk analysis is carried out, including:

[0026] Matching the first vulnerability with the vulnerability in the preset risk library, wherein the risk library is provided with a second association table of vulnerability and risk;

[0027] For the matched first vulnerability, based on the second association table, the risk corresponding to the matched first vulnerability is obtained;

[0028] For the first vulnerability of the matching failure, after the risk analysis, the first vulnerability of the matching failure and the analysis result of the risk are updated into the second association table.

[0029] According to the vehicle controller vulnerability management method provided by the application, for the second vulnerability, a corresponding first repair strategy is obtained and applied to the vehicle controller, including:

[0030] The second vulnerability is matched with the vulnerabilities in the preset vulnerability library, wherein the third association table of the vulnerabilities and the first repair strategies is arranged in the vulnerability library;

[0031] For the second vulnerability of the matching success, based on the third association table, the first repair strategy corresponding to the second vulnerability of the matching success is obtained and applied to the vehicle controller;

[0032] For the second vulnerability of the matching failure, a corresponding repair strategy is obtained and applied to the vehicle controller, and the second vulnerability of the matching failure and the corresponding repair strategy are updated into the third association table.

[0033] According to the vehicle controller vulnerability management method provided by the application, for the first vulnerability, attack feasibility analysis is performed, and the second vulnerability with the attack feasibility greater than the first threshold is screened out as the first vulnerability of the vehicle controller, including:

[0034] The first vulnerability is matched with the vulnerabilities in the preset vulnerability repair library, wherein the fourth association table of the vulnerabilities and the second repair strategies is arranged in the vulnerability repair library;

[0035] For the first vulnerability of the matching success, based on the fourth association table, the second repair strategy corresponding to the first vulnerability of the matching success is obtained and applied to the vehicle controller;

[0036] For the first vulnerability of the matching failure, attack feasibility analysis is performed, and the second vulnerability with the attack feasibility greater than the first threshold is screened out as the first vulnerability of the vehicle controller.

[0037] The application also provides a vehicle controller vulnerability management system, the system comprises:

[0038] The acquisition module is used to acquire the suspected vulnerability related to the vehicle controller.

[0039] The verification module is used to verify the suspected vulnerability through the vehicle controller to obtain the first vulnerability after verification.

[0040] The attack feasibility analysis module is configured to perform attack feasibility analysis on the first weakness, and screen out a second weakness with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller;

[0041] The risk analysis module is configured to perform risk analysis on the first vulnerability, and screen out a second vulnerability with risk greater than a second threshold as a to-be-repaired vulnerability of the vehicle controller;

[0042] The repair module is configured to obtain a corresponding first repair strategy for the second vulnerability and apply the first repair strategy to the vehicle controller.

[0043] The present application also provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the vehicle controller vulnerability management method according to any one of the above.

[0044] The present application also provides a non-transitory computer-readable storage medium having a computer program stored thereon, wherein the computer program is executable on a processor to implement the steps of the vehicle controller vulnerability management method according to any one of the above.

[0045] The present application provides a vehicle controller vulnerability management method, system, electronic device, and storage medium, which collects suspected weaknesses, analyzes vulnerabilities of a vehicle controller, and performs corresponding vulnerability repair, automatically discovers potential vulnerabilities of a vehicle controller, and provides an automatic repair strategy, thereby improving the efficiency of vulnerability management and improving the safety of intelligent networked vehicles. BRIEF DESCRIPTION OF DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the present application or prior art, the following will briefly introduce the drawings needed in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor.

[0047] Figure 1 A flowchart of a vehicle controller vulnerability management method according to the present application;

[0048] Figure 2 A structural diagram of a vehicle controller vulnerability management system according to the present application;

[0049] Figure 3 A structural diagram of another vehicle controller vulnerability management system according to the present application;

[0050] Figure 4 An entity structure diagram of an electronic device according to the present application. DETAILED DESCRIPTION

[0051] In order to make the objects, technical solutions and advantages of the present application clearer, the technical solutions in the present application will be described clearly and completely below in conjunction with the drawings in the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0052] Before the specific embodiments are introduced, first, a plurality of terms involved in the present application are explained as follows.

[0053] Weakness, refers to a defect or feature that can lead to undesirable behavior, the defect can be an outdated cryptographic algorithm or an insecure communication protocol, etc.

[0054] Vulnerability, refers to a weakness that can be exploited as part of an attack path.

[0055] Cybersecurity event, refers to cybersecurity information related to components of a vehicle controller.

[0056] The vehicle controller vulnerability management method provided by the embodiments of the present application will be described in detail below in conjunction with the drawings, specific embodiments and application scenarios.

[0057] Figure 1 A flowchart of a vehicle controller vulnerability management method provided by the present application is shown in FIG. 1, the vehicle controller vulnerability management method provided by the present application can include the following steps. Figure 1

[0058] Preferably, the embodiments of the present application are applied to a server in the cloud, and the server in the cloud is connected with a vehicle controller on a real vehicle.

[0059] Preferably, the embodiments of the present application are applicable to a stage of testing a vehicle by a vehicle manufacturer, and the entire vulnerability management method is realized through program codes in the cloud.

[0060] Further, the embodiments of the present application are applied to vulnerability management of a vehicle controller of an autonomous vehicle.

[0061] S100, acquiring suspected weaknesses related to a vehicle controller.

[0062] Optionally, acquiring suspected weaknesses related to a vehicle controller includes:

[0063] Acquiring internal source information and external source information related to the vehicle controller;

[0064] Based on the internal source information, extracting keywords, and establishing a cybersecurity event trigger library;​

[0065] matching the external source information with the keywords in the cyber security event trigger library;

[0066] based on the matched external source information, obtaining suspected vulnerabilities

[0067] Preferably, the cloud server obtains the internal source information and the external source information related to the vehicle controller through the Internet and / or manual copying.

[0068] Preferably, the keywords extracted by the cyber security event trigger library include the component name of the vehicle controller, the encryption algorithm type, the function of the vehicle controller, the communication protocol, etc.

[0069] Optionally, the internal source information includes at least one of the following information related to the vehicle controller:

[0070] threat analysis reports, architecture design documents, verification test reports, penetration test reports;

[0071] The external source information includes at least one of the following information related to the vehicle controller:

[0072] weakness or vulnerability information of the vehicle controller provided by the original equipment manufacturer or the supplier, commercial or non-commercial security information, external research security information.

[0073] Preferably, the commercial or non-commercial security information includes vulnerability information published by a vulnerability platform, and the external research security information includes a penetration test white paper.

[0074] Preferably, the internal source information is the network security information related to the vehicle controller found by the vehicle manufacturer when testing the vehicle, so that when the test finds the weaknesses and vulnerabilities, they are directly regularized in specific files for easy access.

[0075] Preferably, the external source information is the network security information related to the vehicle controller found by a test subject other than the vehicle manufacturer, so that in addition to the regularized weaknesses and vulnerabilities (which are easily accessible by the test module of the vehicle manufacturer) in the external source information, there may be some non-regularized (relative to the vehicle manufacturer) weaknesses and vulnerabilities information.

[0076] S200, verifying the suspected vulnerabilities through the vehicle controller to obtain the first weakness after verification.

[0077] Preferably, the weakness is verified by the vehicle controller of the real vehicle in the test stage. Further, the SSH server is deployed on the vehicle side to realize the above verification.

[0078] Preferably, the vulnerability is verified by a vehicle controller of the simulation system, and a software environment of the simulation system is consistent with a real vehicle software environment for vulnerability discovery.

[0079] S300, for the first vulnerability, performing attack feasibility analysis, screening out a second vulnerability with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller;

[0080] Optionally, for the first vulnerability, performing attack feasibility analysis, screening out a second vulnerability with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller, comprising:

[0081] Matching the first vulnerability with a vulnerability in a preset vulnerability repair library, wherein the vulnerability repair library is provided with a fourth association table of vulnerabilities and second repair strategies;

[0082] For the matched first vulnerability, based on the fourth association table, obtaining the second repair strategy corresponding to the matched first vulnerability and applying it to the vehicle controller;

[0083] For the matched first vulnerability, performing attack feasibility analysis, screening out a second vulnerability with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller.

[0084] It should be noted that if the first vulnerability can find a matched repair strategy, the subsequent attack feasibility analysis is no longer performed, and the vulnerability can be repaired directly.

[0085] Optionally, for the first vulnerability, performing attack feasibility analysis, comprising:

[0086] Matching the first vulnerability with a vulnerability in a preset attack library, wherein the attack library is provided with a first association table of vulnerabilities and attack feasibilities;

[0087] For the matched first vulnerability, based on the first association table, obtaining the attack feasibility corresponding to the matched first vulnerability;

[0088] For the matched first vulnerability, after attack feasibility analysis, updating the matched first vulnerability and the analysis result of its attack feasibility into the first association table.

[0089] It should be noted that for the matched first vulnerability, performing attack feasibility analysis can be through an input device to obtain input information of a cloud server, the input information including expert input attack feasibility analysis, or through another attack feasibility analysis program to obtain the value of attack feasibility of the vulnerability.

[0090] Further, as a method of the analysis procedure, comprising: firstly analyzing whether the attack path exists, if yes, then analyzing the value of the attack feasibility, if no, then directly giving the result (i.e. the weakness cannot be exploited to become a vulnerability); for the weakness with the attack path, analyzing the value of the attack feasibility. Specifically, the attack feasibility value analysis method can refer to the attack feasibility evaluation method in the threat analysis and risk assessment (Tara), and the value X of the attack feasibility is given. The value X of the attack feasibility and the weakness are updated into the first association table.

[0091] S400, for the first vulnerability, performing risk analysis, screening out a second vulnerability with a risk greater than a second threshold value as a to-be-repaired vulnerability of the vehicle controller;

[0092] Optionally, for the first vulnerability, the risk analysis comprises:

[0093] The first vulnerability is matched with the vulnerabilities in the preset risk library, wherein the second association table of the vulnerabilities and the risks is set in the risk library;

[0094] For the first vulnerability matched successfully, the risk corresponding to the first vulnerability matched successfully is obtained based on the second association table;

[0095] For the first vulnerability matched unsuccessfully, the analysis result of the first vulnerability matched unsuccessfully and the risk is updated into the second association table after the risk analysis.

[0096] It should be noted that, for the first vulnerability matched unsuccessfully, the risk analysis can be performed by inputting the input information of the cloud server through the input device, and the input information comprises the risk analysis input by an expert, or the risk value of the weakness can be obtained through another risk analysis procedure.

[0097] S500, for the second vulnerability, obtaining the corresponding first repair strategy and applying to the vehicle controller.

[0098] Optionally, for the second vulnerability, obtaining the corresponding first repair strategy and applying to the vehicle controller comprises:

[0099] The second vulnerability is matched with the vulnerabilities in the preset vulnerability library, wherein the third association table of the vulnerabilities and the first repair strategy is set in the vulnerability library;

[0100] For the second vulnerability matched successfully, the first repair strategy corresponding to the second vulnerability matched successfully is obtained based on the third association table and applied to the vehicle controller;

[0101] For the second vulnerability of the matching failure, the corresponding repair strategy is obtained and applied to the vehicle controller, and the second vulnerability of the matching failure and the corresponding repair strategy are updated into the third association table.

[0102] It should be noted that for the second vulnerability of the matching failure, the corresponding repair strategy can be obtained by inputting the input information of the cloud server through the input device, which includes the repair strategy input by the expert, or by another repair strategy program.

[0103] The embodiment of the application collects suspected vulnerabilities, forms vulnerability analysis about the vehicle controller, and performs corresponding vulnerability repair, realizes automatic discovery of potential vulnerabilities of the vehicle controller and gives automatic repair strategy, so that the management efficiency of the vulnerability is improved, thereby improving the safety of the intelligent networked vehicle.

[0104] The vehicle controller vulnerability management system provided by the application is described below, and the vehicle controller vulnerability management system described below can be correspondingly referred to the vehicle controller vulnerability management method described above.

[0105] Figure 2 The structure diagram of the vehicle controller vulnerability management system provided by the application is shown in Figure 2 The application also provides a vehicle controller vulnerability management system, which comprises:

[0106] The acquisition module is used to acquire suspected vulnerabilities related to the vehicle controller.

[0107] The verification module is used to verify the suspected vulnerabilities through the vehicle controller, and acquire the first vulnerability after verification.

[0108] The attack feasibility analysis module is used to analyze the attack feasibility of the first vulnerability, and screen out the second vulnerability with attack feasibility greater than the first threshold as the first vulnerability of the vehicle controller.

[0109] The risk analysis module is used to analyze the risk of the first vulnerability, and screen out the second vulnerability with risk greater than the second threshold as the to-be-repaired vulnerability of the vehicle controller.

[0110] The repair module is used to acquire the corresponding first repair strategy for the second vulnerability and apply it to the vehicle controller.

[0111] The embodiment of the application collects suspected vulnerabilities, forms vulnerability analysis about the vehicle controller, and performs corresponding vulnerability repair, realizes automatic discovery of potential vulnerabilities of the vehicle controller and gives automatic repair strategy, so that the management efficiency of the vulnerability is improved, thereby improving the safety of the intelligent networked vehicle.

[0112] Figure 3Another structural schematic diagram of a vehicle controller vulnerability management system provided by the present application is shown in Figure 3 The vulnerability management system designed in the present scheme is realized by 4 modules and 5 libraries, and specifically includes: a network security information collection module, a vulnerability processing module, a vulnerability analysis module, a vulnerability management module, a network security event trigger library, a vulnerability repair library, an attack library, a risk library, and a vulnerability library.

[0113] The network security information collection module needs to obtain network security information, including internal source information and external source information of products. The vulnerability information collected from the internal source information or the external source information needs to be directly transmitted to the vulnerability processing module; the vulnerability information collected from the internal source information or the external source information needs to be directly transmitted to the risk analysis module. For other external source information, it needs to be matched with the keywords in the network security event trigger library. The network security information collection module obtains the external source information that is identified by security evaluation and matched with the keywords in the network security event trigger library, takes the external source information as a suspected vulnerability, and transmits the suspected vulnerability to the vulnerability processing module.

[0114] The vulnerability processing module collects the suspected vulnerability transmitted from the network security information collection module, then calls an automated test script to perform testing inside the vehicle controller, and verifies the authenticity of the suspected vulnerability existing inside the vehicle controller. For the suspected vulnerability that passes the verification, the vulnerability repair library needs to be called for matching to find out whether there is an existing repair strategy for the vulnerability. If there is, the user can be reminded to directly repair; if not, the vulnerability needs to be transmitted to the vulnerability analysis module.

[0115] The main function of the vulnerability analysis module is to analyze the attack feasibility of the vulnerability. When the analysis result shows that the vulnerability can be exploited to become a vulnerability, vulnerability management needs to be performed, otherwise, no repair is needed. Therefore, the vulnerability analysis module will first collect the vulnerability from the vulnerability processing module, then call the attack library to match the vulnerability information, and if the matching is passed, the attack feasibility analysis result will be given. If the matching is not passed, an expert will analyze the attack feasibility, and then the vulnerability analysis module will update the vulnerability information and the feasibility analysis result to the attack library. Specifically, the attack feasibility can be analyzed from the following two aspects: firstly, whether the attack path exists is analyzed. If the attack path exists, the value of the attack feasibility is analyzed. If the attack path does not exist, the result is directly given (i.e., the vulnerability cannot be exploited to become a vulnerability). For the vulnerability with the existing attack path, the value of the attack feasibility is analyzed. The analysis method can refer to the method of attack feasibility in Threat Analysis and Risk Assessment (Tara), and the value X of the attack feasibility is given.

[0116] When the value X of the attack feasibility is less than X1 (X1 can be deduced reversely by the acceptable risk value), the weakness cannot be exploited as a vulnerability, and when the value X of the attack feasibility is greater than or equal to X1, the weakness can be determined as a vulnerability, and it is necessary to jump to the vulnerability management module for processing.

[0117] The vulnerability management module first obtains the vulnerability information from the network security information collection module and the vulnerability analysis module, matches the vulnerability information with the vulnerability information in the risk library, and if the matching passes, completes the risk analysis, and gives the risk value Y of the vulnerability; for the vulnerability that does not pass the matching, the expert must analyze and give the risk value Y, and the risk assessment method can refer to the method in Threat Analysis and Risk Assessment (Tara), and the vulnerability information and the risk value are updated to the risk library. The risk value Y1 is the acceptable risk value of the vehicle controller, and the vulnerability management module must screen out the vulnerability with the risk value greater than Y1, and match with the vulnerability information in the vulnerability library, if it is an existing vulnerability, directly give the repair strategy, if the matching does not pass, the expert must give the repair strategy, and the vulnerability information and the repair strategy are updated to the vulnerability library.

[0118] It should be noted that the risk analysis and attack feasibility analysis realized by the expert can also be realized by the existing program. After continuous test iteration, each library is perfected, the whole system can realize overall full automation, and the expert experience is no longer needed, and full-automatic vulnerability management is realized.

[0119] Figure 4 An electronic device provided by the present application provides an entity structure schematic diagram of an electronic device, as shown in Figure 4 The electronic device can include a processor 410, a communications interface 420, a memory 430 and a communications bus 440, wherein the processor 410, the communications interface 420 and the memory 430 complete mutual communication through the communications bus 440. The processor 410 can call the logical instructions in the memory 430 to execute the vehicle controller vulnerability management method, and the method comprises:

[0120] Obtaining a suspected weakness related to a vehicle controller;

[0121] Verifying the suspected weakness through the vehicle controller to obtain a first weakness after verification;

[0122] Performing attack feasibility analysis on the first weakness, screening out a second weakness with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller;

[0123] For the first vulnerability, a risk analysis is performed, and a second vulnerability with a risk greater than a second threshold is screened out as a to-be-repaired vulnerability of the vehicle controller;

[0124] For the second vulnerability, a corresponding first repair strategy is obtained and applied to the vehicle controller.

[0125] In addition, the logical instructions in the memory 430 described above can be implemented in the form of a software function unit and sold or used as an independent product, and can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the part that contributes to the prior art or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0126] On the other hand, the present application also provides a computer program product, which comprises a computer program stored on a non-transitory computer readable storage medium, and the computer program comprises program instructions, when the program instructions are executed by a computer, the computer can execute the vehicle controller vulnerability management method provided by the above-mentioned method, and the method comprises:

[0127] Obtaining a suspected weakness related to the vehicle controller;

[0128] For the suspected weakness, verification is performed through the vehicle controller, and a first weakness after verification is passed;

[0129] For the first weakness, an attack feasibility analysis is performed, and a second weakness with an attack feasibility greater than a first threshold is screened out as a first vulnerability of the vehicle controller;

[0130] For the first vulnerability, a risk analysis is performed, and a second vulnerability with a risk greater than a second threshold is screened out as a to-be-repaired vulnerability of the vehicle controller;

[0131] For the second vulnerability, a corresponding first repair strategy is obtained and applied to the vehicle controller.

[0132] In yet another aspect, the present application also provides a non-transitory computer readable storage medium having stored thereon a computer program, which, when executed by a processor, implements the vehicle controller vulnerability management method provided above, the method comprising:

[0133] obtaining a suspected weakness related to a vehicle controller;

[0134] verifying the suspected weakness through the vehicle controller, and obtaining a first weakness after verification;

[0135] performing attack feasibility analysis on the first weakness, and screening out a second weakness with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller;

[0136] performing risk analysis on the first vulnerability, and screening out a second vulnerability with risk greater than a second threshold as a to-be-repaired vulnerability of the vehicle controller;

[0137] obtaining a corresponding first repair strategy for the second vulnerability and applying it to the vehicle controller.

[0138] The device embodiments described above are only schematic, wherein the units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the present embodiment. Those skilled in the art can understand and implement it without creative labor.

[0139] From the above description of the embodiments, those skilled in the art can clearly understand that the embodiments can be implemented by means of software plus necessary universal hardware platforms, and of course can also be implemented by hardware. Based on such understanding, the above technical solutions, essentially or in other words, the part that contributes to the prior art, can be embodied in the form of a software product, which can be stored in a computer readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute the methods described in each embodiment or some parts of the embodiments.

[0140] It should be pointed out finally that the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit the same; and although the present application has been described in detail with reference to the foregoing embodiments, it should be appreciated by those skilled in the art that the technical solutions recorded in the foregoing embodiments can be modified, or some technical features thereof can be replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A vehicle controller vulnerability management method, characterized by, The method comprises: Obtaining a suspected weakness related to a vehicle controller; Verifying the suspected weakness through the vehicle controller to obtain a first weakness after verification; Performing attack feasibility analysis on the first weakness to filter out a second weakness with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller; Performing risk analysis on the first vulnerability to filter out a second vulnerability with risk greater than a second threshold as a to-be-repaired vulnerability of the vehicle controller; Obtaining a corresponding first repair strategy for the second vulnerability and applying it to the vehicle controller; The attack feasibility analysis on the first weakness comprises: Matching the first weakness with a weakness in a preset attack library, wherein the attack library is provided with a first association table of weaknesses and attack feasibility; For the first weakness that matches successfully, obtaining the attack feasibility corresponding to the first weakness that matches successfully based on the first association table; For the first weakness that matches unsuccessfully, updating the first weakness that matches unsuccessfully and the analysis result of its attack feasibility into the first association table after attack feasibility analysis; The risk analysis on the first vulnerability comprises: Matching the first vulnerability with a vulnerability in a preset risk library, wherein the risk library is provided with a second association table of vulnerabilities and risks; For the first vulnerability that matches successfully, obtaining the risk corresponding to the first vulnerability that matches successfully based on the second association table; For the first vulnerability that matches unsuccessfully, updating the first vulnerability that matches unsuccessfully and the analysis result of its risk into the second association table after risk analysis; The attack feasibility analysis on the first weakness to filter out a second weakness with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller comprises: Matching the first weakness with a weakness in a preset weakness repair library, wherein the weakness repair library is provided with a fourth association table of weaknesses and second repair strategies; For the first weakness that matches successfully, obtaining the second repair strategy corresponding to the first weakness that matches successfully based on the fourth association table and applying it to the vehicle controller; For the first weakness that matches unsuccessfully, performing attack feasibility analysis to filter out a second weakness with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller.

2. The vehicle controller vulnerability management method of claim 1, wherein, Obtaining a suspected weakness related to a vehicle controller comprises: Obtaining internal source information and external source information related to the vehicle controller; Based on the internal source information, extracting keywords and establishing a network security event trigger library; Matching the external source information with the keywords in the network security event trigger library; Based on the matched external source information, obtaining the suspected weakness.

3. The vehicle controller vulnerability management method of claim 2, wherein, The internal source information comprises at least one of the following information related to the vehicle controller: Threat analysis report, architecture design document, verification test report, penetration test report; The external source information comprises at least one of the following information related to the vehicle controller: Weakness or vulnerability information of a vehicle controller provided by an original equipment manufacturer, commercial or non-commercial security information, external research security information.

4. The vehicle controller vulnerability management method of claim 1, wherein, For the second vulnerability, a corresponding first repair strategy is obtained and applied to the vehicle controller, including: Matching the second vulnerability with vulnerabilities in a preset vulnerability library, wherein a third association table of vulnerabilities and first repair strategies is provided in the vulnerability library; For the second vulnerability that is successfully matched, a first repair strategy corresponding to the second vulnerability that is successfully matched is obtained based on the third association table and applied to the vehicle controller; For the second vulnerability that fails to be matched, a corresponding repair strategy is obtained and applied to the vehicle controller, and the second vulnerability that fails to be matched and the corresponding repair strategy are updated into the third association table.

5. A vehicle controller vulnerability management system, characterized by, The system comprises: An acquisition module configured to acquire a suspected weakness related to a vehicle controller; A verification module configured to verify the suspected weakness through the vehicle controller to obtain a first weakness that passes the verification; An attack feasibility analysis module configured to perform attack feasibility analysis on the first weakness to filter out a second weakness with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller, including: matching the first weakness with weaknesses in a preset attack library, wherein a first association table of weaknesses and attack feasibilities is provided in the attack library; for the first weakness that is successfully matched, attack feasibility corresponding to the first weakness that is successfully matched is obtained based on the first association table; for the first weakness that fails to be matched, the first weakness that fails to be matched and an analysis result of attack feasibility are updated into the first association table after attack feasibility analysis; the attack feasibility analysis on the first weakness to filter out a second weakness with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller includes: matching the first weakness with weaknesses in a preset weakness repair library, wherein a fourth association table of weaknesses and second repair strategies is provided in the weakness repair library; for the first weakness that is successfully matched, the second repair strategy corresponding to the first weakness that is successfully matched is obtained based on the fourth association table and applied to the vehicle controller; for the first weakness that fails to be matched, attack feasibility analysis is performed to filter out a second weakness with attack feasibility greater than a first threshold as a first vulnerability of the vehicle controller. The risk analysis module is configured to perform risk analysis on the first vulnerability, and screen out a second vulnerability with a risk greater than a second threshold as a to-be-repaired vulnerability of the vehicle controller, wherein the risk analysis on the first vulnerability comprises: matching the first vulnerability with a vulnerability in a preset risk library, wherein the risk library is provided with a second association table of vulnerabilities and risks; for a first vulnerability with a successful match, obtaining a risk corresponding to the first vulnerability with the successful match based on the second association table; and for a first vulnerability with a failed match, updating the first vulnerability with the failed match and an analysis result of the risk of the first vulnerability with the failed match into the second association table after performing risk analysis; The repair module is configured to obtain a corresponding first repair strategy for the second vulnerability and apply the first repair strategy to the vehicle controller.

6. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor implements the steps of the vehicle controller vulnerability management method according to any one of claims 1-4 when executing the program.

7. A non-transitory computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program implements the steps of the vehicle controller vulnerability management method according to any one of claims 1-4 when executed by the processor.

Images