Automobile diagnosis interface testing method and device and medium

Abstract

The invention relates to an automobile diagnosis interface testing method and device and a medium, and belongs to the technical field of automobile testing. The method comprises the steps of obtaining a verification process of a to-be-tested automobile diagnosis interface; based on the verification process of the to-be-tested automobile diagnosis interface, searching a target process from a verification process template; detecting whether a cryptographic algorithm is involved in the target process or not; if the target process relates to the cryptographic algorithm, calling the cryptographic algorithm from a pre-written third-party library; acquiring a communication protocol of the to-be-tested automobile diagnosis interface; filling in communication protocol consistency part parameters; executing a test; if the successful response is not obtained, a test report is generated, and the test report records reasons causing the automobile diagnosis interface information to be unsafe. According to the invention, the test blank for the information security of the automobile diagnosis interface is filled. The information security of the automobile diagnosis interface is automatically tested.

Description

Technical Field

[0001] The present invention belongs to the technical field of automobile testing, and in particular relates to a method, device and medium for testing a cycling diagnostic interface. Background Art

[0002] The automotive diagnostic interface is an important diagnostic and debugging interface exposed on the vehicle side. With the advancement of automotive intelligence and networking, it has exposed huge information security risks. At present, there is a lack of standardized testing tools for testing the information security of automotive diagnostic interfaces. Summary of the invention

[0003] The present disclosure provides an automobile diagnostic interface testing method, device and medium to solve the above technical problems.

[0004] According to a first aspect of the present disclosure, a method for testing an automobile diagnostic interface is provided, the method comprising: obtaining a verification process of an automobile diagnostic interface to be tested; searching for a target process from a verification process template based on the verification process of the automobile diagnostic interface to be tested; detecting whether a cryptographic algorithm is involved in the target process; if the cryptographic algorithm is involved in the target process, calling the cryptographic algorithm from a pre-written third-party library; obtaining a communication protocol of the automobile diagnostic interface to be tested; filling in some parameters of the consistency of the communication protocol; executing a test; and generating a test report if no successful response is obtained, wherein the test report records the reasons causing the insecurity of the automobile diagnostic interface information.

[0005] In some embodiments, before detecting whether the target process involves a cryptographic algorithm, it also includes: detecting whether the target process involves a certificate parsing action; if the target process involves the certificate parsing action, directly calling a pre-written certificate parsing module.

[0006] In some embodiments, the cryptographic algorithm includes an encryption and decryption algorithm, a signature verification algorithm, and a digest algorithm.

[0007] In some embodiments, the verification process template includes a public key algorithm process and an encryption and decryption process.

[0008] According to a second aspect of the present disclosure, a vehicle diagnostic interface testing device is provided, comprising: a verification process acquisition module for obtaining a verification process of the vehicle diagnostic interface to be tested; a target process determination module for searching a target process from a verification process template based on the verification process of the vehicle diagnostic interface to be tested; a cryptographic algorithm judgment module for detecting whether a cryptographic algorithm is involved in the target process; a cryptographic algorithm calling module for calling a cryptographic algorithm from a pre-written third-party library if the target process involves the cryptographic algorithm; a communication protocol acquisition module for obtaining the communication protocol of the vehicle diagnostic interface to be tested; a parameter filling module for filling in some parameters of the communication protocol consistency; a test execution module for executing a test; and a test report generation module for generating a test report if no successful response is obtained, wherein the test report records the reasons for the insecurity of the vehicle diagnostic interface information.

[0009] According to a third aspect of the present disclosure, an automobile diagnostic interface testing device is provided, comprising: a memory; and a processor coupled to the memory, wherein the processor is configured to execute the automobile diagnostic interface testing method as described above based on instructions stored in the memory.

[0010] According to a fourth aspect of the present disclosure, a computer storable medium is provided, on which computer program instructions are stored, and when the instructions are executed by a processor, the above-mentioned automobile diagnostic interface testing method is implemented.

[0011] Beneficial effects of the present disclosure: The present disclosure fills the gap in testing the information security of the automobile diagnostic interface. The present disclosure automatically tests the information security of the automobile diagnostic interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0013] Figure 1 is a flow chart illustrating a method for testing an automotive diagnostic interface according to some embodiments of the present disclosure.

[0014] Figure 2 is a diagram showing a test system architecture according to some embodiments of the present disclosure.

[0015] Figure 3 FIG. 4 is a flowchart showing a test system execution according to some embodiments of the present disclosure.

[0016] Figure 4 is a block diagram illustrating an automotive diagnostic interface test device according to some embodiments of the present disclosure.

[0017] Figure 5is a block diagram showing an automobile diagnostic interface testing device according to other embodiments of the present disclosure.

[0018] Figure 6 is a block diagram illustrating a computer system according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0019] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that the relative arrangement of components and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure unless otherwise specifically stated.

[0020] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present disclosure, its application, or uses.

[0021] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered as part of the specification.

[0022] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0023] The automotive diagnostic interface is an important diagnostic and debugging interface exposed on the vehicle side. With the advancement of automotive intelligence and networking, it has exposed huge information security risks. At present, there is a lack of standardized testing tools for information security testing of automotive diagnostic interfaces, and manual packet capture and analysis are mostly used. The testing process is cumbersome, changeable, and has poor universality. In addition, the test results mostly rely on the inspection of testers, resulting in a lack of guarantee for the standardization and authority of the testing.

[0024] Existing testing methods require full human participation, analysis and decision-making. There are significant differences in testing methods for different test objects and test scenarios. The testing efficiency is low and the cost is high. It is difficult to universalize the testing methods, which makes the testing process cumbersome and the fairness and authority of the test results difficult to guarantee.

[0025] Based on the existing automotive diagnostic tool chain (representatively including Vector), the diagnostic connector manually performs relevant information security testing. For each test verification, the tester needs to adaptively edit the test script according to different test objects and solution characteristics, and send the script to the diagnostic connector through the PC to achieve communication with the vehicle.

[0026] Although there are mature automotive diagnostic tool chains in the field of automotive diagnostics (such as the Vector diagnostic tool chain), as common automotive diagnostic development / testing tools, they are all aimed at the general functional diagnostic field of automobiles and cannot effectively cover the branch of information security. There is no separate logic module to achieve fast and convenient verification of information security features such as "security authentication" and "cryptographic algorithm".

[0027] like Figure 1 As shown, the vehicle diagnostic interface testing method includes: step 110, obtaining a verification process of the vehicle diagnostic interface to be tested;

[0028] Step 120, based on the verification process of the automobile diagnostic interface to be tested, searching for a target process from a verification process template;

[0029] Step 130, detecting whether the target process involves a cryptographic algorithm;

[0030] Step 140, if the target process involves the cryptographic algorithm, calling the cryptographic algorithm from a pre-written third-party library;

[0031] Step 150, obtaining the communication protocol of the vehicle diagnostic interface to be tested;

[0032] Step 160, fill in the communication protocol consistency parameters;

[0033] Step 170, executing the test;

[0034] Step 180: If no successful response is obtained, a test report is generated, wherein the test report records the reasons that cause the vehicle diagnostic interface information to be insecure.

[0035] The system uses different diagnostic interface business ends to achieve protocol conversion and information interaction with the other end, so as to build a communication test environment that meets the requirements of the diagnostic interface access end / permit end; the system can automatically adapt different test scripts, cryptographic algorithms, communication protocols, etc. based on the established communication environment, so as to achieve identity authentication and authority control, identity authentication algorithm, and transmission data authenticity and integrity testing for the other business end; the system can automatically select test scripts, communication protocols, cryptographic algorithms and other modules according to the differences in test objects and simulated business ends, so as to meet the needs of different test scenarios.

[0036] like Figure 2 and Figure 3 As shown in the figure, the overall system is based on a mature vehicle bus analysis interface device, and specific test scripts are compiled for different business ends based on the CAPL scripting language of the interface device. At the same time, various encryption and decryption, signature verification, and digest algorithms are encoded into a third-party library to meet the algorithm requirements of different test scenarios.

[0037] The system is divided into functional modules, including the following functional modules: an interface device module, which is configured to connect to the vehicle diagnostic interface access / access terminal, protocol conversion, and information interaction.

[0038] The execution module is configured to convert between different vehicle communication protocols and receive / distribute messages.

[0039] The flow control module can automatically select test scripts, communication protocols, cryptographic algorithm libraries and other modules according to the test object and the simulated business end, to achieve automated testing for different test scenarios.

[0040] The cryptographic algorithm library integrates domestic and foreign standard cryptographic algorithms, including various stream encryption, symmetric encryption, asymmetric encryption, and summary and encoding algorithms.

[0041] The certificate parsing module is used to read various standard cryptographic certificates and customized certificate formats.

[0042] Verify process templates, which record common public key algorithms and encryption and decryption process templates. You can customize the selection process to increase versatility and reduce the development process of custom processes.

[0043] like Figure 3 As shown, the system is expected to perform the following steps: 1. Select a set of process templates from the verification process template module according to the verification process described by the provider of the device to be tested. 2. If the selected process involves cryptographic algorithms, specify the algorithm to be used from the cryptographic algorithm library. 3. Use the flow control module to fill in the parameters of the protocol consistency part according to the protocol provided by the party to be tested. 4. The execution module executes the test to see if the test is successful. 5. If it is found that there is no verification process in the verification process template module that meets the verification process of the device to be tested, use CAPL to write it according to the verification process of the device to be tested. During this period, the cryptographic algorithms and certificates involved can be directly called from the cryptographic algorithm module and the certificate parsing module.

[0044] This disclosure implements the management of verification templates and cryptographic algorithm libraries, and automatically issues test cases according to different test scenarios, enhancing the universality and authority of the test. It realizes full-process automated testing, reduces the manual processing of test personnel, improves test efficiency and the fairness and authority of test results. It fills the gap in detection tools in the field of automotive diagnostic interface information security.

[0045] The present disclosure is based on two-way diagnostic simulation, filling the gap in detection tools in the field of automobile diagnostic interface information security, and meeting the technical characteristics of "two-way authentication" and "asymmetric algorithm" involved in automobile diagnostic authentication in the current and future development mainstream.

[0046] The present disclosure can match the existing automobile diagnostic tool chain as a physical communication basis, and can universally match the existing diagnostic communication tools to reduce costs and difficulty of use.

[0047] like Figure 4 As shown, the automobile diagnostic interface testing device 400 includes a verification process acquisition module 410 to be tested, a target process determination module 420, a cryptographic algorithm judgment module 430, a cryptographic algorithm calling module 440, a communication protocol acquisition module 450, a parameter filling module 460, a test execution module 470, and a test report generation module 480.

[0048] The verification process acquisition module 410 is used to acquire the verification process of the automobile diagnostic interface to be tested;

[0049] A target process determination module 420 is used to search for a target process from a verification process template based on the verification process of the automobile diagnostic interface to be tested;

[0050] A cryptographic algorithm determination module 430 is used to detect whether a cryptographic algorithm is involved in the target process;

[0051] A cryptographic algorithm calling module 440 is used to call the cryptographic algorithm from a pre-written third-party library if the target process involves the cryptographic algorithm;

[0052] The communication protocol acquisition module 450 is used to acquire the communication protocol of the vehicle diagnostic interface to be tested;

[0053] Parameter filling module 460, used to fill in the communication protocol consistency parameters;

[0054] A test execution module 470, for executing a test;

[0055] The test report generating module 480 is used to generate a test report if no successful response is obtained, wherein the test report records the reasons causing the insecurity of the vehicle diagnostic interface information.

[0056] In the device of the embodiment of the present disclosure, the present disclosure fills the gap in the test of information security of the automobile diagnostic interface. The present disclosure automatically tests the information security of the automobile diagnostic interface.

[0057] like Figure 5 As shown, the vehicle diagnostic interface test device 500 includes a memory 510; and a processor 520 coupled to the memory 510. The memory 510 is used to store instructions for executing the corresponding embodiments of the vehicle diagnostic interface test method. The processor 520 is configured to execute the vehicle diagnostic interface test method in any of the embodiments of the present disclosure based on the instructions stored in the memory 510.

[0058] Figure 6is a block diagram showing a computer system for implementing some embodiments of the present disclosure. Figure 6 As shown, computer system 600 may be embodied in the form of a general purpose computing device. Computer system 600 includes memory 610, processor 620, and bus 630 that connects various system components.

[0059] The memory 610 may include, for example, a system memory, a non-volatile storage medium, etc. The system memory may store, for example, an operating system, an application program, a boot loader, and other programs. The system memory may include a volatile storage medium, such as a random access memory (RAM) and / or a cache memory. The non-volatile storage medium may store, for example, instructions for executing at least one corresponding embodiment of the automotive diagnostic interface test method. The non-volatile storage medium includes, but is not limited to, a disk memory, an optical memory, a flash memory, etc.

[0060] The processor 620 may be implemented by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistors, and other discrete hardware components. Accordingly, each module may be implemented by a central processing unit (CPU) running instructions in a memory that execute corresponding steps, or by a dedicated circuit that executes corresponding steps.

[0061] The bus 630 may use any of a variety of bus architectures, including, but not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, and a Peripheral Component Interconnect (PCI) bus.

[0062] The computer system 600 may also include an input / output interface 640, a network interface 650, a storage interface 660, etc. These interfaces 640, 650, 660, the memory 610, and the processor 620 may be connected via a bus 630. The input / output interface 640 may provide a connection interface for input / output devices such as a display, a mouse, and a keyboard. The network interface 650 may provide a connection interface for various networked devices. The storage interface 660 may provide a connection interface for external storage devices such as a floppy disk, a USB flash drive, and an SD card.

[0063] Here, various aspects of the present disclosure are described with reference to flowcharts and / or block diagrams of methods, devices, and computer program products according to embodiments of the present disclosure. It should be understood that each frame of the flowchart and / or block diagram and the combination of frames can be implemented by computer-readable program instructions.

[0064] These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable device to produce a machine, so that the processor executes the instructions to produce means for implementing the functions specified in one or more blocks in the flowchart and / or block diagram.

[0065] These computer-readable program instructions may also be stored in a computer-readable memory, which cause the computer to work in a specific manner to produce an article of manufacture, including instructions for implementing the functions specified in one or more blocks in the flowchart and / or block diagram.

[0066] The present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects.

[0067] The present disclosure fills the gap in the information security test for the automotive diagnostic interface. The present disclosure automatically tests the information security of the automotive diagnostic interface.

[0068] So far, the automotive diagnostic interface test method, device and medium according to the present disclosure have been described in detail. In order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed here.

[0069] Although some specific embodiments of the present disclosure have been described in detail by way of examples, it should be understood by those skilled in the art that the above examples are for illustration only and are not intended to limit the scope of the present disclosure. It should be understood by those skilled in the art that the above embodiments may be modified without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.

Claims

1. A method for testing an automobile diagnostic interface, characterized in that: The method comprises: Get the verification process of the vehicle diagnostic interface to be tested; Based on the verification process of the automotive diagnostic interface to be tested, searching for a target process from a verification process template; Detecting whether a cryptographic algorithm is involved in the target process; If the target process involves the cryptographic algorithm, the cryptographic algorithm is called from a pre-written third-party library; Obtain the communication protocol of the vehicle diagnostic interface to be tested; Fill in the parameters of the communication protocol consistency section; Execute the test; If no successful response is obtained, a test report is generated, wherein the test report records the reasons causing the insecurity of the vehicle diagnostic interface information.

2. The automobile diagnostic interface testing method according to claim 1, characterized in that: Before detecting whether a cryptographic algorithm is involved in the target process, the method further includes: Detecting whether the target process involves a certificate parsing action; If the target process involves the certificate parsing action, the pre-written certificate parsing module is directly called.

3. The automobile diagnostic interface testing method according to claim 1, characterized in that: The cryptographic algorithm includes an encryption and decryption algorithm, a signature verification algorithm, and a digest algorithm.

4. The automobile diagnostic interface testing method according to claim 1, characterized in that: The verification process template includes a public key algorithm process and an encryption and decryption process.

5. An automobile diagnostic interface test device, characterized in that: include: A module for obtaining the verification process to be tested, used to obtain the verification process of the diagnostic interface of the vehicle to be tested; A target process determination module, used to search for a target process from a verification process template based on the verification process of the automobile diagnostic interface to be tested; A cryptographic algorithm determination module, used to detect whether a cryptographic algorithm is involved in the target process; A cryptographic algorithm calling module, used to call the cryptographic algorithm from a pre-written third-party library if the target process involves the cryptographic algorithm; A communication protocol acquisition module, used to acquire the communication protocol of the vehicle diagnostic interface to be tested; Parameter filling module, used to fill in the parameters of the communication protocol consistency part; A test execution module, used to execute tests; The test report generation module is used to generate a test report if no successful response is obtained, wherein the test report records the reasons that cause the vehicle diagnostic interface information to be insecure.

6. An automobile diagnostic interface test device, characterized in that: include: Memory; as well as A processor coupled to the memory, wherein the processor is configured to execute the vehicle diagnostic interface testing method according to any one of claims 1 to 4 based on instructions stored in the memory.

7. A computer storable medium, characterized in that: Computer program instructions are stored thereon, and when the instructions are executed by a processor, the automobile diagnostic interface testing method as claimed in any one of claims 1 to 4 is implemented.

Images