Vulnerability scanning method and device, equipment and storage medium

Abstract

The invention relates to the technical field of network security, in particular to a vulnerability scanning method and device, equipment and a storage medium. The target account user name is generated through simulation, the identity verification request is sent to the cloud server according to the target account user name to start virtual identity verification, and finally the vulnerability scanning strategy of the corresponding category is determined according to the category of the identity verification response fed back by the cloud server. Therefore, automatic vulnerability scanning is realized according to the vulnerability scanning strategy, the accuracy of identity verification is improved, the technical problem that the website has potential safety hazards due to defects of an automatic vulnerability scanning mechanism for website identity verification in the prior art is avoided, various verification scenes can be simulated, and the scanning efficiency is improved.

Description

Technical Field

[0001] The present invention relates to the field of network security technology, and in particular to a vulnerability scanning method, device, equipment and storage medium. Background Art

[0002] When website users use functions such as registration or password reset, there are identity authentication loopholes. In order to improve the operating efficiency of the website, an automated response mechanism is generally adopted. However, the existing automated vulnerability scanning mechanism has defects, which poses a security risk to the website.

[0003] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0004] The main purpose of the present invention is to provide a vulnerability scanning method, device, equipment and storage medium, aiming to solve the technical problem that the automated vulnerability scanning mechanism for website identity authentication in the prior art has defects, resulting in security risks for the website.

[0005] To achieve the above object, the present invention provides a vulnerability scanning method, which comprises the following steps:

[0006] When receiving a vulnerability scanning request, generate the target account username;

[0007] Sending an identity authentication request to a cloud server based on the target account username, so that the cloud server feeds back an identity authentication response;

[0008] Determining a category of the identity authentication response and a corresponding vulnerability scanning strategy;

[0009] Execute the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results.

[0010] Optionally, executing the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results includes:

[0011] When the category of the identity authentication response is verification code information, determining the verification code category of the verification code information;

[0012] When the verification code category is a first type of verification code, performing verification code blasting on the verification code information to obtain a blasting result;

[0013] Generate vulnerability scanning results according to the blasting results.

[0014] Optionally, performing verification code blasting on the verification code information to obtain a blasting result includes:

[0015] Get the number information of the first type of verification code input box;

[0016] Generate a first type of verification code by enumeration according to the quantity information;

[0017] Fill the generated first type of verification code into the first type of verification code input box to send an account update request to the cloud server, wherein the account update request includes: at least one of an account registration request, a password reset request, and an account login request;

[0018] receiving feedback information from the cloud server based on the account update request;

[0019] The blasting result is determined according to the feedback information.

[0020] Optionally, determining the blasting result according to the feedback information includes:

[0021] When the feedback result is that the account update fails, return to the step of generating the first type of verification code by enumeration according to the quantity information until the account update is successful and / or the enumeration duration is greater than or equal to the preset first duration.

[0022] Optionally, the step of performing verification code blasting on the verification code information to obtain a blasting result further includes:

[0023] Reading the first type of verification code information or verification link in the identity verification response through a preset communication interface;

[0024] Performing defect detection on the first type of verification code information;

[0025] Performing controllability detection on the verification link;

[0026] Generate blasting results based on the detection results.

[0027] Optionally, the performing defect detection on the first type of verification code includes:

[0028] Detecting whether the first type of verification code is the same as a historical verification code within a preset number of times; and / or

[0029] Detect whether the first type of verification code is in a binding state.

[0030] Optionally, executing the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results also includes:

[0031] When the verification code category is a second-category verification code, performing image recognition on the second-category verification code by using a preset image recognition model;

[0032] A vulnerability scan is performed based on the image recognition result to obtain the vulnerability scan result.

[0033] Optionally, the performing image recognition on the second type of verification code by using a preset image recognition model includes:

[0034] Determining the verification type of the second type of verification code;

[0035] Determining an image verification strategy according to the verification type of the second type of verification code;

[0036] The second type of verification code is subjected to image verification based on the image verification strategy, and the image verification includes: position detection or trigger detection.

[0037] Optionally, generating a target account username includes:

[0038] Receive account information or dictionary information input by the user;

[0039] determining target format information according to at least one of the account information and / or the dictionary information;

[0040] A target account username is generated according to the target format information.

[0041] Optionally, the target format information includes: character category, character quantity and restriction information;

[0042] The determining the target format information according to at least one of the account information and / or the dictionary information includes:

[0043] Performing regular expression recognition on the account information to obtain character categories, character quantities, and restriction information corresponding to the account information; and / or

[0044] Reading the character category, character quantity and restriction information stored in the dictionary information;

[0045] Accordingly, generating a target account username according to the target format information includes:

[0046] A target account username is generated according to the character category, the number of characters, and the restriction information.

[0047] Optionally, the executing the vulnerability scanning strategy to perform vulnerability scanning and obtaining the vulnerability scanning result further includes:

[0048] Get the number of identity authentication requests within the preset second time period;

[0049] When the number of identity authentication requests is less than a preset request number threshold, matching the vulnerability scan result with historical vulnerability scan results within the preset request number threshold;

[0050] When the match fails, the number of identity authentication requests is recorded as the limit number, and the preset request number threshold is updated according to the limit number.

[0051] In addition, to achieve the above object, the present invention also provides a vulnerability scanning device, the vulnerability scanning device comprising:

[0052] A generation module, used to generate a target account username when receiving a vulnerability scanning request;

[0053] A request module, used to send an identity authentication request to a cloud server based on the target account username, so that the cloud server feeds back an identity authentication response;

[0054] A formulation module for determining the category of the authentication response and the corresponding vulnerability scanning strategy;

[0055] The scanning module is used to execute the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results.

[0056] Optionally, the scanning module is further used to determine the verification code category of the verification code information when the category of the identity authentication response is verification code information;

[0057] When the verification code category is a first type of verification code, performing verification code blasting on the verification code information to obtain a blasting result;

[0058] Generate vulnerability scanning results according to the blasting results.

[0059] Optionally, the scanning module is further used to obtain the quantity information of the first type of verification code input box;

[0060] Generate a first type of verification code by enumeration according to the quantity information;

[0061] Fill the generated first type of verification code into the first type of verification code input box to send an account update request to the cloud server, wherein the account update request includes: at least one of an account registration request, a password reset request, and an account login request;

[0062] receiving feedback information from the cloud server based on the account update request;

[0063] The blasting result is determined according to the feedback information.

[0064] Optionally, the scanning module is further used to return to the step of generating a first type of verification code by enumeration according to the quantity information when the feedback result is that the account update fails, until the account update is successful and / or the enumeration duration is greater than or equal to a preset first duration.

[0065] Optionally, it is also used to read the first type of verification code information or verification link in the identity authentication response through a preset communication interface;

[0066] Performing defect detection on the first type of verification code information;

[0067] Performing controllability detection on the verification link;

[0068] Generate blasting results based on the detection results.

[0069] Optionally, it is also used to detect whether the first type of verification code is the same as a historical verification code within a preset number of times; and / or

[0070] Detect whether the first type of verification code is in a binding state.

[0071] Optionally, when the verification code category is a second type of verification code, performing image recognition on the second type of verification code by using a preset image recognition model;

[0072] A vulnerability scan is performed based on the image recognition result to obtain the vulnerability scan result.

[0073] In addition, to achieve the above-mentioned purpose, the present invention also proposes a vulnerability scanning device, which includes: a memory, a processor, and a vulnerability scanning program stored in the memory and executable on the processor, and the vulnerability scanning program is configured to implement the steps of the vulnerability scanning method described above.

[0074] In addition, to achieve the above-mentioned purpose, the present invention further proposes a storage medium, on which a vulnerability scanning program is stored, and when the vulnerability scanning program is executed by a processor, the steps of the vulnerability scanning method described above are implemented.

[0075] The present invention discloses a vulnerability scanning method, which comprises: upon receiving a vulnerability scanning request, generating a target account user name; sending an identity authentication request to a cloud server based on the target account user name, so that the cloud server feeds back an identity authentication response; determining the category of the identity authentication response and a corresponding vulnerability scanning strategy; executing the vulnerability scanning strategy to perform vulnerability scanning and obtain a vulnerability scanning result. Compared with the prior art, the present invention generates a target account user name by simulation, and sends an identity authentication request to a cloud server according to the target account user name to start a virtual identity authentication, and finally determines a vulnerability scanning strategy of a corresponding category according to the category of the identity authentication response fed back by the cloud server, and then implements automated vulnerability scanning according to the vulnerability scanning strategy, thereby improving the accuracy of identity authentication, avoiding the technical problem that the automated vulnerability scanning mechanism for website identity authentication in the prior art has defects, resulting in security risks for the website, and can simulate various verification scenarios to improve scanning efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] Figure 1 It is a schematic diagram of the structure of a vulnerability scanning device for a hardware operating environment involved in an embodiment of the present invention;

[0077] Figure 2 This is a flow chart of a first embodiment of a vulnerability scanning method of the present invention;

[0078] Figure 3 This is a flow chart of a second embodiment of the vulnerability scanning method of the present invention;

[0079] Figure 4 A schematic diagram of a flow chart of a third embodiment of a vulnerability scanning method of the present invention;

[0080] Figure 5 It is a structural block diagram of the first embodiment of the vulnerability scanning device of the present invention.

[0081] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0082] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0083] Reference Figure 1 , Figure 1 The figure is a schematic diagram of the structure of a vulnerability scanning device for a hardware operating environment involved in an embodiment of the present invention.

[0084] like Figure 1 As shown, the vulnerability scanning device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a wireless fidelity (Wireless-Fidelity, Wi-Fi) interface). The memory 1005 may be a high-speed random access memory (Random Access Memory, RAM), or a stable non-volatile memory (Non-Volatile Memory, NVM), such as a disk storage. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0085] Those skilled in the art will understand that Figure 1 The structure shown in the figure does not constitute a limitation on the vulnerability scanning device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0086] like Figure 1 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a vulnerability scanning program.

[0087] exist Figure 1 In the vulnerability scanning device shown, the network interface 1004 is mainly used for data communication with the network server; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and the memory 1005 in the vulnerability scanning device of the present invention can be set in the vulnerability scanning device, and the vulnerability scanning device calls the vulnerability scanning program stored in the memory 1005 through the processor 1001, and executes the vulnerability scanning method provided by the embodiment of the present invention.

[0088] The embodiment of the present invention provides a vulnerability scanning method, referring to Figure 2 , Figure 2 The figure is a flow chart of a first embodiment of a vulnerability scanning method of the present invention.

[0089] In this embodiment, the vulnerability scanning method includes the following steps:

[0090] Step S10: upon receiving a vulnerability scanning request, generating a target account username.

[0091] It should be noted that the executor of the method of this embodiment can be a device with data input, data processing and network communication functions, such as a control computer, a mobile terminal or a remote device, etc. It can also be other devices that can achieve the same or similar functions. This embodiment does not impose specific restrictions on this. In this embodiment and the following embodiments, the control computer will be used as an example for explanation.

[0092] It is worth mentioning that in the process of website security protection, since the website cannot restrict the information input by the user, when there is a malicious account attack, some website accounts may be tampered with or reset, which may cause security risks to users or the website, affecting user use and causing economic losses.

[0093] It should be noted that a vulnerability scanning request refers to a control instruction input by a user for performing a vulnerability test or scan on a target website for a user account, such as running a vulnerability scanning program or a vulnerability scanning script, etc. This embodiment does not impose any specific restrictions on this, wherein a target website refers to a website for which a vulnerability scan is required for an account.

[0094] It can be understood that the account username refers to a user name that conforms to the setting format of the target website. Since this application is intended to perform vulnerability scanning tests, the account username in this embodiment is an automatically generated virtual account name, and there are different differences depending on the setting format.

[0095] Further, generating the target account username includes:

[0096] Receive account information or dictionary information input by the user;

[0097] determining target format information according to at least one of the account information and / or the dictionary information;

[0098] A target account username is generated according to the target format information.

[0099] It should be understood that in order to generate a target account user name that conforms to the set format of the target website, this embodiment can pre-collect the correct account name provided by the user and analyze it to obtain the set format of the target website, wherein the target format information includes character category, number of characters and restriction information.

[0100] For example: if the setting format of the target website is pure numbers of more than eight digits, then the generated account username can be 12345678. If the setting format of the target website is a combination of numbers and letters of more than eight digits, and the letters are limited to uppercase, then the generated account username can be 1234ABCD. This embodiment is only for illustration and no specific limitation is imposed on this.

[0101] It should be noted that the process of analyzing the account information input by the user may be regular expression recognition of the account information to obtain the format information or restriction information contained in the account information, or may be other information analysis methods that can achieve the same or similar functions. This embodiment does not impose any specific restrictions on this.

[0102] In addition, in addition to obtaining the character category, number of characters and restriction information by analyzing the correct account username entered by the user, this embodiment can also generate a target account username based on dictionary information pre-set by the user, where the dictionary information is used to limit the format of the account username or password of the target website.

[0103] Further, the determining the target format information according to at least one of the account information and / or the dictionary information includes:

[0104] Performing regular expression recognition on the account information to obtain character categories, character quantities, and restriction information corresponding to the account information; and / or

[0105] Reading the character category, character quantity and restriction information stored in the dictionary information;

[0106] Accordingly, generating a target account username according to the target format information includes:

[0107] A target account username is generated according to the character category, the number of characters, and the restriction information.

[0108] It should be noted that regular recognition can be a process of screening, matching or classifying the account information through a pre-set regular expression. For example, for the account username of 1234ABcd, regular recognition is performed, and the regular expression is: whether there are numbers, letters, uppercase and lowercase letters, and special symbols in the character string. It can be seen that the above account username character string includes numbers, uppercase and lowercase letters, and no special symbols. Finally, in order to ensure that other unknown restrictions are not triggered, the generated account username can be generated according to the number of characters being 8, the character categories including: numbers, uppercase and lowercase letters, and the restriction information being: no special characters, to generate an account username, such as: 1A2B3c4d or 1a2B3c4D, etc. This embodiment is only used as an example to illustrate this.

[0109] In this embodiment, whether performing regular expression recognition on the account information input by the user or analyzing the dictionary information to obtain format information such as character category, number of characters, and restriction information, it is used to limit the format of the account username to generate multiple account usernames for account vulnerability scanning tests.

[0110] Step S20: Send an identity authentication request to the cloud server based on the target account username, so that the cloud server feeds back an identity authentication response.

[0111] It is worth noting that the cloud server can be the operating server of the target website, which can be used to maintain and support the operating status of the target website, receive various operations from users, and execute the received operations. This embodiment does not impose specific restrictions on this.

[0112] It should be understood that an identity authentication request refers to a process in which a control computer sends an identity authentication request to a cloud server to establish a communication connection between the control computer and the cloud server, and receives an identity authentication response fed back by the cloud server for matching. In this process, identity authentication can be SMS identity authentication, graphic identity authentication, or other authentication methods that can verify the uniqueness of an account. This embodiment does not impose any specific restrictions on this.

[0113] Step S30: Determine the category of the identity authentication response and the corresponding vulnerability scanning strategy.

[0114] It can be understood that in this embodiment, the types of identity authentication responses include: account verification, verification code verification, and number of operation verification, etc. According to the different categories of identity authentication responses, there are different account vulnerability scanning strategies. For example: when performing SMS verification, it is possible to match whether the SMS verification code fed back by the cloud server is consistent with the content entered by the subsequent user; or when performing graphic verification, it is possible to detect whether the graphic clicked or touched by the user is consistent with the pre-marked one, etc. This embodiment does not impose specific restrictions on this.

[0115] Step S40: Execute the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results.

[0116] It should be understood that in the actual identity authentication process, it is necessary to combine the subsequent user operation information for comprehensive evaluation to obtain the vulnerability scanning result. Therefore, when executing the vulnerability scanning strategy to perform vulnerability scanning, it is necessary to automatically respond to the identity authentication. The vulnerability scanning in this embodiment is to execute the corresponding category of response process according to the category of identity authentication response. For example: if a text message verification vulnerability scan is required, the control calculation automatically inputs a text message verification code, and monitors whether the identity authentication is passed, and then determines whether there is an identity authentication vulnerability; if graphic verification is required, graphic recognition, clicks, conversions and other operations can be automatically performed according to the trained convolutional neural network algorithm, and other verification processes can also be performed. This embodiment does not impose specific restrictions on this.

[0117] The present embodiment discloses a vulnerability scanning method, which includes: generating a target account username upon receiving a vulnerability scanning request; sending an identity authentication request to a cloud server based on the target account username, so that the cloud server feeds back an identity authentication response; determining the category of the identity authentication response and the corresponding vulnerability scanning strategy; executing the vulnerability scanning strategy to perform a vulnerability scan and obtain a vulnerability scanning result. The present embodiment generates a target account username by simulation, and sends an identity authentication request to a cloud server according to the target account username to start a virtual identity authentication. Finally, a vulnerability scanning strategy of a corresponding category is determined according to the category of the identity authentication response fed back by the cloud server, and then an automated vulnerability scan is implemented according to the vulnerability scanning strategy, thereby improving the accuracy of identity authentication, avoiding the technical problem that the automated vulnerability scanning mechanism for website identity authentication in the prior art has defects, resulting in security risks for the website, and can simulate various verification scenarios to improve scanning efficiency.

[0118] refer to Figure 3 , Figure 3 The figure is a flow chart of a second embodiment of a vulnerability scanning method of the present invention.

[0119] Based on the above first embodiment, in this embodiment, step S40 includes:

[0120] Step S401: when the category of the identity authentication response is verification code information, determine the verification code category of the verification code information.

[0121] It should be noted that the categories of verification code information include but are not limited to: SMS verification code, email verification code, network connection verification code, and graphic verification code, etc. It can also be a verification code such as human-machine verification that can achieve identity authentication effects. This embodiment does not make specific restrictions on this.

[0122] Step S402: When the verification code category is a first type of verification code, verification code blasting is performed on the verification code information to obtain a blasting result.

[0123] It is worth noting that the first type of verification code specifically refers to a verification code that requires the user to respond or enter information based on the identity authentication response fed back by the cloud server, such as: SMS verification code, email verification code, and network link verification code.

[0124] In a specific implementation, the verification code blasting for the first type of verification code can be performed by enumerating and inputting according to the verification code category, and a large amount of data is input to achieve the purpose of deciphering the verification code. For example, for the blasting of SMS verification codes, a certain amount of input information can be enumerated according to the allowed character types, and it can be entered into the corresponding input box to achieve the purpose of identity authentication.

[0125] Further, the verification code information is subjected to verification code blasting to obtain a blasting result, including:

[0126] Get the number information of the first type of verification code input box;

[0127] Generate a first type of verification code by enumeration according to the quantity information;

[0128] Fill the generated first type of verification code into the first type of verification code input box to send an account update request to the cloud server, wherein the account update request includes: at least one of an account registration request, a password reset request, and an account login request;

[0129] receiving feedback information from the cloud server based on the account update request;

[0130] The blasting result is determined according to the feedback information.

[0131] It should be noted that although there is a possibility of blasting the verification code through identity authentication, since the basic information that constitutes the facilitating part of the first type of verification code has a large variable, in order to reduce the workload and improve the efficiency of the vulnerability scanning for identity authentication in this embodiment, this embodiment can first determine the number of characters of the first type of verification code, where the number of characters can be determined according to the number of SMS verification code input boxes, or when facing email verification or network link verification, it can be determined according to the number of operable domain name characters. For example: if the number of character input boxes is 4, then the generated verification code should also be a 4-digit string:, similarly, if the number of operable domain name characters is 5, then the generated email or network link domain name information should also be modified accordingly, for example: www.XXXXX.com or XXXXX@163.com, etc. This embodiment does not make specific restrictions on this.

[0132] It should be understood that after the generated first type of verification code is entered into the verification box, an account update request can be initiated to the cloud server, and the account update request includes: at least one of an account registration request, a password reset request, and an account login request, so that the cloud server can feedback the corresponding feedback result to determine whether the identity authentication is passed. If passed, it means that there is a vulnerability. If not, it means that there is no vulnerability. Among them, whether it is passed or not can only be determined after the entire enumeration process is completed.

[0133] Further, determining the blasting result according to the feedback information includes:

[0134] When the feedback result is that the account update fails, return to the step of generating the first type of verification code by enumeration according to the quantity information until the account update is successful and / or the enumeration duration is greater than or equal to the preset first duration.

[0135] The preset first duration may be set to 5 minutes or 10 minutes, and may also be set by the user, and this embodiment does not impose any specific limitation on this.

[0136] In addition, when facing identity authentication via certain SMS or network links, the email or network link fed back by the cloud server may have defects. For example, the SMS verification code fed back by the cloud server should be dynamic or different, but the SMS verification code fed back each time is the same, resulting in loopholes that can be easily deciphered. For example, the network connection for identity authentication is the same each time, and any method of establishing a communication connection with the network connection will be allowed. These will directly affect the accuracy of identity authentication. Therefore, when blasting the verification code information, it should also be detected for defects.

[0137] Furthermore, the step of performing verification code blasting on the verification code information to obtain a blasting result further includes:

[0138] Reading the first type of verification code information or verification link in the identity verification response through a preset communication interface;

[0139] Performing defect detection on the first type of verification code information;

[0140] Performing controllability detection on the verification link;

[0141] Generate blasting results based on detection results

[0142] In a specific implementation, after the cloud server returns the SMS / email verification code to the control computer via HTTP, the control computer will automatically trigger the acquisition of the verification code, check whether the data packet returned by the cloud server contains the verification code, and determine whether the verification code will change, whether the account name is bound to the verification code, and whether the account name is bound to the mobile phone number, etc. This embodiment does not impose any specific restrictions on this.

[0143] Further, the performing defect detection on the first type of verification code includes:

[0144] Detecting whether the first type of verification code is the same as a historical verification code within a preset number of times; and / or

[0145] Detect whether the first type of verification code is in a binding state.

[0146] It is understandable that no matter which established rules are used to generate the first type of verification code, there is a certain possibility that it is the same as the historical verification code. Therefore, it is only necessary to detect and compare the historical verification codes within 1,000 times.

[0147] Step S403: Generate vulnerability scanning results according to the blasting results.

[0148] This embodiment implements vulnerability scanning in the identity authentication process of traditional technologies by blasting verification codes such as text messages, emails, or network links, thereby improving the efficiency of automated vulnerability scanning.

[0149] In this embodiment, the step S40 further includes:

[0150] Step S401`: when the verification code category is a second-category verification code, image recognition is performed on the second-category verification code by using a preset image recognition model.

[0151] It should be noted that the second type of verification code refers to a graphic verification code, wherein the graphic verification code may be a combination of one or more graphics, and this embodiment does not impose any specific limitation on this.

[0152] It can be understood that the preset image recognition model can be an image recognition model obtained by training based on a convolutional neural network algorithm, which is used to perform corresponding analog control operations on graphics, such as position detection or trigger detection, etc. This embodiment does not impose specific restrictions on this.

[0153] Furthermore, the performing image recognition on the second type of verification code by using a preset image recognition model includes:

[0154] Determining the verification type of the second type of verification code;

[0155] Determining an image verification strategy according to the verification type of the second type of verification code;

[0156] The second type of verification code is subjected to image verification based on the image verification strategy, and the image verification includes: position detection or trigger detection.

[0157] In a specific implementation, position detection refers to detection of the position of an image, such as image gap filling, image movement, etc. Trigger detection refers to specific graphic clicks, image classification, and image query, etc. This embodiment does not impose specific restrictions on this.

[0158] Step S402`: Perform vulnerability scanning according to the image recognition result to obtain vulnerability scanning results.

[0159] It should be noted that the image recognition result can be to detect the integrity, similarity and matching degree of the image. After all the above are passed, it is determined that there is no loophole.

[0160] This embodiment realizes vulnerability scanning in the identity authentication process of traditional technologies by identifying graphic verification codes, thereby improving the efficiency of automated vulnerability scanning.

[0161] refer to Figure 4 , Figure 4 Schematic diagram of a flow chart of a third embodiment of a vulnerability scanning method of the present invention.

[0162] Based on the above second embodiment, in this embodiment, after step S40, the following is further included:

[0163] Step S50: Obtain the number of identity authentication requests within a preset second time period.

[0164] It should be noted that the preset second time length may be set to 10 minutes, or may be set by the user, and this embodiment does not impose any specific limitation on this.

[0165] It is worth noting that if the number of access requests to an account is not limited, authentication will inevitably be cracked if the number of requests is constantly enumerated. Vulnerability detection can detect the number of times this process is performed in order to simulate the user input process during the authentication process.

[0166] Step S60: When the number of identity authentication requests is less than a preset request number threshold, the vulnerability scanning result is matched with the historical vulnerability scanning result within the preset request number threshold.

[0167] It is understandable that the preset request number threshold may be set to 20 times or 50 times, etc., and this embodiment does not impose any specific limitation on this.

[0168] In the specific implementation, if the target has a limit on the number of registration requests within a short period of time, 50 registration or password reset requests are made in advance, and the target return content is continuously observed to see if it is different from before. Since registration or password reset operations may be prohibited if verification fails within these 50 times, and input is prohibited if the number of requests is not less than the preset number of requests, the limit can be determined by whether the returned content is different from before.

[0169] Step S70: When the match fails, the number of identity authentication requests is recorded as a limit number, and a preset request number threshold is updated according to the limit number.

[0170] In the specific implementation, the login limit must be later than errors such as graphic verification code error, SMS verification code error, email verification code error, illegal username, etc. Therefore, through continuous observation, if an error return different from the previous one is found after 20 times, it is most likely due to the limit on the number of logins.

[0171] This embodiment limits the number of requests to improve the accuracy of vulnerability scanning, reduce invalid operations, and prevent the website from being attacked.

[0172] In addition, an embodiment of the present invention further provides a storage medium, on which a vulnerability scanning program is stored. When the vulnerability scanning program is executed by a processor, the steps of the vulnerability scanning method described above are implemented.

[0173] Since the storage medium adopts all the technical solutions of all the above embodiments, it has at least all the beneficial effects brought by the technical solutions of the above embodiments, which will not be described one by one here.

[0174] Reference Figure 5 , Figure 5 It is a structural block diagram of the first embodiment of the vulnerability scanning device of the present invention.

[0175] like Figure 5 As shown, the vulnerability scanning device proposed in the embodiment of the present invention includes:

[0176] The generating module 10 is used to generate a target account username when receiving a vulnerability scanning request.

[0177] The request module 20 is used to send an identity authentication request to the cloud server based on the target account username, so that the cloud server feeds back an identity authentication response.

[0178] The formulation module 30 is used to determine the category of the identity authentication response and the corresponding vulnerability scanning strategy.

[0179] The scanning module 40 is used to execute the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results.

[0180] In one embodiment, the scanning module 40 is further used to determine the verification code category of the verification code information when the category of the identity authentication response is verification code information; when the verification code category is a first type of verification code, perform verification code blasting on the verification code information to obtain a blasting result; and generate a vulnerability scanning result based on the blasting result.

[0181] In one embodiment, the scanning module 40 is also used to obtain the quantity information of the first type of verification code input box; enumerate and generate the first type of verification code according to the quantity information; fill the generated first type of verification code into the first type of verification code input box to send an account update request to the cloud server, and the account update request includes: at least one of an account registration request, a password reset request and an account login request; receive feedback information from the cloud server based on the account update request; determine the blasting result according to the feedback information.

[0182] In one embodiment, the scanning module 40 is further used to return to the step of generating a first type of verification code by enumerating according to the quantity information when the feedback result is that the account update fails, until the account update is successful and / or the enumeration duration is greater than or equal to a preset first duration.

[0183] In one embodiment, the scanning module 40 is further used to read the first type of verification code information or verification link in the identity authentication response through a preset communication interface; perform defect detection on the first type of verification code information; perform controllability detection on the verification link; and generate a blasting result based on the detection result.

[0184] In one embodiment, the scanning module 40 is further used to detect whether the first type of verification code is the same as a historical verification code within a preset number of times; and / or detect whether the first type of verification code is in a binding state.

[0185] In one embodiment, the scanning module 40 is further used to perform image recognition on the second-category verification code by using a preset image recognition model when the verification code category is a second-category verification code; and perform vulnerability scanning according to the image recognition result to obtain a vulnerability scanning result.

[0186] In one embodiment, the scanning module 40 is further used to determine the verification type of the second type of verification code; determine the image verification strategy according to the verification type of the second type of verification code; perform image verification on the second type of verification code based on the image verification strategy, and the image verification includes: position detection or trigger detection.

[0187] In one embodiment, the generating module 10 is further used to receive account information or dictionary information input by a user; determine target format information according to at least one of the account information and / or the dictionary information; and generate a target account username according to the target format information.

[0188] In one embodiment, the generating module 10 is further used to perform regular expression recognition on the account information to obtain the character category, character quantity and restriction information corresponding to the account information; and / or read the character category, character quantity and restriction information stored in the dictionary information; accordingly, generating the target account username according to the target format information includes: generating the target account username according to the character category, the character quantity and the restriction information.

[0189] In one embodiment, the scanning module 40 is also used to obtain the number of identity authentication requests within a preset second time period; when the number of identity authentication requests is less than a preset request number threshold, the vulnerability scanning result is matched with the historical vulnerability scanning result within the preset request number threshold; when the match fails, the number of identity authentication requests is recorded as a limited number, and the preset request number threshold is updated according to the limited number.

[0190] The present embodiment discloses a vulnerability scanning method, which includes: generating a target account username upon receiving a vulnerability scanning request; sending an identity authentication request to a cloud server based on the target account username, so that the cloud server feeds back an identity authentication response; determining the category of the identity authentication response and the corresponding vulnerability scanning strategy; executing the vulnerability scanning strategy to perform a vulnerability scan and obtain a vulnerability scanning result. The present embodiment generates a target account username by simulation, and sends an identity authentication request to a cloud server according to the target account username to start a virtual identity authentication. Finally, a vulnerability scanning strategy of a corresponding category is determined according to the category of the identity authentication response fed back by the cloud server, and then an automated vulnerability scan is implemented according to the vulnerability scanning strategy, thereby improving the accuracy of identity authentication, avoiding the technical problem that the automated vulnerability scanning mechanism for website identity authentication in the prior art has defects, resulting in security risks for the website, and can simulate various verification scenarios to improve scanning efficiency.

[0191] It should be understood that the above is only an example and does not constitute any limitation on the technical solution of the present invention. In specific applications, technicians in this field can make settings as needed, and the present invention does not limit this.

[0192] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of the present invention. In practical applications, technicians in this field can select part or all of them according to actual needs to achieve the purpose of the present embodiment, and no limitation is made here.

[0193] In addition, for technical details not fully described in this embodiment, reference can be made to the vulnerability scanning method provided in any embodiment of the present invention, and will not be repeated here.

[0194] In addition, 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 system 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 system. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or system including the element.

[0195] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0196] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory (ROM) / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0197] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

[0198] The present invention discloses A1, a vulnerability scanning method, the vulnerability scanning method comprising:

[0199] When receiving a vulnerability scanning request, generate the target account username;

[0200] Sending an identity authentication request to a cloud server based on the target account username, so that the cloud server feeds back an identity authentication response;

[0201] Determining a category of the identity authentication response and a corresponding vulnerability scanning strategy;

[0202] Execute the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results.

[0203] A2. The vulnerability scanning method as described in A1, wherein executing the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results comprises:

[0204] When the category of the identity authentication response is verification code information, determining the verification code category of the verification code information;

[0205] When the verification code category is a first type of verification code, performing verification code blasting on the verification code information to obtain a blasting result;

[0206] Generate vulnerability scanning results according to the blasting results.

[0207] A3. The vulnerability scanning method as described in A2, wherein the verification code information is subjected to verification code blasting to obtain a blasting result, including:

[0208] Get the number information of the first type of verification code input box;

[0209] Generate a first type of verification code by enumeration according to the quantity information;

[0210] Fill the generated first type of verification code into the first type of verification code input box to send an account update request to the cloud server, wherein the account update request includes: at least one of an account registration request, a password reset request, and an account login request;

[0211] receiving feedback information from the cloud server based on the account update request;

[0212] The blasting result is determined according to the feedback information.

[0213] A4. The vulnerability scanning method as described in A3, wherein determining the blasting result according to the feedback information comprises:

[0214] When the feedback result is that the account update fails, return to the step of generating the first type of verification code by enumeration according to the quantity information until the account update is successful and / or the enumeration duration is greater than or equal to the preset first duration.

[0215] A5. The vulnerability scanning method as described in A2, wherein the verification code information is subjected to verification code blasting to obtain a blasting result, further comprising:

[0216] Reading the first type of verification code information or verification link in the identity verification response through a preset communication interface;

[0217] Performing defect detection on the first type of verification code information;

[0218] Performing controllability detection on the verification link;

[0219] Generate blasting results based on the detection results.

[0220] A6. The vulnerability scanning method as described in A5, wherein the defect detection on the first type of verification code comprises:

[0221] Detecting whether the first type of verification code is the same as a historical verification code within a preset number of times; and / or

[0222] Detect whether the first type of verification code is in a binding state.

[0223] A7. The vulnerability scanning method as described in A1, wherein executing the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results further comprises:

[0224] When the verification code category is a second-category verification code, performing image recognition on the second-category verification code by using a preset image recognition model;

[0225] A vulnerability scan is performed based on the image recognition result to obtain the vulnerability scan result.

[0226] A8. The vulnerability scanning method as described in A7, wherein the image recognition of the second type of verification code is performed by using a preset image recognition model, comprising:

[0227] Determining the verification type of the second type of verification code;

[0228] Determining an image verification strategy according to the verification type of the second type of verification code;

[0229] The second type of verification code is subjected to image verification based on the image verification strategy, and the image verification includes: position detection or trigger detection.

[0230] A9. The vulnerability scanning method as described in A1, wherein generating a target account username comprises:

[0231] Receive account information or dictionary information input by the user;

[0232] determining target format information according to at least one of the account information and / or the dictionary information;

[0233] A target account username is generated according to the target format information.

[0234] A10. The vulnerability scanning method as described in A9, wherein the target format information includes: character category, character quantity, and restriction information;

[0235] The determining the target format information according to at least one of the account information and / or the dictionary information includes:

[0236] Performing regular expression recognition on the account information to obtain character categories, character quantities, and restriction information corresponding to the account information; and / or

[0237] Reading the character category, character quantity and restriction information stored in the dictionary information;

[0238] Accordingly, generating a target account username according to the target format information includes:

[0239] A target account username is generated according to the character category, the number of characters, and the restriction information.

[0240] A11. The vulnerability scanning method as described in any one of A1 to A10, wherein the vulnerability scanning strategy is executed to perform vulnerability scanning, and after obtaining the vulnerability scanning result, the method further comprises:

[0241] Get the number of identity authentication requests within the preset second time period;

[0242] When the number of identity authentication requests is less than a preset request number threshold, matching the vulnerability scan result with historical vulnerability scan results within the preset request number threshold;

[0243] When the match fails, the number of identity authentication requests is recorded as the limit number, and the preset request number threshold is updated according to the limit number.

[0244] The present invention also discloses B12, a vulnerability scanning device, the vulnerability scanning device comprising:

[0245] A generation module, used to generate a target account username when receiving a vulnerability scanning request;

[0246] A request module, used to send an identity authentication request to a cloud server based on the target account username, so that the cloud server feeds back an identity authentication response;

[0247] A formulation module for determining the category of the authentication response and the corresponding vulnerability scanning strategy;

[0248] The scanning module is used to execute the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results.

[0249] B13, the vulnerability scanning device as described in B12, wherein the scanning module is further used to determine the verification code category of the verification code information when the category of the identity authentication response is verification code information;

[0250] When the verification code category is a first type of verification code, performing verification code blasting on the verification code information to obtain a blasting result;

[0251] Generate vulnerability scanning results according to the blasting results.

[0252] B14, the vulnerability scanning device as described in B13, wherein the scanning module is further used to obtain the quantity information of the first type of verification code input box;

[0253] Generate a first type of verification code by enumeration according to the quantity information;

[0254] Fill the generated first type of verification code into the first type of verification code input box to send an account update request to the cloud server, wherein the account update request includes: at least one of an account registration request, a password reset request, and an account login request;

[0255] receiving feedback information from the cloud server based on the account update request;

[0256] The blasting result is determined according to the feedback information.

[0257] B15. In the vulnerability scanning device as described in B14, the scanning module is further used to return to the step of generating the first type of verification code by enumerating according to the quantity information when the feedback result is that the account update fails, until the account update is successful and / or the enumeration duration is greater than or equal to the preset first duration.

[0258] B16, the vulnerability scanning device as described in B13, wherein the scanning module is further used to read the first type of verification code information or verification link in the identity authentication response through a preset communication interface;

[0259] Performing defect detection on the first type of verification code information;

[0260] Performing controllability detection on the verification link;

[0261] Generate blasting results based on the detection results.

[0262] B17. The vulnerability scanning device as described in B16, wherein the scanning module is further used to detect whether the first type of verification code is the same as a historical verification code within a preset number of times; and / or

[0263] Detect whether the first type of verification code is in a binding state.

[0264] B18, the vulnerability scanning device as described in B12, wherein the scanning module is further used to perform image recognition on the second type of verification code by using a preset image recognition model when the verification code category is a second type of verification code;

[0265] A vulnerability scan is performed based on the image recognition result to obtain the vulnerability scan result.

[0266] The present invention also discloses C19, a vulnerability scanning device, which includes: a memory, a processor, and a vulnerability scanning program stored in the memory and executable on the processor, wherein the vulnerability scanning program is configured to implement the vulnerability scanning method described above.

[0267] The present invention also discloses D20, a storage medium, on which a vulnerability scanning program is stored. When the vulnerability scanning program is executed by a processor, the vulnerability scanning method as described above is implemented.

Claims

1. A vulnerability scanning method, characterized in that: The vulnerability scanning method comprises: When receiving a vulnerability scanning request, generate the target account username; Sending an identity authentication request to a cloud server based on the target account username, so that the cloud server feeds back an identity authentication response; Determining a category of the identity authentication response and a corresponding vulnerability scanning strategy; Execute the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results.

2. The vulnerability scanning method according to claim 1, characterized in that: The executing the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results includes: When the category of the identity authentication response is verification code information, determining the verification code category of the verification code information; When the verification code category is a first type of verification code, performing verification code blasting on the verification code information to obtain a blasting result; Generate vulnerability scanning results according to the blasting results.

3. The vulnerability scanning method according to claim 2, characterized in that: The step of performing verification code blasting on the verification code information to obtain a blasting result includes: Get the number information of the first type of verification code input box; Generate a first type of verification code by enumeration according to the quantity information; Fill the generated first type of verification code into the first type of verification code input box to send an account update request to the cloud server, wherein the account update request includes: at least one of an account registration request, a password reset request, and an account login request; receiving feedback information from the cloud server based on the account update request; The blasting result is determined according to the feedback information.

4. The vulnerability scanning method according to claim 3, characterized in that: Determining the blasting result according to the feedback information includes: When the feedback result is that the account update fails, return to the step of generating the first type of verification code by enumeration according to the quantity information until the account update is successful and / or the enumeration duration is greater than or equal to the preset first duration.

5. The vulnerability scanning method according to claim 2, characterized in that: The verification code information is subjected to verification code blasting to obtain a blasting result, further comprising: Reading the first type of verification code information or verification link in the identity verification response through a preset communication interface; Performing defect detection on the first type of verification code information; Performing controllability detection on the verification link; Generate blasting results based on the detection results.

6. The vulnerability scanning method according to claim 5, characterized in that: The performing defect detection on the first type of verification code includes: Detecting whether the first type of verification code is the same as a historical verification code within a preset number of times; and / or Detect whether the first type of verification code is in a binding state.

7. The vulnerability scanning method according to claim 1, characterized in that: The executing the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results also includes: When the verification code category is a second-category verification code, performing image recognition on the second-category verification code by using a preset image recognition model; A vulnerability scan is performed based on the image recognition result to obtain the vulnerability scan result.

8. A vulnerability scanning device, characterized in that: The vulnerability scanning device comprises: A generation module, used to generate a target account username when receiving a vulnerability scanning request; A request module, configured to send an identity authentication request to a cloud server based on the target account username, so that the cloud server feeds back an identity authentication response; A formulation module for determining the category of the authentication response and the corresponding vulnerability scanning strategy; The scanning module is used to execute the vulnerability scanning strategy to perform vulnerability scanning and obtain vulnerability scanning results.

9. A vulnerability scanning device, characterized in that: The vulnerability scanning device comprises: a memory, a processor, and a vulnerability scanning program stored in the memory and executable on the processor, wherein the vulnerability scanning program is configured to implement the vulnerability scanning method according to any one of claims 1 to 7.

10. A storage medium, characterized in that: The storage medium stores a vulnerability scanning program, and when the vulnerability scanning program is executed by the processor, the vulnerability scanning method according to any one of claims 1 to 7 is implemented.

Images