Automatic vulnerability repairing method, storage medium, equipment and product

Abstract

The invention relates to the technical field of vulnerability repair, and particularly provides an automatic vulnerability repair method, a storage medium, equipment and a product, and the method can comprise the steps: determining a to-be-repaired vulnerability which currently executes a repair operation from at least one vulnerability existing in an application program; searching a target patch file corresponding to the to-be-repaired vulnerability from a patch file library; wherein the patch file library contains patch files corresponding to multiple different types of vulnerabilities; the multiple different types of vulnerabilities and the patch file are stored in the form of a directory; under the condition of confirming that the target patch file passes the verification, comparing the target patch file with a version to which the vulnerability to be repaired belongs, and obtaining a comparison result; and under the condition that the comparison result is inconsistent, repairing the to-be-repaired bug by utilizing the target patch file to obtain a repaired application program. According to the embodiment of the invention, the bug repairing efficiency can be improved.

Description

Technical Field

[0001] This application relates to the technical field of vulnerability repair. Specifically, it relates to a method, storage medium, device, and product for automatic vulnerability repair. Background Art

[0002] A Bug in an application, in the narrow sense, refers to a vulnerability or defect in a software program. In the broad sense, it also includes details that can be improved in the software discovered and proposed by test engineers or users, or function implementations that differ from the requirements document. Since most of the code of an application is manually written and entered by developers, there will inevitably be some vulnerabilities during the writing process. Moreover, no application can be absolutely free of Bugs when it is released. When a Bug is detected in an application, it is usually repaired by patching. Currently, the patch file depends on the version, one version corresponds to one patch file, and it needs to be manually uploaded by technicians; if a technician makes a mistake, there will be a problem of version incompatibility.

[0003] Therefore, how to provide a technical solution for an efficient and accurate method for automatic vulnerability repair has become a technical problem that urgently needs to be solved. Summary of the Invention

[0004] Some embodiments of this application aim to provide a method, storage medium, device, and product for automatic vulnerability repair. Through the technical solutions of the embodiments of this application, automatic vulnerability repair can be achieved, the efficiency and accuracy of vulnerability repair can be improved, and the labor cost can be reduced.

[0005] In a first aspect, some embodiments of this application provide a method for automatic vulnerability repair, including: determining a vulnerability to be repaired for the current repair operation from at least one vulnerability existing in the application; searching for a target patch file corresponding to the vulnerability to be repaired in the patch file library; wherein, the patch file library contains patch files corresponding to various different types of vulnerabilities; the various different types of vulnerabilities and the patch files are stored in the form of a directory; when it is confirmed that the target patch file passes the verification, comparing the target patch file with the version to which the vulnerability to be repaired belongs to obtain a comparison result; when the comparison result is inconsistent, using the target patch file to repair the vulnerability to be repaired to obtain a repaired application.

[0006] In some embodiments of the present application, after selecting the vulnerability to be repaired from the vulnerabilities of the application and then searching for the corresponding target patch file in the patch file library, the target patch file itself and the target patch file and the version are compared and verified, and then the target patch file is used to repair the vulnerability to be repaired, obtaining the repaired application. Some embodiments of the present application can realize the automatic search of the target patch file, realize the automatic repair of vulnerabilities, improve the efficiency and accuracy of vulnerability repair, and reduce the labor and time costs.

[0007] In some embodiments, determining the vulnerability to be repaired for the current repair operation from at least one vulnerability existing in the application includes: obtaining the at least one vulnerability, and performing priority sorting on the at least one vulnerability according to a sorting rule to obtain a vulnerability repair queue; wherein, the sorting rule includes: repair difficulty, repair duration or version importance; determining the vulnerability to be repaired from the vulnerability repair queue.

[0008] Some embodiments of the present application can reasonably plan the repair order of vulnerabilities and improve the repair efficiency by performing priority sorting on the vulnerabilities to determine the vulnerability to be repaired for the current repair operation.

[0009] In some embodiments, before searching for the target patch file corresponding to the vulnerability to be repaired in the patch file library, the method further includes: obtaining various patch files corresponding to various vulnerability types existing in various versions of the application; integrating the various patch files into the patch file library in the form of a directory.

[0010] Some embodiments of the present application can realize the automatic search of the target patch file and save labor and time costs without manual uploading by integrating various patch files into the patch file library.

[0011] In some embodiments, confirming that the target patch file passes the verification includes: calculating the target patch file to obtain a value to be verified; confirming that the value to be verified is consistent with the verification value of the target patch file pre-stored in the patch file library, then the target patch file passes the verification; or, obtaining a patch function corresponding to the vulnerability to be repaired from the target patch file; calculating the patch function to obtain a value to be verified; confirming that the value to be verified is consistent with the function feature value of the patch function pre-stored in the patch file library, then the target patch file passes the verification.

[0012] Some embodiments of the present application ensure that the content in the target patch file is not tampered with and guarantee the effectiveness and security of the repair by verifying the target patch file or the patch function in the target patch file.

[0013] In some embodiments, comparing the target patch file with the version to which the vulnerability to be repaired belongs to obtain a comparison result includes: calculating the content of the target patch file to obtain a first check value; calculating the version to obtain a second check value; if the first check value and the second check value are consistent, the comparison result is consistent; if the first check value and the second check value are inconsistent, the comparison result is inconsistent.

[0014] Some embodiments of the present application compare the target patch file with the version of the vulnerability to be repaired to confirm that the vulnerability to be repaired needs to be repaired, ensuring the accuracy of the repair.

[0015] In some embodiments, the method further includes: after detecting the generation of a new patch file, updating the patch file library with the new patch file.

[0016] Some embodiments of the present application continuously update the patch file library to improve the repair ability of the patch file library.

[0017] In some embodiments, after obtaining the repaired application program, the method further includes: periodically comparing the patch file in the repaired application program with the patch file library, and when the patch file in the repaired application program is inconsistent with the one stored in the patch file library, performing a repair operation on the patch file in the repaired application program.

[0018] Some embodiments of the present application can achieve automatic periodic repair and improve the repair efficiency by automatically detecting the patch files in the repaired application program periodically.

[0019] In a second aspect, some embodiments of the present application provide an apparatus for automatic vulnerability repair, including: a vulnerability determination module for determining a vulnerability to be repaired that is currently undergoing a repair operation from at least one vulnerability existing in an application program; a patch search module for searching for a target patch file corresponding to the vulnerability to be repaired from the patch file library; wherein, the patch file library contains patch files corresponding to various different types of vulnerabilities; the various different types of vulnerabilities and the patch files are stored in the form of a directory; a comparison module for comparing the target patch file with the version to which the vulnerability to be repaired belongs to obtain a comparison result in the case where it is confirmed that the target patch file passes the verification; a repair module for repairing the vulnerability to be repaired with the target patch file to obtain a repaired application program in the case where the comparison result is inconsistent.

[0020] In a third aspect, some embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the method described in any one of the embodiments of the first aspect can be implemented.

[0021] Fourth aspect, some embodiments of the present application provide an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. Wherein, when the processor executes the program, the method described in any embodiment of the first aspect can be implemented.

[0022] Fifth aspect, some embodiments of the present application provide a computer program product, the computer program product includes a computer program, wherein when the computer program is executed by a processor, the method described in any embodiment of the first aspect can be implemented. Description of the Drawings

[0023] In order to more clearly illustrate the technical solutions of some embodiments of the present application, the drawings required for some embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present application, and therefore should not be regarded as limiting the scope. For those of ordinary skill in the art, without creative efforts, other related drawings can also be obtained based on these drawings.

[0024] Figure 1 System diagram of automatic vulnerability repair provided for some embodiments of the present application; Figure 2 One of the method flowcharts of automatic vulnerability repair provided for some embodiments of the present application; Figure 3 Another method flowchart of automatic vulnerability repair provided for some embodiments of the present application; Figure 4 Block diagram of the device composition of automatic vulnerability repair provided for some embodiments of the present application; Figure 5 Schematic diagram of an electronic device provided for some embodiments of the present application. Detailed Embodiments

[0025] Next, the technical solutions in some embodiments of the present application will be described in conjunction with the drawings in some embodiments of the present application.

[0026] It should be noted that: similar reference numerals and letters denote similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. At the same time, in the description of the present application, the terms "first", "second", etc. are only used for distinguishing descriptions, and cannot be understood as indicating or implying relative importance.

[0027] In the related art, when fixing vulnerabilities (or bugs), patch files are version-dependent. One version corresponds to one patch file, and technicians need to manually upload the patch file for bug fixing during the repair. Since the version and the patch file have a strong binding relationship, if the technician uploads the patch file incorrectly due to personal reasons, there will be problems with version compatibility, and the efficiency of bug fixing will be reduced.

[0028] In view of this, some embodiments of the present application provide a method for automatic vulnerability repair, which can integrate all types of application programs and all patch files corresponding to all versions in a patch file library. When performing vulnerability repair, the corresponding target patch file can be found from the patch file library so that the target patch file can repair the vulnerability. Some embodiments of the present application can realize the automatic search and upload of the target patch file, without manual participation, avoiding version incompatibility problems, improving the efficiency and accuracy of vulnerability repair, with a high degree of intelligence, and saving labor and time costs.

[0029] The following combines the attached Figure 1 Exemplarily elaborate on the overall composition structure of the automatic vulnerability repair system provided by some embodiments of the present application.

[0030] As Figure 1 As shown, some embodiments of the present application provide a system diagram for automatic vulnerability repair. The system diagram for automatic vulnerability repair includes: a terminal 100 and a server 200. Among them, various types of application software programs or application system programs (as a specific example of application programs) are deployed on the terminal 100. A patch file library is pre-deployed in the server 200. The server 200 can detect vulnerabilities in the application programs on the terminal 100. When it detects that a certain application software program or application system program on the terminal 100 has a vulnerability, the server 200 can select the vulnerability to be repaired that needs to be repaired currently, and then automatically select the target patch file from the patch file library. After passing various validations, the target patch file is used to repair the vulnerability to be repaired, and the repaired application program is obtained.

[0031] In some embodiments of the present application, the terminal 100 can be a mobile terminal or a non-portable computer terminal, and the embodiments of the present application do not make specific limitations here.

[0032] In some other embodiments of the present application, if a patch file library can be deployed inside the terminal 100, and the terminal 100 has the functions of vulnerability detection, target patch file search, and vulnerability repair with the server 200, the server 200 can not be set at this time. Specifically, it can be selected according to the actual application scenario, and the embodiments of the present application do not make specific limitations here.

[0033] The following combines the attachedFigure 2 Exemplarily illustrate the implementation process of automatic vulnerability repair executed by the server 200 provided by some embodiments of the present application.

[0034] Please refer to the appendix Figure 2 , Figure 2 For some embodiments of the present application, it is a flowchart of a method for automatic vulnerability repair. The method for automatic vulnerability repair may include: S210, determine a vulnerability to be repaired for the current repair operation from at least one vulnerability existing in the application program.

[0035] For example, in some embodiments of the present application, when the server 200 executes a repair task, it first needs to select a vulnerability to be repaired that can be repaired currently from at least one vulnerability.

[0036] In some embodiments of the present application, S210 may include: obtaining the at least one vulnerability, and performing priority sorting on the at least one vulnerability according to a sorting rule to obtain a vulnerability repair queue; wherein, the sorting rule includes: repair difficulty, repair duration, or version importance; determine the vulnerability to be repaired from the vulnerability repair queue.

[0037] For example, in some embodiments of the present application, the server 200 may use a vulnerability detection model or a vulnerability detection algorithm to regularly detect the application program on the terminal 100 and obtain one or more vulnerabilities existing therein. Since the causes and types of vulnerabilities are diverse, the at least one vulnerability can be sorted by priority to determine the repair order to ensure that important vulnerabilities can be repaired first. For example, a sorting rule composed of the order of vulnerability generation, repair difficulty, repair time length, or version importance, etc. can be sorted to obtain a vulnerability repair queue. Repair in sequence according to the priority order in the vulnerability repair queue, and thus the current vulnerability to be repaired can be determined. In addition, for a vulnerability with a long repair duration (for example, the repair duration exceeds a time threshold), an additional repair period needs to be set, for example, repair during the idle period of the application program to ensure the normal processing of other services. It should be understood that the sorting rule and the time threshold can be flexibly set according to the actual application scenario, and the embodiments of the present application do not make specific limitations here.

[0038] To achieve automatic vulnerability repair, in some embodiments of the present application, before executing S220, the method for automatic vulnerability repair further includes: obtaining various patch files corresponding to various vulnerability types existing in various versions of the application program; integrating the various patch files into the patch file library in the form of a directory.

[0039] For example, in some embodiments of the present application, patch files for multiple vulnerabilities are stored in the same patch file library to achieve automatic search for target patch files. Specifically, different patch files are constructed according to factors such as different software (or system) types and Bug types (i.e., vulnerability types); the patch files and the corresponding Bugs can be stored in the form of a directory. For example, patch files corresponding to each vulnerability among all possible vulnerabilities for different versions under a certain software directory. In addition, the hash value of each patch file (as a specific example of the verification value) needs to be stored in the patch file library to ensure that each patch file has not been tampered with. Or, the function hash value of each patch function in each patch file (as a specific example of the function feature value) is stored in the patch file library, and verification can be performed as needed during use to ensure that each patch file has not been tampered with and reduce the calculation cost.

[0040] In some embodiments of the present application, the method for automatic vulnerability repair further includes: after detecting the generation of a new patch file, updating the patch file library with the new patch file.

[0041] For example, in some embodiments of the present application, the patch file library can be continuously updated. That is, when a new patch file is generated, it can be automatically or manually updated to the patch file library to enhance its repair ability.

[0042] S220, search for the target patch file corresponding to the vulnerability to be repaired from the patch file library; wherein, the patch file library contains patch files corresponding to multiple different types of vulnerabilities; the multiple different types of vulnerabilities and the patch files are stored in the form of a directory.

[0043] For example, in some embodiments of the present application, the target patch file corresponding to the vulnerability to be repaired can be searched from the patch file library based on the version to which the vulnerability to be repaired belongs. Or, first extract the characteristics of the vulnerability to be repaired, find multiple patch files through the characteristics, and then select the target patch file from the multiple patch files based on the version. The search method can be flexibly adjusted, and the embodiments of the present application are not limited thereto.

[0044] In some embodiments of the present application, before executing S230, the method for automatic vulnerability repair further includes: verifying the target patch file.

[0045] In one implementation, calculate the target patch file to obtain the value to be verified; confirm that the value to be verified is consistent with the verification value of the target patch file pre-stored in the patch file library, then the target patch file passes the verification.

[0046] For example, in some embodiments of the present application, a hash calculation is performed on the found target patch file to obtain a hash value to be verified (as a specific example of the value to be verified). If the hash value to be verified is consistent with the hash value stored in the patch file library, the verification is passed, indicating that the file has not been tampered with and can be used safely at this time.

[0047] In another implementation, a patch function corresponding to the vulnerability to be repaired is obtained from the target patch file; a value to be verified is calculated for the patch function; if it is confirmed that the value to be verified is consistent with the function feature value of the patch function pre-stored in the patch file library, the target patch file passes the verification.

[0048] For example, in some embodiments of the present application, since there may be multiple patch functions involved in the target patch file, and only some of the patch functions may be required for the vulnerability to be repaired. At this time, the patch function to be used can be found from the target patch file, and a hash value calculation is performed on it to obtain a hash value to be verified. If the hash value to be verified is consistent with the function hash value stored in the patch file library, the verification is passed, indicating that the patch function has not been tampered with and can be used safely at this time.

[0049] S230, in the case of confirming that the target patch file passes the verification, compare the target patch file with the version to which the vulnerability to be repaired belongs to obtain a comparison result.

[0050] For example, in some embodiments of the present application, in order to prevent data loss and program crashes, before repair, it is also necessary to compare the version to which the vulnerability to be repaired belongs with the content of the target patch file to obtain a comparison result. This comparison result indicates whether the vulnerability to be repaired has been repaired, avoiding other program problems caused by repeated patching.

[0051] In some embodiments of the present application, S230 may include: calculating a first verification value for the content of the target patch file; calculating a second verification value for the version; if the first verification value and the second verification value are consistent, the comparison result is consistent; if the first verification value and the second verification value are inconsistent, the comparison result is inconsistent.

[0052] For example, in some embodiments of the present application, the content (such as, patch function) in the target patch file and the version to be repaired are calculated respectively to obtain a first verification value and a second verification value. If the two are consistent, no repair is required; if the two are inconsistent, the vulnerability to be repaired needs to be repaired. The calculation method can adopt hash value or code similarity calculation, and the embodiments of the present application do not make specific limitations here.

[0053] S240. When the comparison result is inconsistent, use the target patch file to repair the vulnerability to be repaired, and obtain the repaired application program.

[0054] For example, in some embodiments of the present application, the patch function in the target patch file is used to automatically repair the vulnerability to be repaired, and the repaired application program is obtained.

[0055] In some embodiments of the present application, after executing S240, the method for automatic vulnerability repair further includes: regularly comparing the patch file in the repaired application program with the patch file library, and when the patch file in the repaired application program is inconsistent with the one stored in the patch file library, performing a repair operation on the patch file in the repaired application program.

[0056] For example, in some embodiments of the present application, the repaired application program can be regularly maintained. The patch files in the application program are regularly detected, and if it is found that the check value of the patch file of this version is inconsistent with the check value in the stored patch file, an automatic repair operation is performed.

[0057] The following combines the attached Figure 3 Exemplarily elaborate on the specific process of automatic vulnerability repair provided by some embodiments of the present application.

[0058] Please refer to the attached Figure 3 , Figure 3 which is a flowchart of a method for automatic vulnerability repair provided by some embodiments of the present application.

[0059] The following exemplarily elaborates on the above process.

[0060] S310. Determine the vulnerability to be repaired for the current repair operation.

[0061] S320. Search for the target patch file corresponding to the vulnerability to be repaired from the patch file library.

[0062] S330. Calculate the target patch file to obtain the value to be verified; S340. Determine whether the value to be verified is consistent with the one stored in the patch file library. If so, execute S350; otherwise, execute S380.

[0063] S350. Calculate the first check value of the target patch file and the second check value of the version to which the vulnerability to be repaired belongs.

[0064] S360. Determine whether the first check value and the second check value are consistent. If not, execute S370; if so, no repair is performed.

[0065] S370. Use the target patch file to repair the vulnerability to be repaired, and obtain the repaired application program.

[0066] S380: Generate an alarm message and send it to a technician terminal.

[0067] For example, when a target patch file is tampered with, the technical personnel can be informed in time to repair and replace the target patch file in the patch file library.

[0068] It is understandable that the specific implementation process of S310~S370 can refer to the method embodiment provided above, and the detailed description is appropriately omitted here to avoid repetition. It should be understood that S310~S370 only describes the automatic repair process using one vulnerability to be repaired as an example, and in actual applications, the above process can be executed cyclically, that is, after repairing one vulnerability or when the vulnerability to be repaired does not need to be repaired, the next vulnerability can be selected from the repair vulnerability list and the above repair process can be executed again to complete the repair of all vulnerabilities in the application.

[0069] Through some of the embodiments of the present application described above, it can be seen that the present application does not need to consider version compatibility during the process of automatic vulnerability repair. Automatic repair is achieved through automatic search, with high repair accuracy and efficiency, saving time costs.

[0070] Please refer to Figure 4 , Figure 4 The following is a block diagram of the components of the device for automatically repairing vulnerabilities provided by some embodiments of the present application. It should be understood that the device for automatically repairing vulnerabilities corresponds to the above method embodiment and can execute each step involved in the above method embodiment. The specific functions of the device for automatically repairing vulnerabilities can be found in the description above. To avoid repetition, the detailed description is appropriately omitted here.

[0071] Figure 4 The device for automatically repairing vulnerabilities includes at least one software function module that can be stored in a memory in the form of software or firmware or solidified in the device for automatically repairing vulnerabilities, and the device for automatically repairing vulnerabilities includes: a vulnerability determination module 410, used to determine the vulnerability to be repaired that is currently performing a repair operation from at least one vulnerability existing in the application; a patch search module 420, used to search for a target patch file corresponding to the vulnerability to be repaired from the patch file library; wherein the patch file library contains patch files corresponding to multiple different types of vulnerabilities; the multiple different types of vulnerabilities and the patch files are stored in the form of a directory; a comparison module 430, used to compare the target patch file with the version to which the vulnerability to be repaired belongs to, and obtain a comparison result when confirming that the target patch file has passed the verification; a repair module 440, used to repair the vulnerability to be repaired using the target patch file when the comparison result is inconsistent, and obtain a repaired application.

[0072] Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working process of the device described above can refer to the corresponding process in the foregoing method, and will not be elaborated herein.

[0073] Some embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, it can implement the operations corresponding to any of the methods in the foregoing methods provided in the above embodiments.

[0074] Some embodiments of the present application also provide a computer program product, the computer program product includes a computer program, wherein when the computer program is executed by a processor, it can implement the operations corresponding to any of the methods in the foregoing methods provided in the above embodiments.

[0075] As Figure 5 As shown, some embodiments of the present application provide an electronic device 500, and the electronic device 500 includes: a memory 510, a processor 520, and a computer program stored on the memory 510 and executable on the processor 520. Among them, when the processor 520 reads the program from the memory 510 through the bus 530 and executes the program, it can implement the method of any of the above embodiments.

[0076] The processor 520 can process digital signals and can include various computing structures. For example, a complex instruction set computer structure, a reduced instruction set computer structure, or a structure that implements a combination of multiple instruction sets. In some examples, the processor 520 can be a microprocessor.

[0077] The memory 510 can be used to store instructions executed by the processor 520 or data related to the execution of the instructions. These instructions and / or data can include code for implementing some or all of the functions of one or more modules described in the embodiments of the present application. The processor 520 of the present disclosure embodiment can be used to execute the instructions in the memory 510 to implement the method shown above. The memory 510 includes dynamic random access memory, static random access memory, flash memory, optical memory, or other memories well known to those skilled in the art.

[0078] The above are only the embodiments of the present application and are not used to limit the protection scope of the present application. For those skilled in the art, the present application can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that similar reference numerals and letters denote similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings.

[0079] As described above, it is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of changes or substitutions, which should all be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims described above.

[0080] It should be noted that, in this text, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of another identical element in the process, method, article or device including the said element.

Claims

1. A method for automatic vulnerability repair, characterized in that Including: Determine a vulnerability to be repaired for the current repair operation from at least one vulnerability existing in the application; Search for a target patch file corresponding to the vulnerability to be repaired from the patch file library; wherein, the patch file library contains patch files corresponding to various different types of vulnerabilities; the various different types of vulnerabilities and the patch files are stored in the form of a directory; When it is confirmed that the target patch file passes the verification, compare the target patch file with the version to which the vulnerability to be repaired belongs, and obtain a comparison result; When the comparison result is inconsistent, use the target patch file to repair the vulnerability to be repaired, and obtain a repaired application.

2. The method according to claim 1, wherein The determining a vulnerability to be repaired for the current repair operation from at least one vulnerability existing in the application includes: Obtain the at least one vulnerability, and perform priority sorting on the at least one vulnerability according to a sorting rule to obtain a queue of vulnerabilities to be repaired; wherein, the sorting rule includes: repair difficulty, repair duration, or version importance; Determine the vulnerability to be repaired from the queue of vulnerabilities to be repaired.

3. The method according to claim 1 or 2, characterized in that, Before searching for a target patch file corresponding to the vulnerability to be repaired from the patch file library, the method further includes: Obtain various patch files corresponding to various vulnerability types existing in various versions of the application; Integrate the various patch files into the patch file library in the form of a directory.

4. The method according to claim 1 or 2, characterized in that The confirming that the target patch file passes the verification includes: Perform a calculation on the target patch file to obtain a value to be verified; If it is confirmed that the value to be verified is consistent with the verification value of the target patch file pre-stored in the patch file library, then the target patch file passes the verification; or, Obtain a patch function corresponding to the vulnerability to be repaired from the target patch file; Perform a calculation on the patch function to obtain a value to be verified; If it is confirmed that the value to be verified is consistent with the function feature value of the patch function pre-stored in the patch file library, then the target patch file passes the verification.

5. The method according to claim 1 or 2, characterized in that, The comparing the target patch file with the version to which the vulnerability to be repaired belongs and obtaining a comparison result includes: Perform a calculation on the content of the target patch file to obtain a first verification value; Perform a calculation on the version to obtain a second verification value; If the first verification value and the second verification value are consistent, then the comparison result is consistent; If the first verification value and the second verification value are inconsistent, then the comparison result is inconsistent.

6. The method according to claim 1 or 2, characterized in that, The method further includes: After monitoring the generation of a new patch file, update the patch file library with the new patch file.

7. The method according to claim 1 or 2, characterized in that, After obtaining the repaired application, the method further includes: Regularly compare the patch files in the repaired application with the patch file library, and when the patch files in the repaired application are inconsistent with those stored in the patch file library, perform a repair operation on the patch files in the repaired application.

8. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, wherein the computer program, when run by a processor, executes the method according to any one of claims 1-7.

9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the computer program, when run by the processor, executes the method according to any one of claims 1-7.

10. A computer program product, characterized in that, The computer program product includes a computer program, wherein the computer program, when run by a processor, executes the method according to any one of claims 1-7.

Images