Software vulnerability detection method, device, computer equipment and storage medium
By matching the vulnerable software version library, identifying the software with vulnerability in the terminal device, solving the problem of lack of real-time software vulnerability detection capabilities in the existing technology and improving network security.
Patent Information
- Application Number
- CN202111316010.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-11-08
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2041-11-08
AI Technical Summary
The lack of effective software vulnerability detection platforms in the prior art, especially the lack of real-time software vulnerability detection capabilities, which makes it difficult to ensure network security.
通过获取终端设备中安装的软件信息,并将其与漏洞软件版本库中的软件名称和版本进行匹配,确定存在漏洞的目标软件,从而实现漏洞检测。
Real-time vulnerability detection of software in terminal devices is realized, network security is improved, and potential threat identification and protection capabilities are enhanced.
Smart Images

Figure CN114021144B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network security technology, and in particular to a software vulnerability detection method, device, computer equipment and storage medium. Background Art
[0002] Software vulnerabilities are one of the main sources of information security risks and an important target in network attack and defense. Whether from the perspective of national cybersecurity strategy or social information security protection, security vulnerabilities have become one of the core issues in the game between the two sides of information confrontation.
[0003] At present, there are a variety of software on the market, resulting in an increasing number of exploitable software vulnerabilities. However, there are relatively few platforms that can detect software vulnerabilities, and even fewer platforms that can perform real-time vulnerability detection on software. Summary of the invention
[0004] Embodiments of the present application provide a software vulnerability detection method, apparatus, computer equipment, and storage medium for performing vulnerability detection on software installed in a terminal device.
[0005] An embodiment of the present invention provides a software vulnerability detection method, the method comprising:
[0006] Obtaining software information corresponding to each software installed in the terminal device, wherein the software information includes the software name and the corresponding software version;
[0007] Matching the software information with the software names and software versions in a vulnerability software version library, wherein the vulnerability software version library stores the names of the vulnerable software and the corresponding software versions;
[0008] Determine the software in the terminal device corresponding to the software information that successfully matches the software name and software version in the vulnerable software version library as the target software;
[0009] The target software is determined to be software with vulnerabilities.
[0010] An embodiment of the present invention provides a software vulnerability detection device, the device comprising:
[0011] An acquisition module, used to acquire software information corresponding to each software installed in the terminal device, wherein the software information includes a software name and a corresponding software version;
[0012] A matching module, used to match the software information with the software name and software version in a vulnerability software version library, wherein the vulnerability software version library stores the names of the software with vulnerabilities and the corresponding software versions;
[0013] A determination module, used to determine the software in the terminal device corresponding to the software information that successfully matches the software name and software version in the vulnerable software version library as the target software;
[0014] The determination module is further used to determine that the target software is software with vulnerabilities.
[0015] A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the software vulnerability detection method when executing the computer program.
[0016] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the software vulnerability detection method is implemented.
[0017] The present invention provides a software vulnerability detection method, device, computer equipment and storage medium. After acquiring the software information corresponding to each software installed in the terminal device, the present invention matches the software information with the software name and software version in the vulnerability software version library, and then determines the software corresponding to the software information in the terminal device that successfully matches the software name and software version in the vulnerability software version library as the target software, that is, determines the target software as the software with vulnerabilities. Thus, the vulnerability detection of the software installed in the terminal device is realized through the present invention, thereby improving network security. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] Figure 1 A flow chart of a software vulnerability detection method provided by this application;
[0019] Figure 2 A flowchart for obtaining the software version corresponding to the software name provided by this application;
[0020] Figure 3 A schematic diagram of the structure of the software vulnerability detection device provided by this application;
[0021] Figure 4 A schematic diagram of a computer device provided for this application. DETAILED DESCRIPTION
[0022] In order to better understand the above-mentioned technical scheme, the technical scheme of the embodiments of the present application is described in detail below through the accompanying drawings and specific embodiments. It should be understood that the embodiments of the present application and the specific features in the embodiments are detailed descriptions of the technical scheme of the embodiments of the present application, rather than limitations on the technical scheme of the present application. In the absence of conflict, the embodiments of the present application and the technical features in the embodiments may be combined with each other.
[0023] See also Figure 1, is a software vulnerability detection method provided by an embodiment of the present invention, the method specifically comprises steps S101 to S104:
[0024] Step S101, obtaining software information corresponding to each software installed in the terminal device.
[0025] The software information includes the software name and the corresponding software version, and the software version may be the software version number, such as 1.0, 2.0, 3.0, etc. In this embodiment, the software information of all software installed in the terminal device or the software information of specific software in the terminal device may be obtained, so as to determine the vulnerable software in the terminal device according to the software information in subsequent steps.
[0026] It should be noted that if it is necessary to determine whether there is a vulnerability in a specific software in a terminal device, the software that needs to be detected for vulnerabilities in the terminal device can be marked, so that the terminal device obtains the specific software that needs to be detected for vulnerabilities based on the mark, and then obtains the software information of the specific software.
[0027] The present invention provides an optional embodiment, wherein the obtaining of software information corresponding to each software installed in the terminal device includes: obtaining the software name of the software installed in the terminal device at a preset time interval, or obtaining the software name of the startup software when the software in the terminal device is started; and obtaining the software version corresponding to the software name according to the software name. Furthermore, after obtaining the software name of each software in the terminal device, it is necessary to determine whether the obtained software name corresponds to the real software name of the software.
[0028] For example, when a new software process is started, the path of the process file is obtained, and the name of the process file is determined through the PDB information of the process. For example, powershell.exe is artificially renamed to power.exe, but its PDB information is powershell.pdb, so it can be determined that the software name of this program is powershell.exe.
[0029] Specifically, the software name of the software installed in the terminal device is obtained according to the preset time interval, including: obtaining the path of the process file of the software according to the preset time interval, obtaining the debugging file through the path of the process file, and determining the software name of the corresponding software according to the process name in the debugging file.
[0030] Among them, the preset time interval can be set according to actual needs, such as the preset time interval can be 10 hours, 24 hours, 48 hours, etc., which is not specifically limited in this embodiment.
[0031] Furthermore, this embodiment can set time intervals corresponding to different software according to the usage frequency of each software in the terminal device, and then obtain software information of the corresponding software according to different time intervals. Specifically, in this embodiment, the higher the usage frequency of the software, the shorter the corresponding time interval is set; the lower the usage frequency of the software, the longer the corresponding time interval is set. That is, this embodiment obtains software information of different software at different time intervals, so that the obtained software information is targeted, thereby improving the efficiency of software vulnerability detection.
[0032] Specifically, when software in a terminal device is started, the software name of the startup software is obtained, including: when software in the terminal device is started, the path of the process file of the software is obtained, the debugging file is obtained through the path of the process file, and the software name of the startup software is determined according to the process name in the debugging file.
[0033] For example, when a new process is started in the terminal device, the path of the process file corresponding to the newly started process is obtained, and the name of this process file is obtained through the debugging file (program database file) of the process, that is, the process name in the debugging file is obtained, and then the process name is determined as the software name of the startup software.
[0034] Step S102, matching the software information with the software name and software version in the vulnerable software version library.
[0035] The vulnerability software version library stores the names of the software with vulnerabilities and the corresponding software versions. It should be noted that in this embodiment, the versions of the commonly used software or the software to be detected with vulnerabilities can be obtained from the entire network, such as the official website of the software publisher, the official website of Microsoft, the national information security vulnerability library CNNVD, the official website of CVE, etc. to obtain the software versions with vulnerabilities, and then the obtained software names and software versions with vulnerabilities are stored in the vulnerability software version library accordingly.
[0036] It should be noted that the present embodiment can update the vulnerable software version library in real time, that is, after discovering new vulnerable software, the software name and software version of the vulnerable software are updated to the vulnerable software version library; the vulnerable software version library can also be updated at regular intervals, and the update time can be 5 days, 10 days, 15 days, etc., and the present embodiment does not make specific limitations on this.
[0037] Furthermore, if the vulnerable software has been repaired, the software name and software version of the corresponding vulnerable software in the vulnerable software version library can be deleted. For example, video software A has two software versions, 1.0 and 2.0, and both software versions have vulnerabilities, that is, the vulnerable software version library stores the above two data records, video software A, 1.0, and video software A, 2.0. If the operator of video software A repairs version 1.0 (the repair patch automatically repairs the software), the data record "video software A, 1.0" in the vulnerable software version library can be deleted.
[0038] Step S103: determine the software in the terminal device corresponding to the software information that successfully matches the software name and software version in the vulnerable software version library as the target software.
[0039] For example, a social software A is installed in the terminal device. After the social software A is started, the terminal device can obtain the software information of the social software A (the software name and software version of the social software A). If the software name and software version of the social software A exist in the vulnerable software version library, it means that the social software A is the target software, that is, the social software A is a software with a vulnerability.
[0040] Step S104: determine that the target software is software with vulnerabilities.
[0041] The present invention provides a software vulnerability detection method. After obtaining software information corresponding to each software installed in a terminal device, the present invention matches the software information with the software name and software version in the vulnerability software version library, and then determines the software corresponding to the software information in the terminal device that successfully matches the software name and software version in the vulnerability software version library as the target software, that is, determines the target software as software with vulnerabilities. Thus, the vulnerability detection of the software installed in the terminal device is realized through the present invention, thereby improving network security.
[0042] See also Figure 2 , according to the software name, obtain the software version corresponding to the software name, including:
[0043] Step S201, reading the uninstallation or modification program information in the registry of the terminal device.
[0044] Step S202, querying whether the uninstall or change program information contains a software version corresponding to the software name.
[0045] It should be noted that the uninstall or change program information of the registry usually stores the software version corresponding to the software name, so the software version corresponding to the software name can be obtained through the uninstall or change program information of the registry. However, there are some software that does not need to be installed (software that can be run directly without being installed on the terminal device), such as applets, public accounts, etc., and the software version corresponding to the software name cannot be found in the uninstall or change program information of the registry. Therefore, this embodiment adopts a different processing method for whether the software version corresponding to the software name can be queried in the uninstall or change program information of the registry, that is, if the software version corresponding to the software name exists in the uninstall or change program information, jump to step S203 to continue execution; if the software version corresponding to the software name does not exist in the uninstall or change program information, jump to step S204 to continue execution.
[0046] Step S203: If the software version corresponding to the software name exists in the uninstall or change program information, the software version queried in the uninstall or change program information is determined as the software version corresponding to the software name.
[0047] Step S204: if the software version corresponding to the software name does not exist in the uninstall or change program information, the software version corresponding to the software name is obtained according to the software version obtaining method corresponding to each software name in the preset mapping table.
[0048] The preset mapping table records the acquisition method of the software version of each software. The software version corresponding to the software name can be acquired through the acquisition method of the software version recorded in the preset mapping table.
[0049] Specifically, the method for obtaining the software versions corresponding to the software names in the preset mapping table includes: obtaining the preset position information in the registry corresponding to the software name in the preset mapping table or the file information under the preset directory; obtaining the software version corresponding to the software name through the preset position information in the registry or the file information under the preset directory.
[0050] Among them, the software version corresponding to the software name is recorded under the preset location information in the registry. The preset location information is provided by the software operator or discovered by manual mining; the preset directory is also provided by the software operator. The software version corresponding to the software name can be obtained by reading the file information under the preset directory.
[0051] Furthermore, if the method for obtaining the software version of the software name does not exist in the preset mapping table, the software version corresponding to the software name is obtained through the file attributes corresponding to the software name; or the software version corresponding to the software name is obtained by running a preset command; or the software version corresponding to the software name is obtained by intercepting the software directory corresponding to the software name.
[0052] It should be noted that the software version corresponding to the software name obtained by using file attributes, preset commands or intercepting the software directory can be obtained by any of the above methods, that is, this embodiment does not limit the specific form of obtaining the software version.
[0053] It should be noted that, since the success rate of obtaining the software version corresponding to the software name is in the following order from largest to smallest: through file attributes, preset commands, and interception of software directories, therefore, in this embodiment, if the software version obtaining method of the software name does not exist in the preset mapping table, the software version corresponding to the software name is obtained through the file attributes corresponding to the software name; if the software version corresponding to the software name is not obtained through the file attributes corresponding to the software name, the software version corresponding to the software name is obtained by running a preset command; if the software version corresponding to the software name is not obtained by running a preset command, the software version corresponding to the software name is obtained by intercepting the software directory corresponding to the software name.
[0054] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.
[0055] In one embodiment, a software vulnerability detection device is provided, which corresponds one-to-one to the software vulnerability detection method in the above embodiment. Figure 3 As shown, the functional modules of the software vulnerability detection device are described in detail as follows:
[0056] The acquisition module 31 is used to acquire software information corresponding to each software installed in the terminal device, wherein the software information includes the software name and the corresponding software version;
[0057] A matching module 32, used to match the software information with the software name and software version in a vulnerability software version library, wherein the vulnerability software version library stores the names of the vulnerable software and the corresponding software versions;
[0058] A determination module 33 is used to determine the software in the terminal device corresponding to the software information that successfully matches the software name and software version in the vulnerable software version library as the target software;
[0059] The determination module 33 is further used to determine that the target software is software with vulnerabilities.
[0060] In an optional embodiment, the acquisition module 31 is specifically configured to:
[0061] Obtaining the software name of the software installed in the terminal device at a preset time interval, or obtaining the software name of the startup software when the software in the terminal device is started;
[0062] According to the software name, a software version corresponding to the software name is obtained.
[0063] In an optional embodiment, the acquisition module 31 is further configured to:
[0064] When software is started in the terminal device, the path of the process file of the software is obtained;
[0065] Obtain the debugging file through the path of the process file;
[0066] The software name of the startup software is determined according to the process name in the debugging file.
[0067] In an optional embodiment, the acquisition module 31 is further configured to:
[0068] Reading uninstall or change program information in the registry of the terminal device;
[0069] Querying whether the uninstall or change program information contains a software version corresponding to the software name;
[0070] If the uninstall or change program information contains a software version corresponding to the software name, the software version queried in the uninstall or change program information is determined as the software version corresponding to the software name;
[0071] If the software version corresponding to the software name does not exist in the uninstall or change program information, the software version corresponding to the software name is obtained according to the software version acquisition method corresponding to each software name in the preset mapping table.
[0072] In an optional embodiment, the acquisition module 31 is further configured to:
[0073] Obtaining preset location information in a registry corresponding to the software name in the preset mapping table or file information under a preset directory;
[0074] The software version corresponding to the software name is obtained through the preset position information in the registration table or the file information under the preset directory.
[0075] In an optional embodiment, the acquisition module 31 is further configured to:
[0076] If the software version acquisition method of the software name does not exist in the preset mapping table, acquiring the software version corresponding to the software name through the file attribute corresponding to the software name; or
[0077] Obtain the software version corresponding to the software name by running a preset command; or
[0078] The software version corresponding to the software name is obtained by intercepting the software directory corresponding to the software name.
[0079] In an optional embodiment, the acquisition module 31 is further configured to:
[0080] If the software version acquisition method of the software name does not exist in the preset mapping table, acquiring the software version corresponding to the software name through the file attribute corresponding to the software name;
[0081] If the software version corresponding to the software name is not obtained through the file attribute corresponding to the software name, the software version corresponding to the software name is obtained by running a preset command;
[0082] If the software version corresponding to the software name is not obtained by running the preset command, the software version corresponding to the software name is obtained by intercepting the software directory corresponding to the software name.
[0083] For the specific definition of the software vulnerability detection device, please refer to the definition of the software vulnerability detection method above, which will not be repeated here. Each module in the above-mentioned device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.
[0084] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 4 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a software vulnerability detection method is implemented.
[0085] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:
[0086] Obtaining software information corresponding to each software installed in the terminal device, wherein the software information includes the software name and the corresponding software version;
[0087] Matching the software information with the software names and software versions in a vulnerability software version library, wherein the vulnerability software version library stores the names of the vulnerable software and the corresponding software versions;
[0088] Determine the software in the terminal device corresponding to the software information that successfully matches the software name and software version in the vulnerable software version library as the target software;
[0089] The target software is determined to be software with vulnerabilities.
[0090] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
[0091] Obtaining software information corresponding to each software installed in the terminal device, wherein the software information includes the software name and the corresponding software version;
[0092] Matching the software information with the software names and software versions in a vulnerability software version library, wherein the vulnerability software version library stores the names of the vulnerable software and the corresponding software versions;
[0093] Determine the software in the terminal device corresponding to the software information that successfully matches the software name and software version in the vulnerable software version library as the target software;
[0094] The target software is determined to be software with vulnerabilities.
[0095] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods 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 in this application 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).
[0096] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.
[0097] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in the protection scope of the present invention.
Claims
1. A software vulnerability detection method, characterized in that: The method comprises: Obtaining software information corresponding to each software installed in the terminal device, wherein the software information includes the software name and the corresponding software version; If it is determined whether the specific software in the terminal device has a vulnerability, the specific software in the terminal device is marked so that the terminal device obtains the specific software that needs to be tested for a vulnerability according to the mark and obtains software information of the specific software; Matching the software information with the software names and software versions in a vulnerability software version library, wherein the vulnerability software version library stores the names of the vulnerable software and the corresponding software versions; Determine the software in the terminal device corresponding to the software information that successfully matches the software name and software version in the vulnerable software version library as the target software; Determining that the target software is software with vulnerabilities; The obtaining of software information corresponding to each software installed in the terminal device includes: Obtain the software name of the software installed in the terminal device according to the preset time interval, or obtain the software name of the startup software when the software in the terminal device is started; set the time intervals corresponding to different software according to the usage frequency of each software in the terminal device; the higher the usage frequency of the software, the shorter the corresponding time interval is set; the lower the usage frequency of the software, the longer the corresponding time interval is set; Acquire a software version corresponding to the software name according to the software name; The acquiring the software version corresponding to the software name according to the software name includes: Reading uninstall or change program information in the registry of the terminal device; Querying whether the uninstall or change program information contains a software version corresponding to the software name; If the uninstall or change program information contains a software version corresponding to the software name, the software version queried in the uninstall or change program information is determined as the software version corresponding to the software name; If the software version corresponding to the software name does not exist in the uninstall or change program information, obtaining the software version corresponding to the software name according to the software version obtaining method corresponding to each software name in the preset mapping table; If the software version acquisition method of the software name does not exist in the preset mapping table, acquiring the software version corresponding to the software name through the file attribute corresponding to the software name; If the software version corresponding to the software name is not obtained through the file attribute corresponding to the software name, the software version corresponding to the software name is obtained by running a preset command; If the software version corresponding to the software name is not obtained by running the preset command, the software version corresponding to the software name is obtained by intercepting the software directory corresponding to the software name.
2. The method according to claim 1, characterized in that The step of obtaining the software name of the startup software when the software in the terminal device is started includes: When software is started in the terminal device, the path of the process file of the software is obtained; Obtain the debugging file through the path of the process file; The software name of the startup software is determined according to the process name in the debugging file.
3. The method according to claim 1, characterized in that The method of obtaining the software version corresponding to each software name in the preset mapping table according to the software version obtaining method respectively corresponding to each software name includes: Obtaining preset location information in a registry corresponding to the software name in the preset mapping table or file information under a preset directory; The software version corresponding to the software name is obtained through the preset position information in the registration table or the file information under the preset directory.
4. The method according to claim 1 or 3, characterized in that: The method further comprises: If the software version acquisition method of the software name does not exist in the preset mapping table, acquiring the software version corresponding to the software name through the file attribute corresponding to the software name; or Obtain the software version corresponding to the software name by running a preset command; or The software version corresponding to the software name is obtained by intercepting the software directory corresponding to the software name.
5. A software vulnerability detection device, characterized in that: The device comprises: An acquisition module is used to acquire software information corresponding to each software installed in the terminal device, wherein the software information includes the software name and the corresponding software version; if it is determined that a specific software in the terminal device has a vulnerability, the specific software in the terminal device is marked so that the terminal device acquires the specific software that needs to be detected for a vulnerability according to the mark, and acquires the software information of the specific software; A matching module, used to match the software information with the software name and software version in a vulnerability software version library, wherein the vulnerability software version library stores the names of the software with vulnerabilities and the corresponding software versions; A determination module, used to determine the software in the terminal device corresponding to the software information that successfully matches the software name and software version in the vulnerable software version library as the target software; The determination module is further used to determine that the target software is software with vulnerabilities; The acquisition module is further used to perform the following steps: Obtain the software name of the software installed in the terminal device according to the preset time interval, or obtain the software name of the startup software when the software in the terminal device is started; set the time intervals corresponding to different software according to the usage frequency of each software in the terminal device; the higher the usage frequency of the software, the shorter the corresponding time interval is set; the lower the usage frequency of the software, the longer the corresponding time interval is set; Acquire a software version corresponding to the software name according to the software name; Reading uninstall or change program information in the registry of the terminal device; Querying whether the uninstall or change program information contains a software version corresponding to the software name; If the uninstall or change program information contains a software version corresponding to the software name, the software version queried in the uninstall or change program information is determined as the software version corresponding to the software name; If the software version corresponding to the software name does not exist in the uninstall or change program information, obtaining the software version corresponding to the software name according to the software version obtaining method corresponding to each software name in the preset mapping table; If the software version acquisition method of the software name does not exist in the preset mapping table, acquiring the software version corresponding to the software name through the file attribute corresponding to the software name; If the software version corresponding to the software name is not obtained through the file attribute corresponding to the software name, the software version corresponding to the software name is obtained by running a preset command; If the software version corresponding to the software name is not obtained by running the preset command, the software version corresponding to the software name is obtained by intercepting the software directory corresponding to the software name.
6. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the software vulnerability detection method according to any one of claims 1 to 4 is implemented.
7. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the software vulnerability detection method according to any one of claims 1 to 4 is implemented.
