Method, system and terminal for analyzing CVE vulnerability report
By organizing the CVE vulnerability history into a table and comparing it with the latest report using a Python script, new vulnerabilities are automatically discovered, solving the problems of low analysis efficiency and omissions in existing technologies, and achieving efficient CVE vulnerability analysis.
Patent Information
- Application Number
- CN202411024071.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-29
- Publication Date
- 2024-11-26
AI Technical Summary
Current CVE vulnerability analysis techniques cannot inherit previous analysis conclusions, resulting in low analysis efficiency, easy omissions, and high manpower consumption.
By acquiring historical CVE vulnerability analysis records and organizing them into a table with a preset format, a Python script is used to compare them with the latest vulnerability scan report to automatically discover new vulnerabilities and generate analysis records.
It improves the efficiency of CVE vulnerability analysis, reduces repetitive workload, quickly discovers new CVE vulnerabilities in product components, and provides automated analysis capabilities.
Smart Images

Figure CN119026132A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of vulnerability report analysis, and in particular to a CVE vulnerability report analysis method, system, terminal and computer-readable storage medium. Background Art
[0002] CVE (Common Vulnerabilities and Exposures) is a cybersecurity technical term used to describe and identify known vulnerabilities and security risks in the field of information security. CVE is a public list or database that provides standardized names for various publicly known information security vulnerabilities and risks. Each CVE identifier is unique and named in a certain format. These identifiers allow security experts and researchers to maintain consistency when discussing, analyzing or fixing specific vulnerabilities.
[0003] In the existing technology, many third-party components are needed in the process of product function development. There are many types of components and new CVE vulnerabilities are constantly exposed. In order to ensure that the product uses safe third-party open source components, a binary scanning tool is used to perform a security scan on the product firmware package. The scan report will display the components in the product and the CVE vulnerabilities in the components.
[0004] However, the number of CVE vulnerabilities scanned each time is relatively large, and manual confirmation is very difficult. It takes a lot of manpower to analyze the report, and it is also easy to miss new components in the firmware and CVE vulnerabilities during the analysis process, and it is impossible to inherit previous analysis conclusions.
[0005] Therefore, the prior art still needs to be improved and developed. Summary of the invention
[0006] The main purpose of the present invention is to provide an analysis method, system, terminal and computer-readable storage medium for CVE vulnerability reports, aiming to solve the problem that the analysis of CVE vulnerabilities in the prior art cannot inherit previous analysis conclusions, resulting in omissions and low analysis efficiency when analyzing CVE vulnerabilities.
[0007] To achieve the above object, the present invention provides a method for analyzing CVE vulnerability reports, the method comprising the following steps:
[0008] Acquire a CVE vulnerability history analysis record, organize the CVE vulnerability history analysis record into a table in a preset format, obtain a target CVE vulnerability history analysis record, and store the target CVE vulnerability history analysis record in a first path;
[0009] Obtain a CVE vulnerability scanning file to be analyzed, perform vulnerability scanning on the CVE vulnerability scanning file to obtain a vulnerability report file, and store the vulnerability report file in a second path;
[0010] Use a python script to obtain the target CVE vulnerability history analysis record stored in the first path and the vulnerability report file in the second path, and use the python script to compare the target CVE vulnerability history analysis record and the vulnerability report file to obtain a comparison result;
[0011] If the comparison results are the same, it means that no new vulnerabilities are found in this round of testing, and the CVE vulnerability historical analysis record is retained. If the comparison results are different, new vulnerabilities are found according to the comparison results, and an analysis record of this round of CVE vulnerability scanning files is generated.
[0012] Optionally, in the analysis method of the CVE vulnerability report, the CVE vulnerability history analysis record is an analysis record of a previous round of CVE vulnerability scanning files, and the analysis record includes components of the product and the vulnerability status of the components.
[0013] Optionally, the method for analyzing the CVE vulnerability report, wherein the step of arranging the CVE vulnerability history analysis record into a table in a preset format to obtain a target CVE vulnerability history analysis record, specifically includes:
[0014] Check whether the CVE vulnerability history analysis record has any missing parts. If there are missing parts, fill in the missing parts of the CVE vulnerability history analysis record to obtain a filled record, and organize the filled record into an Excel table;
[0015] The format of the Excel spreadsheet is adjusted to the format of a CVE vulnerability scanning file to obtain a target CVE vulnerability historical analysis record.
[0016] Optionally, the method for analyzing a CVE vulnerability report, wherein the step of obtaining a CVE vulnerability scanning file to be analyzed further includes:
[0017] Get the pre-downloaded Python script and load it onto the openlab platform.
[0018] Optionally, the CVE vulnerability report analysis method, wherein the CVE vulnerability scanning file is subjected to vulnerability scanning to obtain a vulnerability report file, and the vulnerability report file is stored in a second path, specifically comprises:
[0019] Obtain a firmware package in the CVE vulnerability scanning file, and obtain an open source software component according to the firmware package;
[0020] Use a vulnerability scanning tool to perform vulnerability scanning on the open source software components to obtain vulnerability scanning results;
[0021] The vulnerability scanning result is converted into an Excel table through the openlab platform to obtain the vulnerability report file.
[0022] Optionally, the CVE vulnerability report analysis method, wherein the use of the Python script to compare the target CVE vulnerability history analysis record with the vulnerability report file to obtain a comparison result, specifically includes:
[0023] Open the target CVE vulnerability history analysis record and the vulnerability report file through the python script;
[0024] Compare the target CVE vulnerability history analysis record and the vulnerability report file in sequence according to the table order of the Excel table to obtain the comparison status of each component;
[0025] Combine the comparison of each component to obtain the comparison result.
[0026] Optionally, the method for analyzing the CVE vulnerability report, wherein the step of obtaining the comparison result further includes:
[0027] The CVE vulnerability history analysis record for the next round of testing is determined based on the comparison results.
[0028] In addition, to achieve the above-mentioned purpose, the present invention further provides a CVE vulnerability report analysis system, wherein the CVE vulnerability report analysis system comprises:
[0029] A first security performance enhancement module is used to obtain a soft bus to be enhanced and an anti-intrusion system, and add the anti-intrusion system to the soft bus to be enhanced to obtain the anti-intrusion soft bus;
[0030] The second security performance enhancement module is used to perform vulnerability scanning, access control, communication encryption, regular monitoring and security audit on the anti-intrusion soft bus to obtain a soft bus with enhanced security performance.
[0031] In addition, to achieve the above-mentioned purpose, the present invention also provides a terminal, wherein the terminal includes: a memory, a processor, and an analysis program for CVE vulnerability reports stored in the memory and executable on the processor, and when the analysis program for CVE vulnerability reports is executed by the processor, the steps of the analysis method for CVE vulnerability reports as described above are implemented.
[0032] In addition, to achieve the above-mentioned purpose, the present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores an analysis program for CVE vulnerability reports, and when the analysis program for CVE vulnerability reports is executed by a processor, the steps of the analysis method for CVE vulnerability reports as described above are implemented.
[0033] In the present invention, a CVE vulnerability history analysis record is obtained, and the CVE vulnerability history analysis record is organized into a table of a preset format to obtain a target CVE vulnerability history analysis record; a CVE vulnerability scanning file to be analyzed is obtained, and a vulnerability scanning is performed on the CVE vulnerability scanning file to obtain a vulnerability report file; a python script is used to obtain the target CVE vulnerability history analysis record and the vulnerability report file, and a python script is used to compare the target CVE vulnerability history analysis record and the vulnerability report file to obtain a comparison result; if the comparison results are the same, it means that no new vulnerabilities are found in this round of testing, and the CVE vulnerability history analysis record is retained; if the comparison results are different, new vulnerabilities are found according to the comparison results, and an analysis record of this round of CVE vulnerability scanning files is generated. The workload of repeated analysis is reduced, and new CVE vulnerabilities in components in the product can be quickly discovered. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] Figure 1 It is a flow chart of a preferred embodiment of the method for analyzing CVE vulnerability reports of the present invention;
[0035] Figure 2 It is a schematic diagram of the principle of a preferred embodiment of the CVE vulnerability report analysis system of the present invention;
[0036] Figure 3 Schematic diagram of the operating environment of a preferred embodiment of the terminal of the present invention. DETAILED DESCRIPTION
[0037] The present application provides a method for analyzing CVE vulnerability reports and related equipment. To make the purpose, technical solution and effect of the present application clearer and more specific, the present application is further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0038] It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those generally understood by those skilled in the art to which this application belongs. It should also be understood that terms such as those defined in general dictionaries should be understood to have meanings consistent with those in the context of the prior art, and will not be interpreted with idealized or overly formal meanings unless specifically defined as here.
[0039] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present invention, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or suggesting their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.
[0040] The analysis method of CVE vulnerability report described in the preferred embodiment of the present invention is as follows: Figure 1 As shown, the analysis method of the CVE vulnerability report includes the following steps:
[0041] Step S10: Acquire CVE vulnerability history analysis records, organize the CVE vulnerability history analysis records into a table in a preset format, obtain target CVE vulnerability history analysis records, and store the target CVE vulnerability history analysis records in a first path.
[0042] Specifically, the CVE vulnerability history analysis record is an analysis record of a previous round of CVE vulnerability scanning files, and the analysis record includes components of a product and vulnerability conditions of the components.
[0043] It is understandable that after each test is completed, the security tester needs to first organize the CVE vulnerability historical analysis records. The CVE vulnerability historical analysis records are based on the problems and non-problems of each previous analysis of the product. As a reference for the next analysis record, for problems that have been confirmed, subsequent analysis will no longer waste energy on comparing the problems that have been analyzed, which can improve analysis efficiency.
[0044] Furthermore, the CVE vulnerability history analysis record is organized into a table in a preset format to obtain a target CVE vulnerability history analysis record, specifically including:
[0045] Check whether the CVE vulnerability history analysis record has any missing parts. If there are missing parts, fill in the missing parts of the CVE vulnerability history analysis record to obtain a filled record, and organize the filled record into an Excel table;
[0046] The format of the Excel spreadsheet is adjusted to the format of a CVE vulnerability scanning file to obtain a target CVE vulnerability historical analysis record.
[0047] In this embodiment, after obtaining the CVE vulnerability history analysis record, first check whether the CVE vulnerability history analysis record is complete and whether there is any missing situation. If there is no missing situation, directly organize the CVE vulnerability history analysis record into an Excel table. If there is a missing situation, fill the missing in the CVE vulnerability history analysis record to obtain a filled record, and then organize the filled record into an Excel table.
[0048] Furthermore, the format of the Excel table is adjusted to the format of a CVE vulnerability scanning file to obtain a target CVE vulnerability history analysis record. In the present invention, the CVE vulnerability history analysis record is organized into an Excel table and the format of the Excel table is adjusted to the format of a CVE vulnerability scanning file. The purpose is to keep the CVE vulnerability history analysis record consistent with the current CVE vulnerability scanning file format, which is convenient for subsequent comparison and reference without the need for redundant format processing, thereby improving the efficiency of the analysis.
[0049] Furthermore, the target CVE vulnerability history analysis record is stored in a first path; the first path is a pre-specified path, and the target CVE vulnerability history analysis record is stored in the specified path. The subsequent python script will directly obtain the file under the path through the code, which can speed up the comparison.
[0050] Step S20: obtain a CVE vulnerability scanning file to be analyzed, perform a vulnerability scan on the CVE vulnerability scanning file, obtain a vulnerability report file, and store the vulnerability report file in a second path.
[0051] It is understandable that obtaining the CVE vulnerability scanning file to be analyzed also includes: obtaining the pre-downloaded python script and loading the pre-downloaded python script onto the openlab platform. The python script is used to compare the historical analysis records with the latest report, and to show how many new CVE vulnerabilities have been added compared to the historical analysis records, so that the analysis of the new CVE vulnerabilities can be focused; the openlab platform is used to convert the scanning results into an excel table.
[0052] Specifically, first obtain the uploaded CVE vulnerability scanning file to be analyzed from the user end, scan the CVE vulnerability scanning file to be analyzed, obtain the firmware package in the CVE vulnerability scanning file, and obtain the open source software component based on the firmware package; then use a vulnerability scanning tool (such as OpenVAS, Nessus, and AWVS, etc.) to perform a vulnerability scan on the open source software component to obtain the vulnerability scanning result, and then convert the vulnerability scanning result into an excel table through the openlab platform to obtain the vulnerability report file.
[0053] OpenVAS: A powerful open source vulnerability scanning tool, developed based on the Nessus framework, provides a rich vulnerability library and scanning plug-ins, suitable for quickly discovering various vulnerabilities and risks in the network environment. Nessus: Developed by TenableNetwork Security, it supports automatic scanning of the network environment, discovers various security vulnerabilities and risks, and provides detailed reports and analysis results. AWVS (Acunetix Web Vulnerability Scanner): Specially used for vulnerability scanning of Web applications, automatically scans Web applications and discovers possible vulnerabilities, such as SQL injection, cross-site scripting, etc.
[0054] Furthermore, the vulnerability report file is stored in a second path; the second path is a pre-specified path, and the vulnerability report file is stored in the specified path. The subsequent python script will directly obtain the file under the path through the code, which can speed up the comparison.
[0055] Step S30: Use a python script to obtain the target CVE vulnerability history analysis record stored in the first path and the vulnerability report file in the second path, and use the python script to compare the target CVE vulnerability history analysis record and the vulnerability report file to obtain a comparison result.
[0056] Specifically, a python script is used to automatically obtain the target CVE vulnerability history analysis record and the vulnerability report file stored in the first path and the second path. The code in the python script will automatically obtain the file content in a given path. This path is set in the code. When the python script needs to be used to compare the target CVE vulnerability history analysis record and the vulnerability report file, the python script will first call this code to obtain the target CVE vulnerability history analysis record and the vulnerability report file stored in the first path and the second path.
[0057] The python script compares the historical analysis records with the latest report, and shows how many new CVE vulnerabilities have been added compared to the historical analysis records, so that you can focus on analyzing the new CVE vulnerabilities.
[0058] Further, the use of the python script to compare the target CVE vulnerability history analysis record with the vulnerability report file to obtain a comparison result specifically includes:
[0059] The target CVE vulnerability history analysis record and the vulnerability report file are opened by the python script; the target CVE vulnerability history analysis record and the vulnerability report file are compared in sequence according to the table order of the excel table to obtain the comparison situation of each component; and the comparison result is obtained by combining the comparison situation of each component.
[0060] In this embodiment, the target CVE vulnerability history analysis record and the vulnerability report file are both in the form of Excel tables, and the format of the tables is also the same. Therefore, after opening the target CVE vulnerability history analysis record and the vulnerability report file, the python script will compare them in sequence according to the table order of the Excel table. Each column in the table represents a component. By comparing them in sequence, the comparison status of each component can be obtained, and then the comparison status of each component is summarized to obtain the total comparison result.
[0061] Step S40: If the comparison results are the same, it means that no new vulnerability is found in this round of testing, and the CVE vulnerability history analysis record is retained. If the comparison results are different, new vulnerabilities are found according to the comparison results, and an analysis record of this round of CVE vulnerability scanning files is generated.
[0062] Specifically, if the comparison results are the same, it means that no new vulnerabilities are found in this round of testing, and the test is ended, indicating that no new problems are found in this round of testing; if the comparison results are different, it means that the python script has found a new CVE vulnerability. At this time, it is necessary to find the new vulnerability according to the comparison result, that is, find the difference from the target CVE vulnerability history analysis record in the vulnerability report file, which is the newly appeared vulnerability. At the same time, the analysis record of this round of CVE vulnerability scanning files is generated according to the target CVE vulnerability history analysis record and the newly appeared vulnerability, and the analysis record of the current round of CVE vulnerability scanning files is used as the data for the next CVE scanning report analysis; that is, after obtaining the comparison result, this embodiment will also determine the CVE vulnerability history analysis record for the next round of testing according to the comparison result.
[0063] It can be seen that the analysis method of CVE vulnerability report disclosed in the present invention effectively solves the problems that CVE vulnerabilities are prone to omissions, cannot inherit previous analysis conclusions, have a large number of CVE vulnerabilities, are prone to errors, have low efficiency, and repeat work. It can quickly discover new CVE vulnerabilities in components in products, provide automated analysis capabilities, improve testing efficiency, and reduce manpower investment. Previously recorded CVE analysis conclusions can be recorded through configuration files and Excel. A new analysis can process CVE vulnerabilities based on previous analysis conclusions, thereby reducing the workload of repeated analysis.
[0064] Furthermore, if Figure 2As shown, based on the above-mentioned CVE vulnerability report analysis method, the present invention also provides a CVE vulnerability report analysis system accordingly, wherein the CVE vulnerability report analysis system includes:
[0065] A historical data processing module 41 is used to obtain CVE vulnerability historical analysis records, organize the CVE vulnerability historical analysis records into a table in a preset format, obtain target CVE vulnerability historical analysis records, and store the target CVE vulnerability historical analysis records in a first path;
[0066] A vulnerability scanning module 42 is used to obtain a CVE vulnerability scanning file to be analyzed, perform a vulnerability scan on the CVE vulnerability scanning file, obtain a vulnerability report file, and store the vulnerability report file in a second path;
[0067] A report file comparison module 43 is used to use a python script to obtain the target CVE vulnerability history analysis record stored in the first path and the vulnerability report file in the second path, and use the python script to compare the target CVE vulnerability history analysis record and the vulnerability report file to obtain a comparison result;
[0068] The analysis record generation module 44 is used to, if the comparison results are the same, indicate that no new vulnerabilities are found in this round of testing, and retain the CVE vulnerability history analysis record; if the comparison results are different, find new vulnerabilities based on the comparison results and generate analysis records for this round of CVE vulnerability scanning files.
[0069] Furthermore, if Figure 3 As shown, based on the above-mentioned CVE vulnerability report analysis method and system, the present invention also provides a terminal accordingly, and the terminal includes a processor 10, a memory 20 and a display 30. Figure 3 Only some components of the terminal are shown, but it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead.
[0070] In some embodiments, the memory 20 may be an internal storage unit of the terminal, such as a hard disk or memory of the terminal. In other embodiments, the memory 20 may also be an external storage device of the terminal, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (SecureDigital, SD) card, a flash card (Flash Card), etc. equipped on the terminal. Further, the memory 20 may also include both an internal storage unit of the terminal and an external storage device. The memory 20 is used to store application software and various types of data installed on the terminal, such as the program code of the installation terminal, etc. The memory 20 may also be used to temporarily store data that has been output or is to be output. In one embodiment, the memory 20 stores a CVE vulnerability report analysis program 40, which can be executed by the processor 10, thereby realizing the CVE vulnerability report analysis method in the present application.
[0071] In some embodiments, the processor 10 may be a central processing unit (CPU), a microprocessor or other data processing chip, used to run the program code or process data stored in the memory 20, such as executing the analysis method of the CVE vulnerability report.
[0072] In some embodiments, the display 30 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, etc. The display 30 is used to display information on the terminal and to display a visual user interface. The components 10-30 of the terminal communicate with each other via a system bus.
[0073] In one embodiment, when the processor 10 executes the CVE vulnerability report analysis program 40 in the memory 20, the following steps are implemented:
[0074] Acquire a CVE vulnerability history analysis record, organize the CVE vulnerability history analysis record into a table in a preset format, obtain a target CVE vulnerability history analysis record, and store the target CVE vulnerability history analysis record in a first path;
[0075] Obtain a CVE vulnerability scanning file to be analyzed, perform vulnerability scanning on the CVE vulnerability scanning file to obtain a vulnerability report file, and store the vulnerability report file in a second path;
[0076] Use a python script to obtain the target CVE vulnerability history analysis record stored in the first path and the vulnerability report file in the second path, and use the python script to compare the target CVE vulnerability history analysis record and the vulnerability report file to obtain a comparison result;
[0077] If the comparison results are the same, it means that no new vulnerabilities are found in this round of testing, and the CVE vulnerability historical analysis record is retained. If the comparison results are different, new vulnerabilities are found according to the comparison results, and an analysis record of this round of CVE vulnerability scanning files is generated.
[0078] The CVE vulnerability history analysis record is an analysis record of a previous round of CVE vulnerability scanning files, and the analysis record includes components of a product and vulnerability conditions of the components.
[0079] The step of arranging the CVE vulnerability history analysis records into a table in a preset format to obtain a target CVE vulnerability history analysis record specifically includes:
[0080] Check whether the CVE vulnerability history analysis record has any missing parts. If there are missing parts, fill in the missing parts of the CVE vulnerability history analysis record to obtain a filled record, and organize the filled record into an Excel table;
[0081] The format of the Excel spreadsheet is adjusted to the format of a CVE vulnerability scanning file to obtain a target CVE vulnerability historical analysis record.
[0082] The step of obtaining the CVE vulnerability scanning file to be analyzed further includes:
[0083] Get the pre-downloaded Python script and load it onto the openlab platform.
[0084] The step of performing vulnerability scanning on the CVE vulnerability scanning file to obtain a vulnerability report file and storing the vulnerability report file in the second path specifically includes:
[0085] Obtain a firmware package in the CVE vulnerability scanning file, and obtain an open source software component according to the firmware package;
[0086] Use a vulnerability scanning tool to perform vulnerability scanning on the open source software components to obtain vulnerability scanning results;
[0087] The vulnerability scanning result is converted into an Excel table through the openlab platform to obtain the vulnerability report file.
[0088] The use of the python script to compare the target CVE vulnerability history analysis record with the vulnerability report file to obtain a comparison result specifically includes:
[0089] Open the target CVE vulnerability history analysis record and the vulnerability report file through the python script;
[0090] Compare the target CVE vulnerability history analysis record and the vulnerability report file in sequence according to the table order of the Excel table to obtain the comparison status of each component;
[0091] Combine the comparison of each component to obtain the comparison result.
[0092] Wherein, the step of obtaining the comparison result further includes:
[0093] The CVE vulnerability history analysis record for the next round of testing is determined based on the comparison results.
[0094] In summary, the present invention provides a method and system for analyzing CVE vulnerability reports, the method comprising: obtaining CVE vulnerability history analysis records, arranging the CVE vulnerability history analysis records into a table of a preset format, and obtaining a target CVE vulnerability history analysis record; obtaining a CVE vulnerability scanning file to be analyzed, performing vulnerability scanning on the CVE vulnerability scanning file, and obtaining a vulnerability report file; using a python script to obtain a target CVE vulnerability history analysis record and a vulnerability report file, and using a python script to compare the target CVE vulnerability history analysis record and the vulnerability report file to obtain a comparison result; if the comparison results are the same, it means that no new vulnerabilities are found in this round of testing, and the CVE vulnerability history analysis records are retained. If the comparison results are different, new vulnerabilities are found according to the comparison results, and analysis records of this round of CVE vulnerability scanning files are generated. The present invention can quickly discover new CVE vulnerabilities in components in a product, provide automated analysis capabilities, improve test efficiency, reduce manpower investment, and can record previously recorded CVE analysis conclusions through configuration files and excel. A new analysis can process CVE vulnerabilities based on previous analysis conclusions, reduce the workload of repeated analysis, and quickly discover new CVE vulnerabilities in components in a product.
[0095] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or terminal including the element.
[0096] Of course, those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided by the present invention can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
[0097] It should be understood that the application of the present invention is not limited to the above examples. For ordinary technicians in this field, improvements or changes can be made based on the above description. All these improvements and changes should fall within the scope of protection of the claims attached to the present invention.
Claims
1. A method for analyzing CVE vulnerability reports, characterized in that: The analysis method of the CVE vulnerability report includes: Acquire a CVE vulnerability history analysis record, organize the CVE vulnerability history analysis record into a table in a preset format, obtain a target CVE vulnerability history analysis record, and store the target CVE vulnerability history analysis record in a first path; Obtain a CVE vulnerability scanning file to be analyzed, perform vulnerability scanning on the CVE vulnerability scanning file to obtain a vulnerability report file, and store the vulnerability report file in a second path; Use a python script to obtain the target CVE vulnerability history analysis record stored in the first path and the vulnerability report file in the second path, and use the python script to compare the target CVE vulnerability history analysis record and the vulnerability report file to obtain a comparison result; If the comparison results are the same, it means that no new vulnerabilities are found in this round of testing, and the CVE vulnerability history analysis record is retained. If the comparison results are different, new vulnerabilities are found according to the comparison results, and an analysis record of this round of CVE vulnerability scanning files is generated.
2. The method for analyzing CVE vulnerability reports according to claim 1, characterized in that: The CVE vulnerability history analysis record is an analysis record of the last round of CVE vulnerability scanning files, and the analysis record includes components of the product and the vulnerability status of the components.
3. The method for analyzing CVE vulnerability reports according to claim 2, characterized in that: The step of arranging the CVE vulnerability history analysis records into a table in a preset format to obtain a target CVE vulnerability history analysis record specifically includes: Check whether the CVE vulnerability history analysis record has any missing parts. If there are missing parts, fill in the missing parts of the CVE vulnerability history analysis record to obtain a filled record, and organize the filled record into an Excel table; The format of the Excel spreadsheet is adjusted to the format of a CVE vulnerability scanning file to obtain a target CVE vulnerability historical analysis record.
4. The method for analyzing CVE vulnerability reports according to claim 3, characterized in that: The obtaining of the CVE vulnerability scanning file to be analyzed also includes: Get the pre-downloaded Python script and load it onto the openlab platform.
5. The method for analyzing CVE vulnerability reports according to claim 4, characterized in that: The performing vulnerability scanning on the CVE vulnerability scanning file to obtain a vulnerability report file, and storing the vulnerability report file in the second path specifically includes: Obtain a firmware package in the CVE vulnerability scanning file, and obtain an open source software component according to the firmware package; Use a vulnerability scanning tool to perform vulnerability scanning on the open source software components to obtain vulnerability scanning results; The vulnerability scanning result is converted into an Excel table through the openlab platform to obtain the vulnerability report file.
6. The method for analyzing CVE vulnerability reports according to claim 5, characterized in that: The use of the python script to compare the target CVE vulnerability history analysis record with the vulnerability report file to obtain a comparison result specifically includes: Open the target CVE vulnerability history analysis record and the vulnerability report file through the python script; Compare the target CVE vulnerability history analysis record and the vulnerability report file in sequence according to the table order of the Excel table to obtain the comparison status of each component; Combine the comparison of each component to obtain the comparison result.
7. The method for analyzing CVE vulnerability reports according to claim 1, characterized in that: The comparison result is obtained, and then further includes: The CVE vulnerability history analysis record for the next round of testing is determined based on the comparison results.
8. A CVE vulnerability report analysis system, characterized in that: The analysis system of the CVE vulnerability report includes: A historical data processing module, used to obtain CVE vulnerability historical analysis records, organize the CVE vulnerability historical analysis records into a table in a preset format, obtain target CVE vulnerability historical analysis records, and store the target CVE vulnerability historical analysis records in a first path; A vulnerability scanning module is used to obtain a CVE vulnerability scanning file to be analyzed, perform a vulnerability scan on the CVE vulnerability scanning file, obtain a vulnerability report file, and store the vulnerability report file in a second path; A report file comparison module, used to use a python script to obtain the target CVE vulnerability history analysis record stored in the first path and the vulnerability report file in the second path, and use the python script to compare the target CVE vulnerability history analysis record and the vulnerability report file to obtain a comparison result; The analysis record generation module is used to, if the comparison results are the same, indicate that no new vulnerabilities are found in this round of testing, and retain the CVE vulnerability history analysis record; if the comparison results are different, find new vulnerabilities based on the comparison results and generate analysis records for this round of CVE vulnerability scanning files.
9. A terminal, characterized in that: The terminal includes: a memory, a processor, and a CVE vulnerability report analysis program stored in the memory and executable on the processor. When the CVE vulnerability report analysis program is executed by the processor, the steps of the CVE vulnerability report analysis method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a CVE vulnerability report analysis program, and when the CVE vulnerability report analysis program is executed by a processor, the steps of the CVE vulnerability report analysis method according to any one of claims 1 to 7 are implemented.
