System, method and program for checking vulnerability of website
The system determines website and parameter types using trained models and inspection rules to detect vulnerabilities beyond invalid inputs, improving the accuracy and comprehensiveness of vulnerability testing.
Patent Information
- Application Number
- JP2023137988
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-08-28
- Publication Date
- 2024-11-20
- Estimated Expiration
- 2043-05-08
AI Technical Summary
Conventional vulnerability detection methods fail to identify defects caused by valid input values, such as changing a product price from 1000 yen to 100 yen, which are not detected as invalid inputs.
A system and method that determines the type of website, web page, and parameters based on page information to inspect vulnerabilities, using trained models and inspection rules to identify and assess vulnerabilities beyond invalid inputs.
Enables comprehensive vulnerability testing by identifying issues in web pages and parameters, including those caused by valid input changes, enhancing the accuracy and appropriateness of vulnerability inspections.
Smart Images

Figure 2024161871000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a system, method, and program for checking the vulnerability of a website. [Background technology]
[0002] Conventionally, various techniques have been proposed for inspecting vulnerabilities in websites. For example, Patent Document 1 below discloses acquiring communication content between a website and a browser, and analyzing vulnerabilities inherent in the website based on parameters included in the communication content. Such parameter-based vulnerability detection is typically performed by sending a request to which a prepared detection pattern is applied to the parameter, and based on the content of the response to the request. The detection pattern is, for example, "'" (one single quote) in the case of an SQL injection vulnerability, and includes input values constituting a command statement to a database, etc. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2004-310267 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, while the conventional approaches described above make it possible to detect defects caused by invalid input values, they are unable to detect defects when the input values are not invalid. For example, they are unable to detect changes that are not permitted by the specifications (such as changing the price of a product from 1,000 yen to 100 yen on a screen for purchasing a product).
[0005] One of the objects of the embodiments of the present invention is to support the inspection of various vulnerabilities of websites. Other objects of the embodiments of the present invention will become apparent by referring to the entire specification. [Means for solving the problem]
[0006] A system according to one embodiment of the present invention is a system for testing vulnerabilities of a website, comprising one or more computer processors, the one or more computer processors performing the steps of acquiring page information of a webpage contained in the website, determining the type of the website, the webpage, and at least one type of parameters in the webpage based on the page information, and testing the website for vulnerabilities based on the at least one type.
[0007] A method according to one embodiment of the present invention is executed by one or more computers and is a method for testing vulnerabilities of a website, comprising the steps of obtaining page information of a web page contained in the website, determining a type of the website, the web page, and at least one type of parameters in the web page based on the page information, and testing the website for vulnerabilities based on the at least one type.
[0008] A program according to one embodiment of the present invention is a program for checking the vulnerabilities of a website, and causes one or more computers to execute the steps of acquiring page information of a webpage contained in the website, determining the type of the website, the webpage, and at least one type of parameters in the webpage based on the page information, and checking the vulnerability of the website based on the at least one type. Effect of the Invention
[0009] Various embodiments of the present invention support testing of websites for various vulnerabilities. [Brief description of the drawings]
[0010] [Figure 1] 1 is a diagram showing a schematic configuration of a network including a vulnerability testing server 10 according to an embodiment of the present invention. [Diagram 2] 4 is a diagram illustrating an example of information managed by an inspection rule management table 152. [Diagram 3] 4 is a diagram illustrating an example of information managed by an examination management table 154. [Figure 4] 4 is a diagram illustrating an example of information managed by a page information management table 156. [Diagram 5] 4 is a flowchart illustrating a process executed by the vulnerability check server 10 when checking for vulnerabilities in a website. [Figure 6] FIG. 4 is a diagram illustrating a target site setting screen 50. [Figure 7] 6 is a flowchart illustrating a process executed by the vulnerability check server 10 when setting a screen transition. [Figure 8] 4 is a flowchart illustrating a process executed by the server 10 when performing an inspection based on an inspection rule. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each drawing, the same reference numerals may be used to denote the same or similar components.
[0012] FIG. 1 is a diagram showing a schematic configuration of a network including a vulnerability testing server 10 according to an embodiment of the present invention. As shown in the figure, the server 10 is communicatively connected to a user terminal 30 via a communication network 20 such as the Internet. Although only one user terminal 30 is shown in FIG. 1, the server 10 is communicatively connected to a plurality of user terminals 30. The vulnerability testing server 10 provides a vulnerability testing service to a user who operates the user terminal 30, which tests for vulnerabilities (information security flaws) of a website 22 or the like designated by the user. The vulnerability testing server 10 is an example of a device that implements all or a part of the system of the present invention.
[0013] First, a description will be given of the hardware configuration of the vulnerability checking server 10. The vulnerability checking server 10 is configured as a general computer, and as shown in Fig. 1, includes a computer processor 11, a main memory 12, an input / output I / F 13, a communication I / F 14, and a storage (storage device) 15, and these components are electrically connected via a bus or the like (not shown).
[0014] The computer processor 11 is configured as a CPU, a GPU, or the like, and loads various programs stored in a storage 15 or the like into a main memory 12, and executes various instructions included in the programs. The main memory 12 is configured, for example, by a DRAM or the like.
[0015] The input / output I / F 13 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 13 includes, for example, an information input device such as a keyboard, a pointing device (e.g., a mouse, a touch panel, etc.), an audio input device such as a microphone, and an image input device such as a camera. The input / output I / F 13 also includes an image output device such as a display, and an audio output device such as a speaker.
[0016] The communication I / F 14 is implemented as hardware such as a network adapter, various communication software, or a combination of these, and is configured to realize wired or wireless communication via a communication network 20 or the like.
[0017] The storage 15 is configured, for example, by a magnetic disk or a flash memory. The storage 15 stores various programs including an operating system, various data, and the like. For example, as shown in Fig. 1, the storage 15 has an inspection rule management table 152 that manages information related to inspection rules used in vulnerability inspection, an inspection management table 154 that manages information related to inspection, and a page information management table 156 that manages page information related to web pages included in a website to be inspected. Some of these tables may be integrated into one table, or may be divided into multiple tables.
[0018] Furthermore, for example, the storage 15 stores a server-side program 40 according to an embodiment of the present invention. The program 40 is a program for causing the server 10 to function as all or part of a system for providing a vulnerability testing service. At least a part of the server-side program 40 can be configured to be executed on the user terminal 30 side via a terminal-side program 42, which will be described later.
[0019] In this embodiment, the vulnerability testing server 10 may be configured using a plurality of computers each having the above-mentioned hardware configuration. For example, the server 10 is configured by a plurality of server devices.
[0020] The vulnerability testing server 10 thus configured can be configured to have the functions of a web server and an application server, and executes various processes in response to requests from the user terminal 30, and transmits screen data (e.g., HTML data) and control data according to the results of the processes to the user terminal 30. The user terminal 30 outputs a web page or other screen based on the received data.
[0021] Next, a description will be given of the hardware configuration of the user terminal 30. The user terminal 30 is configured as a general computer, and as shown in Fig. 1, includes a computer processor 31, a main memory 32, an input / output I / F 33, a communication I / F 34, and a storage (storage device) 35, and these components are electrically connected via a bus or the like (not shown).
[0022] The computer processor 31 is configured as a CPU, a GPU, or the like, and loads various programs stored in a storage 35 or the like into a main memory 32 and executes various instructions included in the programs. The main memory 32 is configured, for example, by a DRAM or the like.
[0023] The input / output I / F 33 includes various input / output devices for exchanging information with an operator, etc. The input / output I / F 33 includes, for example, an information input device such as a keyboard or a pointing device (e.g., a mouse, a touch panel, etc.), an audio input device such as a microphone, and an image input device such as a camera. The input / output I / F 33 also includes an image output device such as a display, and an audio output device such as a speaker.
[0024] The communication I / F 34 is implemented as hardware such as a network adapter, various communication software, or a combination of these, and is configured to realize wired or wireless communication via the communication network 20 or the like.
[0025] The storage 35 is configured, for example, by a magnetic disk or a flash memory. The storage 35 stores various programs including an operating system, various data, and the like. The programs stored in the storage 35 can be downloaded from an application market or the like and installed. The storage 35 also stores the above-mentioned terminal-side program 42. The program 42 is configured as a web browser or other application (for example, a terminal-side application for the vulnerability testing service of this embodiment, etc.) and can be configured to execute at least a part of the server-side program 40 as described above.
[0026] In this embodiment, the user terminal 30 may be configured as a smartphone, a tablet terminal, a personal computer, or the like.
[0027] A user operating a user terminal 30 configured in this manner can use the vulnerability testing service provided by the server 10 by communicating with the server 10 via a terminal-side program 42 installed in storage 35 or the like.
[0028] Next, a description will be given of the functions of the vulnerability testing server 10 configured as above. The computer processor 11 of the server 10 is configured to function as a management function control unit 112, a page information acquisition unit 114, a page information analysis unit 116, and a testing control unit 118 by executing instructions included in a program (e.g., at least a part of the server-side program 40) loaded into the main memory 12, as shown in FIG.
[0029] The management function control unit 112 is configured to execute various processes related to the control of the management function of the vulnerability testing service. For example, the management function control unit 112 transmits screen data and control data of various screens related to the management function to the user terminal 30, executes various processes in response to an operation input by a user via the screen output on the user terminal 30, and transmits screen data and control data according to the results of the processes to the user terminal 30. The management functions controlled by the management function control unit 112 include, for example, login processing (user authentication), billing control, and management of user accounts.
[0030] The page information acquisition unit 114 is configured to acquire page information on each web page included in the website 22 to be inspected. For example, the page information acquisition unit 114 crawls through these multiple web pages to acquire the page information. This crawling is performed automatically by the page information acquisition unit 114, or is performed accompanied by a manual operation by the user of the user terminal 30. The acquired page information is managed, for example, in a page information management table 154. The page information includes various information on the web page, such as HTML data and names and values of request parameters.
[0031] The page information analysis unit 116 is configured to execute various processes related to the analysis of page information. For example, the page information analysis unit 116 is configured to determine at least one type (e.g., meaning, use, or function) of the website 22, each webpage, and parameters in the webpage based on the page information of each webpage. Such a type is determined, for example, via a rule base or a machine learning model (e.g., stored in the storage 15, etc.). For example, a trained model generated by machine learning is configured to output information for determining the above-mentioned type when page information is input. The trained model includes a large-scale language model.
[0032] The inspection control unit 118 is configured to execute various processes for controlling the inspection of vulnerabilities of the website 22. For example, the inspection control unit 118 is configured to inspect the vulnerability of the website 22 based on the type of the website 22, each web page, and at least one type of parameters in the web page. For example, the inspection control unit 118 inspects the vulnerability of the website 22 according to an inspection rule corresponding to such a type (for example, an HTTP request to which an inspection pattern set as an inspection rule is applied is sent to the website 22, and vulnerability of the corresponding inspection item is determined based on the contents of the HTTP response received from the website 22). For example, the inspection control unit 118 inspects the vulnerability of the website 22 according to an inspection rule corresponding to a combination of the type of the website 22 and the type of each web page.
[0033] In this way, the vulnerability testing server 10 in this embodiment determines the type of the website 22, each web page, and / or parameters in each web page based on the page information of each of the multiple web pages included in the website 22, and tests the vulnerability of the website 22 based on these types, making it possible to perform appropriate testing according to the meaning, use, function, etc. of the website, web page, or parameters, in addition to defects caused by simple invalid input values. In other words, the server 10 supports testing of various vulnerabilities of websites.
[0034] The inspection control unit 118 may also be configured to identify a specific type of webpage from among multiple webpages included in the website 22, and inspect the website 22 for vulnerabilities through a specific operation on the identified webpage. The specific operation includes various operations for inspecting vulnerabilities, and typically involves sending an HTTP request. This configuration enables inspection of vulnerabilities through the specific operation on a specific type of webpage.
[0035] In this case, the inspection control unit 118 can be configured to identify an inspection rule corresponding to the type of the website 22 from among a plurality of predetermined inspection rules, and to identify a predetermined type of web page corresponding to the identified inspection rule from a plurality of web pages included in the website 22. The type of website 22 corresponding to each inspection rule is managed, for example, in the inspection rule management table 152. This configuration enables vulnerability inspection of a type of web page corresponding to an inspection rule based on the type of the website 22 via a predetermined operation.
[0036] In this embodiment, the inspection control unit 118 may be configured to identify a predetermined type of parameter from among multiple parameters in each web page, and inspect the website 22 for vulnerabilities through a predetermined operation on the web page that involves changing the value of the identified parameter. Such a configuration enables inspection of vulnerabilities through a predetermined operation that involves changing the value of a predetermined type of parameter.
[0037] In this case, the inspection control unit 118 may be configured to inspect the vulnerability of the website 22 based on the page information of a destination webpage to which the webpage transitions in response to a predetermined operation on the webpage. For example, the inspection control unit 118 is configured to determine the operation result of the predetermined operation (e.g., whether or not the operation ended normally) based on the page information of the destination webpage, and to determine the vulnerability related to the predetermined operation based on the determination result. Such a configuration enables the inspection of vulnerabilities based on the page information of the destination webpage in response to a predetermined operation.
[0038] Furthermore, the inspection control unit 118 may be configured to input page information of each webpage into a predetermined trained model, and obtain a vulnerability score indicating the vulnerability of the website 22 output from the predetermined trained model. The trained model is generated, for example, through machine learning using a large amount of training data, and is configured to output a vulnerability score of the corresponding website 22 when page information is input. The trained model is stored, for example, in the storage 15. Such a configuration enables the vulnerability score to be obtained using the page information and the trained model.
[0039] In this case, the inspection control unit 118 may be configured to set the acquired vulnerability score as the inspection result when the vulnerability score is less than the threshold, and to inspect the vulnerability of the website 22 via a predetermined operation on the web page when the vulnerability score is equal to or greater than the threshold. This configuration makes it possible to avoid inspection via a predetermined operation on the web page when the vulnerability score is small (the severity of the vulnerability is low).
[0040] Next, a specific example of one aspect of the vulnerability testing server 10 of this embodiment having such functions will be described. First, information managed by each table in this example will be described. FIG. 2 illustrates information managed by the testing rule management table 152 in this example. The testing rule management table 152 in this example manages information related to testing rules applied to vulnerability testing, and as shown in the figure, manages information such as a "site type" indicating the type of website to which this testing rule is applied, a "page function" indicating the function (type) of the web page to which this testing rule is applied, a "parameter type" indicating the type of parameter to which this testing rule is applied, "test method information" which is information related to the testing method, and "result determination method information" which is information related to the method of determining the test result, in association with an "test rule ID" which identifies an individual testing rule. These pieces of information are set in advance by the provider of the vulnerability testing service.
[0041] 3 illustrates information managed by the inspection management table 154 in this example. The inspection management table 154 in this example manages information related to inspection cases, and as shown in the figure, manages information such as a "top screen URL" which is the URL of the top screen (top page) that is the starting point of the inspection of the website to be inspected, and a "inspection execution date and time" which is the date and time the inspection was performed, in association with an "inspection ID" which identifies an individual inspection (case).
[0042] FIG. 4 illustrates information managed by the page information management table 156 in this example. The page information management table 156 in this example manages information on each screen included in the screen transition during the inspection among multiple screens (web pages) in the website to be inspected, and as shown in the figure, manages information such as a "screen URL" which is the URL of the screen, "HTML data" of the screen, "parameter information" which is information (name and value) of the request parameter transmitted on the screen, "transition source information" which is information on the transition source of the screen in the screen transition (screen ID of the transition source screen, element ID of the transition source screen element, etc.), and "inspection result information" which is information on the inspection result of the screen, in association with a combination of an "inspection ID" which identifies an individual inspection and a "screen ID" which identifies an individual screen in the website to be inspected. In this example, the screen transition during the inspection is automatically set by the server 10, which will be described in detail later.
[0043] The information managed by each table in this example has been described above. Next, the process executed by the vulnerability check server 10 and the screens output on the user terminal 30 in this example will be described.
[0044] 5 is a flowchart illustrating the process executed by the vulnerability check server 10 when checking for vulnerability of a website in this example. As shown in the figure, the server 10 first accepts settings of a website to be checked for vulnerability (step S100). The settings are accepted via a screen displayed on the user terminal 30.
[0045] 6 illustrates a target site setting screen 50 for accepting settings of a website to be inspected, which is output on the user terminal 30. As illustrated, the screen 50 has a URL input area 52 for inputting the URL of the top screen (top page) of the website to be inspected, a login ID input area 54 for inputting a login ID used to log in to the website, a password input area 56 for inputting a password used to log in to the website, and a continue button 58 with the text "Start patrol and inspection" added. Thus, in this example, the URL of the top screen, the login ID, and the password are accepted as setting information of the website to be inspected.
[0046] The continue button 58 is an object for instructing browsing (setting screen transitions) and inspection of the website to be inspected. Returning to the flowchart of Fig. 5, when the continue button 58 is selected, the server 10 next browses the website to be inspected and sets screen transitions for inspection (step S110).
[0047] 7 is a flow chart illustrating a process executed by the server 10 when setting a screen transition. As shown in the figure, the server 10 first accesses the top screen of the website to be inspected and adds the top screen to the screen transition (step S200). Specifically, a web browser is started and access is made to the top screen specified by the URL input via the target site setting screen 50. Also, information about the top screen is registered in the page information management table 156, and specifically, an inspection ID, a screen ID, a screen URL, HTML data, and parameter information are set.
[0048] Next, the server 10 identifies a plurality of transition target elements included in the top screen (step S210). Specifically, screen components (buttons, images, text, etc.) to which links or scripts are set are identified as transition target elements.
[0049] Next, the server 10 clicks on the identified element (step S220), and if the screen to be transitioned to according to the click is a screen to be added to the screen transition (YES in step S230), adds the transition to the screen to the screen transition (step S240). Specifically, information on the screen to be transitioned to is registered in the page information management table 156, that is, the examination ID, screen ID, screen URL, HTML data, parameter information, and transition source information are set. Note that the transition source information includes a screen ID for identifying the top screen, which is the transition source, and an element ID for identifying the clicked element.
[0050] Also, in this example, when clicking on a transition target element, if there is a required input field, the input values prepared in advance (including the combination of login ID and password entered via the target site setting screen 50) are automatically set.
[0051] On the other hand, if the screen to which the user transitions in response to the click is not a screen to be added to the screen transition (NO in step S230), the transition to that screen is not added to the screen transition.
[0052] Here, in this example, the following two screens are determined as screens that cannot be added to the screen transition. (1) Screen of a site outside the site being inspected (2) A screen that overlaps with a screen already included in the screen transition
[0053] Regarding (2), in this example, the overlap between two screens is determined based on the similarity between these screens, and specifically, if the similarity is equal to or greater than a threshold, the two screens are determined to overlap. The similarity can be calculated using various criteria, for example, based on a comparison of the screen (page) contents, URL, and URL parameters.
[0054] Then, when it is determined whether or not a transition to a transition destination screen in response to a click is added to the screen transition for all of the transition target elements included in the top screen (NO in step S260), the server 10 then identifies the transition target elements included in each screen added to the screen transition (step S280) in the same manner as for the top screen, and determines whether or not a transition to the screen transition in response to a click of each element is added to the screen transition (steps S220 to S260). This process is repeated until no new screens are added to the screen transition (NO in step S270).
[0055] Returning to the flowchart of Fig. 5, once the screen transitions are set in this way, the server 10 then executes vulnerability testing according to the set screen transitions (step S120). Specifically, a web browser is started, and each screen included in the screen transition is visited in order according to the information managed in the page information management table 156, and testing is performed for predetermined vulnerability testing items. The vulnerability testing items include, for example, items defined in OWASP Top 10. The testing results are registered in the testing result information in the page information management table 156.
[0056] In this example, for the above-mentioned predetermined inspection items, inspections are performed based on inspection rules according to the nature of the inspection. The inspection rules are managed in the inspection rule management table 152, and include, for example, the following inspection rules. (Rule 1) Site type: E-commerce site Page function: Product purchase screen Parameter type: Product price Inspection method: Numerical change (0.5 times) Result determination method: Price information on the completion screen (Rule 2) Site type: SNS site Page function: Private message screen Parameter type: Message ID Inspection method: Change in value (-1) Result determination method: Message information of the user on the same screen (Rule 3) Site type: SNS site Page function: Post content editing screen Parameter type: Post ID Inspection method: Change in value (-1) Result determination method: Post information on the post content viewing screen (Rule 4) Site Type: All Page function: Password change screen Parameter type: Password value Inspection method: Using vulnerability scores from a trained model (Rule 5) Site Type: All Page function: Data deletion screen Parameter type: Data ID Inspection method: Using vulnerability scores from a trained model
[0057] FIG. 8 is a flowchart illustrating a process executed by the server 10 when performing an inspection based on the inspection rule. As shown in the figure, the server 10 first determines the site type of the target website (step S300). In this example, the site type is determined using a trained model for determining the site type of the website. The trained model is generated by machine learning using a large amount of training data, and is configured to output a score indicating the probability of each of a plurality of predetermined site types (e.g., an EC site, an SNS site, etc.) when page information (HTML data and parameter information) of each of a plurality of web pages included in the website is input. The server 10 inputs page information (HTML data and parameter information) of each screen included in the screen transition set in the target website (inspection) into the trained model, and determines that the site type with the highest score output from the trained model is the site type of the target website. The page information of each screen is managed in a page information management table 156.
[0058] Next, if the determined site type matches the site type set in the target inspection rule (the target inspection rule is identified from among multiple inspection rules in a predetermined order) (YES in step S305), the server 10 identifies a screen corresponding to the function set in the inspection rule from among multiple screens included in the screen transition (step S310). On the other hand, if the determined site type does not match the site type set in the inspection rule (NO in step S305), the website is not subject to the inspection rule, so inspection based on the inspection rule is skipped.
[0059] In this example, similarly to the above-mentioned site type, a trained model for determining the function of a screen is used to determine the function. The trained model is generated by machine learning using a large amount of training data, and is configured to output a score indicating the probability of each of a plurality of functions (e.g., a product purchase screen, a private message screen, a post content editing screen, a password change screen, and a data deletion screen) when page information of each screen is input. The server 10 determines that the function with the highest score output from the trained model among the plurality of functions is the function of each screen. Then, among the plurality of screens, a screen of the function set in the inspection rule is identified.
[0060] If a screen corresponding to the target inspection rule (a screen for a function set in the inspection rule) exists (YES in step S315), the server 10 identifies a predetermined type of parameter included in the inspection rule from among a plurality of parameters on the screen (step S320). On the other hand, if a screen corresponding to the inspection rule does not exist (NO in step S315), the website is not subject to the inspection rule, and inspection based on the inspection rule is skipped.
[0061] In this example, a trained model for determining parameters of a predetermined type (e.g., product price, message ID, post ID, password value, and data ID, etc.) is used to identify the parameters. The trained model is generated by machine learning using a large amount of training data, and is configured to output a score indicating the probability that the parameter with the input name is a parameter of the predetermined type when page information of each screen and the name of the parameter included in the screen (e.g., item_price, message_id, post_id, password, or data_id, etc.) are input. The server 10 determines that a parameter of a predetermined type is a parameter of a predetermined type among a plurality of parameters included in each screen, the parameter having a score output from the trained model that is equal to or greater than a threshold value.
[0062] Then, when a parameter of a predetermined type corresponding to the inspection rule exists (YES in step S325), the server 10 acquires a vulnerability score via the trained model (step S330). The trained model is generated by machine learning using a large amount of training data, and is configured to output a vulnerability score of each screen when page information of the screen is input.
[0063] On the other hand, if the parameter of the predetermined type does not exist (NO in step S325), the website is not subject to the inspection rule, and therefore the inspection based on the inspection rule is skipped.
[0064] After acquiring the vulnerability score via the trained model, the server 10 records the vulnerability score as an inspection result (step S360) if the inspection method set in the inspection rule is not a change in parameter value (NO in step S335), or if the inspection method is a change in parameter value (YES in step S335) but the acquired vulnerability score value is less than the threshold value (NO in step S340). Specifically, the vulnerability score is registered for the inspection result information of the corresponding screen in the page information management table 156. Note that, among rules 1 to 5 in the above-mentioned example of the inspection rule, rules 4 and 5 apply when the inspection method set is not a change in parameter value (that is, in this example, "when the inspection method is not a change in parameter value" can be said to be "when the inspection method is the use of a vulnerability score by a trained model").
[0065] On the other hand, when the inspection method set in the inspection rule is a change in parameter value (YES in step S335) and the acquired vulnerability score value is equal to or greater than the threshold value (YES in step S340), the server 10 changes the parameter value and transmits a request (step S345). Specifically, the change in the parameter value is set in the inspection method information of the inspection rule. For example, in the rule 1 in the above example, when the parameter of the predetermined type is "product price", a numerical change of "0.5 times" is set. In this case, for example, a request in which the product price of "1000 yen" in the page information of the corresponding screen is changed to "500 yen" is transmitted. The transmission of the request can be said to be the execution of a product purchase process. Also, for example, in the rule 2 in the above example, when the parameter of the predetermined type is "message ID", a numerical change of "-1" is set. In this case, for example, a request in which the message ID of "12345" in the page information of the corresponding screen is changed to "12344" is transmitted. The transmission of the request can be said to be the execution of a message transmission process. Also, for example, in rule 3 in the above example, when the parameter of the predetermined type is "post ID", a numerical change of "-1" is set. In this case, for example, a request is sent in which the post ID of "987" in the page information of the corresponding screen is changed to "986". The sending of this request can be said to be the execution of a post content editing process.
[0066] Next, the server 10 judges the vulnerability based on the response from the website and registers the judgment result (step S350). The judgment of the vulnerability is performed based on the result judgment method information in the inspection rule. For example, in the rule 1 in the above example, if normal processing is confirmed with the changed product price in the product purchase completion screen of the transition destination based on the response, it is judged that there is a vulnerability. Also, for example, in the rule 2 in the above example, if normal processing is confirmed with the changed message (message of another user) in the private message screen of the transition destination based on the response, it is judged that there is a vulnerability. Also, for example, in the rule 3 in the above example, if normal processing is confirmed with the changed post (post of another user) in the post content viewing screen of the transition destination based on the response, it is judged that there is a vulnerability. Such a judgment result is registered in the page information management table 156 with respect to the inspection result information of the corresponding screen.
[0067] Thus, in this example, when the inspection method set in the inspection rule is not changing the parameter value (when the inspection method is using the vulnerability score by the trained model), the vulnerability score acquired via the trained model is used as the inspection result. Compared to an inspection in which a parameter value is changed and a request is sent, acquiring such a vulnerability score can reduce the impact on the production environment and other development environments, and shorten the inspection time. For example, for an inspection rule that is expected to have an impact on the production environment, an inspection method that does not change the parameter value is set in advance.
[0068] For example, in the above-mentioned rule 4, if an inspection is performed on the password change screen where a request is sent after setting "' or 1=1 --" or the like for the password parameter value, (SQL Injection inspection), it is expected that other users' passwords will be changed. Also, for example, in the above-mentioned rule 5, if an inspection is performed on the data deletion screen where a request is sent after changing the data ID parameter value (for example, -1), it is expected that data used for purposes other than testing, or actual data of other users, will be deleted.
[0069] In this example, even if the inspection method set in the inspection rule is to change the parameter value, if the vulnerability score obtained through the trained model is less than the threshold, the vulnerability score is used as the inspection result. As a result, it is possible to limit the implementation of an inspection in which a request is sent by changing the parameter value to cases in which the severity of the vulnerability is assumed to be high (the score is relatively large).
[0070] After recording the vulnerability score (step S360) or registering the vulnerability determination result (step S350), if there are unprocessed inspection rules (NO in step S355), the server 10 returns to step S305 and performs an inspection based on the site type, screen function, and parameter type for the next inspection rule. This inspection is repeated until the last inspection rule is reached (YES in step S355).
[0071] In the above example, the inspection rule may be set in natural language (for example, a sentence such as "On the product purchase screen of an EC site, a request parameter including the product price is identified, and a request with this value tampered is sent. If the product can be purchased at the tampered price, a vulnerability is reported."). In this case, the inspection rule set in natural language may be analyzed via a large-scale language model (LLM) or the like.
[0072] In the above example, the site type, screen function, and parameter type are determined via a trained model, but these types may also be determined via a large-scale language model (LLM).
[0073] In the above example, the vulnerability score is obtained via a trained model, but it is also possible to use a large-scale language model (LLM) that can output, in addition to the vulnerability score, the basis for calculating the score (such as a constraint condition such as "except in the case of xxx").
[0074] The vulnerability testing server 10 according to the present embodiment described above determines the type of the website 22, each web page, and / or parameters in each web page based on the page information of each of the multiple web pages included in the website 22, and tests the vulnerability of the website 22 based on these types, making it possible to perform appropriate testing according to the meaning, use, function, etc. of the website, web page, or parameters, in addition to defects due to simple invalid input values. In other words, the server 10 supports testing of various vulnerabilities of websites.
[0075] In other embodiments of the present invention, some or all of the functions of the vulnerability testing server 10 in the above-described embodiments may be realized by cooperation between the vulnerability testing server 10 and the user terminal 30, or may be realized by the user terminal 30.
[0076] The processes and procedures described herein may be realized by software, hardware, or any combination thereof, other than those explicitly described. For example, the processes and procedures described herein may be realized by implementing logic corresponding to the processes and procedures in a medium such as an integrated circuit, a volatile memory, a non-volatile memory, or a magnetic disk. In addition, the processes and procedures described herein may be implemented as a computer program corresponding to the processes and procedures, and executed by various computers.
[0077] Although processes and procedures described herein are described as being performed by a single device, software, component, or module, such processes or procedures may be performed by multiple devices, software, components, and / or modules. Also, the software and hardware elements described herein may be realized by combining them into fewer components or breaking them down into more components.
[0078] In this specification, even if a component of the invention is described as either singular or plural, or described without limitation to either singular or plural, the component may be either singular or plural unless the context requires otherwise. [Explanation of symbols]
[0079] 10 Vulnerability testing server 11. Computer Processors 112 Management function control section 114 Page information acquisition unit 116 Page Information Analysis Section 118 Inspection Control Unit 15. Storage 152 Inspection rule management table 154 Inspection Management Table 156 Page Information Management Table 30 User terminal 40 Server-side programs 42 Terminal side program 50 Target site setting screen
Claims
1. 1. A system for testing a website for vulnerability, comprising: one or more computer processors, the one or more computer processors comprising: obtaining page information of a web page included in the website; determining at least one type of the website, the web page, and parameters in the web page based on the page information; and testing the website for vulnerabilities based on the at least one type. system.
2. The determining step determines the at least one type by using a first trained model configured to output information for determining the at least one type when the page information is input. The system of claim 1.
3. The determining step includes determining at least a type of the web page, the inspecting step includes identifying a web page of a predetermined type from among a plurality of web pages included in the website, and inspecting the vulnerability of the website through a predetermined operation on the web page; The system of claim 1.
4. The determining step includes determining at least a type of the website and the web page; The one or more computer processors further execute a step of identifying a first inspection rule corresponding to the type of the website from among a plurality of predetermined inspection rules; the inspecting step includes identifying the web page of the predetermined type corresponding to the first inspection rule from among the plurality of web pages; The system of claim 3.
5. The determining step determines at least a type of the parameter, the step of inspecting includes identifying a first parameter of a predetermined type from among a plurality of parameters in a first web page included in the website, and inspecting the vulnerability of the website through a predetermined operation on the first web page, the predetermined operation involving a change in a value of the first parameter; The system of claim 1.
6. the inspecting step inspects the vulnerability of the website based on the page information of a second web page which transitions in response to the predetermined operation on the first web page; The system of claim 5.
7. The one or more computer processors further perform the steps of inputting the page information into a second trained model and obtaining a score indicative of a vulnerability of the website output from the second trained model. The system of claim 1.
8. the step of inspecting includes, if the score is less than a threshold, taking the score as an inspection result, and, if the score is equal to or greater than the threshold, inspecting the vulnerability of the website through a predetermined operation on the web page. The system of claim 7.
9. 1. A method for testing a website for vulnerability, executed by one or more computers, comprising: obtaining page information of a web page included in the website; determining at least one type of the website, the web page, and parameters in the web page based on the page information; and testing the website for vulnerabilities based on the at least one type. method.
10. A program for testing the vulnerability of a website, comprising: obtaining page information of a web page included in the website; determining at least one type of the website, the web page, and parameters in the web page based on the page information; and testing the website for vulnerabilities based on the at least one type. program.
Citation Information
Patent Citations
Web fingerprint detection method and related equipment
CN114528457A
Inspection equipment for web site
JP2004310267A
Web application inspection device
JP2005250945A
Vulnerability determination system, vulnerability determination method and computer program
JP2019148917A
Systems and methods for a text mining approach for predicting exploitation of vulnerabilities
US20220229912A1
