JP2011138456A - Apparatus, method and program for confirming screen sequence - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reliably and efficiently inspect vulnerability by generating an HTTP request by using parameter information stored in a screen information file. <P>SOLUTION: A screen sequence confirming apparatus 1 includes: a reading part 12 for reading screen information from a storage part 11 that stores the screen information including a URL and parameter information; a transmission part 13 for transmitting an HTTP request on the basis of first read screen information; a receiving part 14 for receiving an HTTP response; an extraction part 15 for extracting a URL for another screen and parameter information from a screen source code included in the HTTP response; a comparison part 16 for comparing the extracted URL and parameter information with a URL and parameter information included in second screen information read after the first screen information; and a rewriting part 17 which when the URLs are not coincident as a result of comparison and all parameter names coincide with each other, rewrites the URL included in the second screen information by the extracted URL. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a screen sequence confirmation device, a screen sequence confirmation method, and a screen sequence confirmation program.

  If the vulnerabilities hidden in Web applications are left unattended, they can be exploited for attacks such as unauthorized access and computer viruses, and there is a risk of serious damage such as system or network down and leakage of personal information. Therefore, it is necessary to detect vulnerabilities early and deal with them appropriately. In general, when developing a Web system, the vulnerability of a Web application is inspected by executing software for inspecting the vulnerability (see, for example, Patent Document 1 below).

  In the software for inspecting vulnerabilities, each screen of the Web application to be inspected is read in the order of display transition, and the URL and parameters included in each screen are stored in advance for each screen. In some cases, the vulnerabilities are inspected in the order of display transitions of the screen stored in the previous work. Some screens cannot be changed to the next screen unless they are entered in the input items provided on the screen. In a system having such a screen, the above-mentioned preliminary work is performed manually one screen at a time. Become.

JP 2007-241906 A

  By the way, when the screen is corrected after the vulnerability is inspected, it is necessary to inspect the vulnerability of the corrected screen again, and accordingly, it is necessary to perform the above-described preliminary work again. In particular, when the preliminary work is performed manually, if the number of input items and the number of correction screens is large, the time required for the preliminary work increases, resulting in a reduction in work efficiency.

  When the screen is corrected, the URL of the correction target screen may be changed. When the URL of the screen is changed, it is necessary to perform the preliminary work again when examining the vulnerability. However, for example, if the person in charge of the screen modification work is different from the person in charge of the vulnerability inspection work, if the changes are not accurately communicated due to a communication error, etc., the vulnerability can be resolved without performing the preliminary work again. It is also possible to inspect. In this case, a vulnerability inspection failure occurs.

  On the other hand, in order to prevent omissions due to contact mistakes etc., it may be possible to perform preliminary work on the entire screen every time vulnerability inspection is performed, but in this case, the time required for the preliminary work increases, Work efficiency will decrease.

  The present invention has been made to solve the above-described problems, and provides a screen sequence confirmation device, a screen sequence confirmation method, and a screen sequence confirmation program capable of reliably and efficiently inspecting a vulnerability. With the goal.

  The screen sequence confirmation device of the present invention includes a storage unit that stores screen information having storage location information that specifies a storage location of an information resource related to a screen, and parameter information that includes a parameter name corresponding to the information resource, and the storage unit A reading unit that reads the screen information stored in the display order of the screens, and the first storage location information and the first parameter included in the first screen information read by the reading unit A transmission unit for transmitting a request for the information resource corresponding to the first storage location information to a server device corresponding to the first storage location information based on the information; and the server in response to the request A receiving unit that receives a response transmitted from the device; and the second storage location information and the second parameter from the information resource included in the response. The second storage location information and the second parameter information extracted by the extraction unit, and the reading unit reads the first screen information next to the first screen information. The comparison unit that compares the third storage location information and the third parameter information included in the second screen information, and the comparison by the comparison unit, the storage location information does not match each other. And when the parameter names included in the parameter information all match, the third storage location information included in the second screen information stored in the storage unit, A rewriting unit that rewrites the second storage location information extracted by the extracting unit.

  The screen sequence confirmation device of the present invention is a storage unit for storing screen information having storage location information for specifying a storage location of information resources related to a screen and parameter information corresponding to the information resources, and is stored in the storage unit. The first storage location included in the first screen information based on the first screen information read by the reading unit and the reading unit that reads the screen information in the display order of the screens. A transmitting unit that transmits a request for the information resource corresponding to the first storage location information to a server device corresponding to the information; and a receiving unit that receives a response transmitted from the server device in response to the request; An extraction unit for extracting event information including a predetermined function from the information resource included in the response; and the first screen read by the reading unit When the predetermined parameter value included in the parameter information of the information is included in the information resource of the response, the predetermined function included in the event information extracted by the extraction unit is analyzed to analyze the predetermined parameter A function analysis unit that acquires the second storage location information corresponding to the value; the second storage location information acquired by the function analysis unit; and the reading unit that follows the first screen information. The comparison unit that compares the third storage location information included in the second screen information read out to the screen information and the comparison by the comparison unit result in the storage location information not matching each other. The second storage location information acquired by the function analysis unit, the third storage location information included in the second screen information stored in the unit Comprising a rewriting unit for rewriting, a.

  The screen sequence confirmation method of the present invention includes a storage step of storing screen information having storage location information for specifying a storage location of an information resource related to a screen and parameter information including a parameter name corresponding to the information resource, and the storage step A reading step of reading the screen information stored in the display order of the screens, the first storage location information and the first parameter information included in the first screen information read in the reading step A transmission step of transmitting a request for the information resource corresponding to the first storage location information to a server device corresponding to the first storage location information, and the server device in response to the request A receiving step for receiving a response transmitted from the information resource, and from the information resource included in the response Extracting the storage location information and the second parameter information, extracting the second storage location information and the second parameter information extracted in the extraction step, and reading the second storage location information and the second parameter information. A comparison step of comparing each of the third storage location information and the third parameter information included in the second screen information read next to the one screen information, and the comparison in the comparison step, When the storage location information is inconsistent and the parameter names included in the parameter information all match, the second screen information stored in the storage step includes the second screen information. Rewrite the third storage location information with the second storage location information extracted by the extraction unit. Including a conversion step, the.

  The screen sequence confirmation program of the present invention causes a computer to execute each step included in the screen sequence confirmation method.

  According to the present invention, vulnerability inspection can be performed reliably and efficiently.

It is a block diagram which illustrates the functional composition of the screen sequence check device in a 1st embodiment. It is a figure which illustrates the data structure of the screen information file in 1st Embodiment. It is a figure which illustrates the screen source code containing a POST method. It is a flowchart (the 1) which shows the process sequence at the time of confirming the screen sequence in 1st Embodiment. It is a flowchart (the 2) which shows the process sequence at the time of confirming the screen sequence in 1st Embodiment. It is a flowchart (the 1) which shows the process sequence at the time of confirming the screen sequence in 2nd Embodiment. It is a flowchart (the 2) which shows the process sequence at the time of confirming the screen sequence in 2nd Embodiment. It is a block diagram which illustrates the functional structure of the screen sequence confirmation apparatus in 3rd Embodiment. It is a figure which illustrates the data structure of the screen information file in 3rd Embodiment. It is a flowchart (the 1) which shows the process sequence at the time of confirming the screen sequence in 3rd Embodiment. It is a flowchart (the 2) which shows the process sequence at the time of confirming the screen sequence in 3rd Embodiment.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments of a screen sequence confirmation device, a screen sequence confirmation method, and a screen sequence confirmation program according to the present invention will be described with reference to the accompanying drawings. The screen sequence confirmation apparatus in each embodiment is for managing a screen information file generated by a prior work of vulnerability inspection performed before executing software for inspecting vulnerability according to the state of the latest Web system. Device. In the preliminary work, each screen of the Web application to be inspected is read in the order of display transition, and screen information files related to URLs and parameters to other screens included in each screen are sequentially stored for each screen. Generate. The software for inspecting vulnerabilities inspects the vulnerabilities in the order of screen display transitions stored in the screen information file.

  [First embodiment]

  With reference to FIG. 1, the functional configuration of the screen sequence confirmation apparatus in the first embodiment will be described. Functionally, the screen sequence confirmation apparatus 1 is functionally, for example, a storage unit 11, a reading unit 12, a transmission unit 13, a reception unit 14, an extraction unit 15, a comparison unit 16, a rewriting unit 17, and an output. Part 18.

  Here, the screen sequence confirmation device 1 physically includes, for example, a CPU (Central Processing Unit), a storage device, an input device, a display device, and a communication device. These elements are connected to each other via a bus. The storage device includes, for example, a ROM (Read Only Memory) and HDD (Hard Disk Drive) that store programs and data processed by the CPU, and a RAM (Random Access Memory) mainly used as various work areas for control processing. ) Etc. are included. For example, the screen information file shown in FIG. 2 is stored in the storage device in the present embodiment. The CPU executes a program stored in the ROM, and processes various data expanded in the RAM in accordance with various commands input from the input device. The CPU displays the processing result on the display device. Thereby, the function of each part in the screen sequence confirmation apparatus 1 described in detail below can be realized.

  The storage unit 11 includes a screen information file that stores screen information generated in the prior work of vulnerability inspection. The data structure of the screen information file will be described with reference to FIG. FIG. 2 is a data configuration diagram of the screen information file. The screen information file stores one record for each screen (hereinafter referred to as “screen information record”). The screen information record includes, for example, a screen name item, a scheme item, a host item, a port item, a path item, a method item, a parameter name item, and a parameter value item as data items. A URL (Uniform Resource Locator; storage location information) that specifies the storage location of the source code (information resource) for displaying the screen is represented by the scheme item, the host item, and the path item. Parameter information is composed of parameter name items and parameter value items.

  The screen name item shown in FIG. 2 stores a screen name for specifying a screen information record. In the scheme item, for example, a scheme such as http or ftp is stored. The host item stores information for specifying the Web server device that provides the content. In the port item, the port number of the Web server device is stored. The path item stores information for specifying a location for storing content in the Web server device. In the method item, information for specifying a method indicating the content of an instruction to the Web server device is stored. The parameter name item stores a parameter name that identifies a parameter set on the screen as data to be transmitted to the Web server device. Examples of parameter names include name, address, telephone number, family structure, bank account, and the like. A parameter value corresponding to the parameter name is stored in the parameter value item.

  The screen information file stores screen information records in the screen display transition order in the Web system provided by the Web server device. For example, the screen information file shown in FIG. 2 indicates that when the Web system is operated, the screen names are changed and displayed in the order of “A”, “B”, and “C”.

  The description method of the screen information file is not limited to the table format shown in FIG. 2, and may be described in another format such as an xml format.

  The reading unit 12 reads the screen information records stored in the screen information file in the screen display order. In the present embodiment, since the screen information records stored in the screen information file are stored in advance in the screen display order, they may be read in order from the top record. On the other hand, when the screen information record is not stored in the display order, for example, a data item for specifying the display order may be provided in the screen information record, and the screen information record may be read in the ascending order of the display order item.

  Based on the screen information of the screen information record, the transmission unit 13 sends an HTTP (HyperText Transfer Protocol) request for requesting a screen source code stored in a location corresponding to the URL of the screen information to the screen information. It transmits to the Web server apparatus corresponding to host.

  The receiving unit 14 receives an HTTP response transmitted from the Web server device in response to the HTTP request.

  The extraction unit 15 extracts URLs and parameter information to other screens from the screen source code included in the HTTP response. Examples of URLs and parameter information to other screens include link destinations and parameter names described in http GET methods and POST methods. This will be specifically described with reference to FIG. FIG. 3 is a source code of a screen including a POST method. The extraction unit 15 extracts “http://www.test.example.com/testpage1.cgi” from the source code shown in FIG. 3 as a URL to another screen, and “name11”, Extract “name12” and “submit”.

  The comparison unit 16 compares the URL and parameter information extracted by the extraction unit 15 with the URL and parameter information included in the screen information read next by the reading unit 12. If there are a plurality of URLs to be extracted by the extraction unit 15, the process of extracting one URL and comparing the extracted one URL with the URL included in the screen information is sequentially repeated. Good.

  Of the screen information stored in the screen information file, the rewrite unit 17 determines that the URLs do not match and the parameter names included in the parameter information all match by the comparison by the comparison unit 16. The URL included in the screen information used for the comparison is rewritten with the URL extracted by the extraction unit 15 used for the comparison.

  The output unit 18 outputs and displays various messages on the display device. As various messages, for example, a message indicating that a URL to another screen could not be extracted, a message indicating that a part of the screen configuration may have been changed, and a new screen may have been added. A message to that effect is applicable. Various messages may be output to a message file instead of being output to the display device.

  Next, the operation of the screen sequence confirmation apparatus in the first embodiment will be described with reference to FIG. 4 and FIG. FIG. 4 and FIG. 5 are flowcharts showing the processing procedure when confirming the screen sequence.

  First, the reading unit 12 reads the first screen information record stored in the screen information file (step S101). For example, in the screen information file shown in FIG. 2, a screen information record having a screen name “A” is read as the first screen information record.

  If the screen information record cannot be read in step S101 (step S102; NO), the process ends. On the other hand, when the screen information record can be read (step S102; YES), the transmission unit 13 is based on the URL and parameter information of the screen information stored in the screen information record read in step S101. An HTTP request for requesting the screen source code stored in the location corresponding to the URL of the screen information is transmitted to the Web server device corresponding to the host of the screen information (step S103).

  Subsequently, the receiving unit 14 receives an HTTP response transmitted from the Web server device in response to the HTTP request (step S104).

  Subsequently, the extraction unit 15 extracts the URL and parameter information for another screen from the screen source code included in the HTTP response (step S105).

  If the URL and parameter information for the other screens cannot be extracted in step S105 (step S106; NO), the output unit 18 sends a message that the URL for the other screens cannot be extracted and the step S101. And outputs the URL of the screen information record read in step S107 to the display device (step S107), and ends the process.

  On the other hand, when the URL and parameter information for another screen can be extracted in step S105 (step S106; YES), the reading unit 12 reads the next screen information record from the screen information file (step S108). For example, in the screen information file shown in FIG. 2, a screen information record having a screen name “B” is read as the next screen information record.

  If the screen information record cannot be read in step S108 (step S109; NO), the process ends. On the other hand, when the screen information record can be read (step S109; YES), the comparison unit 16 adds the URL and parameter information extracted in step S105 and the screen information record read most recently in step S108. The included URL and parameter information are respectively compared (step S110).

  If all the parameter names match as a result of the comparison in step S110 (step S111; YES) and the URLs match (step S112; YES), they are read most recently in step S108. It can be determined that the screen information record has not been changed. Therefore, the process proceeds to step S114 described later.

  On the other hand, if all parameter names match (step S111; YES) and the URLs do not match (step S112; NO), the URL of the screen information record most recently read in step S108 above Can be determined to have changed. Therefore, the rewriting unit 17 rewrites the URL included in the screen information record read most recently in step S108 among the screen information records stored in the screen information file with the URL extracted in step S105. (Step S113).

  Subsequently, the transmission unit 13 sends the URL and parameter information of the screen information stored in the screen information record read most recently in step S108 (if the URL has been updated in step S113, the updated URL). And an HTTP request for requesting the source code of the screen stored in the location corresponding to the URL is transmitted to the Web server device corresponding to the host of the screen information (step S114). Then, the process proceeds to step S104 described above.

  On the other hand, if it is determined in step S111 described above that there is a mismatched parameter name (step S111; NO), URLs to other screens are included in the screen source code of the HTTP response received in step S104. It is determined whether or not another exists (step S115). If this determination is YES (step S115; YES), the URL existing separately is transferred to step S110 described above as the URL extracted in step S105.

  On the other hand, if it is determined in step S115 that there are no other URLs to other screens (step S115; NO), the comparison unit 16 determines whether the URLs are based on the comparison in step S110. Are matched (step S116). When this determination is YES (step S116; YES), the output unit 18 outputs a message indicating that a part of the screen configuration may be changed to the display device (step S117), and ends the process. To do. On the other hand, if the URLs do not match (step S116; NO), the output unit 18 outputs a message indicating that a new screen may be added to the display device (step S118), and ends the process. .

  As described above, according to the screen sequence confirmation device 1 in the first embodiment, even if the URL of the screen configuring the Web system is changed, the latest screen is based on the response of the Web server device. When the information is acquired and the information stored in the screen information file is compared with the latest screen information acquired from the Web server device, the URLs do not match and the parameter names all match. It can be determined that the URL has been changed, and the URL of the screen information stored in the screen information file can be changed to the latest URL acquired from the Web server device. Further, when obtaining the latest screen information from the Web server device, an HTTP request can be generated using the parameter information stored in the screen information file. As a result, it is not necessary to manually perform the vulnerability inspection prior work again, so that the work efficiency can be improved. In other words, vulnerability inspection can be performed reliably and efficiently.

  Also, when the information stored in the screen information file is compared with the latest screen information acquired from the Web server device, the URLs match and all the parameter names do not match or only a part matches A new screen is added when there is a possibility that a part of the screen configuration may have been changed, or when the URLs do not match, and all the parameter names do not match or only partially match Since it is possible to notify that there is a possibility that the vulnerability has been detected, it is possible to reliably prevent the inspection of the vulnerability from being missed.

[Second Embodiment]
A second embodiment of the present invention will be described. The screen sequence confirmation device in the second embodiment is different from the screen sequence confirmation device in the first embodiment described above in that it has a function of further confirming that the URL has been changed before rewriting the URL of the screen information file. It is a point added to each component. The functional configuration of the screen sequence confirmation device in the second embodiment is the same as the functional configuration of the screen sequence confirmation device in the first embodiment shown in FIG. Is omitted. In the following, differences from the first embodiment will be mainly described.

  With reference to FIGS. 6 and 7, the operation of the screen sequence confirmation apparatus in the second embodiment will be described. FIG. 5 is a flowchart showing a processing procedure when confirming the screen sequence. Here, steps S201 to S211 and steps S221 to S224 shown in FIGS. 6 and 7 are the same as steps S101 to S111 and steps S101 to S111 shown in FIGS. 4 and 5 described in the first embodiment. Since it is the same as each process from S115 to step S118, description of each of these processes is omitted. In the following, each process from step S212 to step S220 different from the above-described first embodiment will be described.

  As a result of the comparison in step S210 shown in FIG. 7, when all the parameter names match (step S211; YES) and the URLs match (step S212; YES), the latest reading is performed in step S208. It can be determined that there is no change in the displayed screen information record. Therefore, the transmission unit 13 requests the screen source code stored in the location corresponding to the URL of the screen information based on the screen information stored in the screen information record read most recently in step S208. An HTTP request for sending is sent to the Web server device corresponding to the host of the screen information (step S220). Then, the process proceeds to step S204.

  On the other hand, if all the parameter names match as a result of the comparison at step S210 shown in FIG. 7 (step S211; YES) and the URLs do not match (step S212; NO), at step S208. It can be determined that there is a high possibility that the URL of the screen information record read most recently has changed. Therefore, based on the URL extracted in step S205 and the parameter information stored in the screen information record read most recently in step S208, the transmission unit 13 is stored in a location corresponding to the URL of this screen information. An HTTP request for requesting the source code of the current screen is transmitted to the Web server device corresponding to the host of the screen information (step S213).

  Subsequently, the receiving unit 14 receives an HTTP response transmitted from the Web server device in response to the HTTP request transmitted in step S213 (step S214).

  Subsequently, the extraction unit 15 extracts a URL to another screen from the source code of the screen included in the HTTP response received in step S214 (step S215).

  Subsequently, the reading unit 12 reads the next screen information record from the screen information file (step S216). For example, in the screen information file shown in FIG. 2, a screen information record whose screen name is “C” is read as the next screen information record.

  Subsequently, the comparison unit 16 determines whether or not the URL extracted in Step S215 includes the URL read most recently in Step S216 (Step S217). When this determination is NO (step S217; NO), the output unit 18 outputs a message including the URL of the screen information record read in step S208 to the display device (step S218), and ends the process. .

  On the other hand, when it is determined in step S217 that the URL extracted in step S215 includes the URL read most recently in step S216 (step S217; YES), step S208 is performed. It can be determined that there has been a change in the URL of the screen information record read in. Accordingly, the rewriting unit 17 rewrites and updates the URL included in the screen information record read in step S208 with the URL extracted in step S205 among the screen information records stored in the screen information file ( Step S219). Then, the process proceeds to step S205 described above.

  As described above, according to the screen sequence confirmation device 1 in the second embodiment, since the parameter names are all the same and the URLs are different, it can be determined that there is a high possibility that the URL has been changed. In addition, it is confirmed whether or not the URL to another screen included in the screen of the URL having a high possibility of being changed is stored in the URL of the next screen information record, and is confirmed to be stored. When it is done, the URL can be rewritten. Thereby, when the URL is changed, the screen information record can be changed after the sequence state after the change is surely confirmed.

[Third embodiment]
A third embodiment of the present invention will be described. In each of the above-described embodiments, the case where the URL to the other screen is directly described in the screen source code is described, but the URL to the other screen is not directly described in the screen source code. There is also. Therefore, in the third embodiment, an embodiment in which URLs to other screens are not directly described will be described.

  In the third embodiment, for example, a description will be given of an example in which the link destination changes depending on the selection location of a plurality of radio buttons provided on the screen. In the third embodiment, for example, a value value (predetermined parameter value) is set corresponding to each radio button, a URL is set corresponding to each value value, and one radio button is selected. In this case, description will be made on the assumption that event handler information including a predetermined function for acquiring a URL corresponding to the value value of the selected radio button is described in the Form tag of the screen source code.

  With reference to FIG. 8, the functional configuration of the screen sequence confirmation apparatus in the third embodiment will be described. Functionally, the screen sequence confirmation device 2 in the third embodiment is, for example, a storage unit 21, a reading unit 22, a transmission unit 23, a reception unit 24, an extraction unit 25, a comparison unit 26, and a rewrite. A unit 27, an output unit 28, and a function analysis unit 29. The storage unit 21, the reading unit 22, the transmission unit 23, and the reception unit 24 are the same as the storage unit 11, the reading unit 12, the transmission unit 13, and the reception unit 14 in the first embodiment. In the following, differences from the first embodiment will be mainly described.

  With reference to FIG. 9, the screen information stored in the screen information file in the third embodiment will be described. The data items of the screen information record are the same as the data items of the screen information record in the first embodiment shown in FIG. The parameter name of the screen information record shown in FIG. 9 stores “Value”, which is the name of the parameter for storing the value value of the selected radio button, and the parameter stored in this “Value” parameter. “AAA” or “CCC” is stored as a value. The Value value is set for each radio button on the same screen. Therefore, if the Value value is known, the radio button selected on the screen can be identified.

  In the first screen information record shown in FIG. 9, as a result of selecting the radio button corresponding to the value “AAA” and clicking the send button, the event handler described in the Form tag of the source code of the screen name “D” This indicates that a predetermined function included in the information has been executed and the screen has shifted to the URL screen set in correspondence with the value value “AAA” of the selected radio button.

  The extraction unit 25 extracts event handler information from the form tag of the screen source code included in the HTTP response. As the event handler information, for example, “OnSubmit”, “OnClick”, “OnSelect”, “OnFocus”, “OnChange”, and the like are applicable. If the event handler information cannot be extracted, the output unit 28 outputs a message indicating that the event handler information could not be extracted to the display device.

  The function analysis unit 29 determines whether “value” is registered in the parameter name of the screen information record most recently read by the reading unit 22. When the “value” parameter is registered, the function analysis unit 29 determines whether or not the value value that matches the parameter value corresponding to the “value” parameter is described in the form tag of the screen source code of the HTTP response. Determine whether.

  The function analysis unit 29 is described in the event handler information extracted by the extraction unit 25 when the value corresponding to the parameter value corresponding to the “value” parameter is described in the form tag of the screen source code. The predetermined function is analyzed, and the URL set corresponding to the parameter value of the “value” parameter is acquired.

  A specific example of the procedure for analyzing the function described in the event handler information will be described. For example, when “OnSubmit = examplefunc ()” is described in the event handler information, the function analysis unit 29 analyzes the function “examplefunc ()”. In this case, the function analysis unit 29 sets a URL that can be acquired when the “examplefunc ()” function is executed using the parameter value of the “value” parameter, corresponding to the parameter value of the “value” parameter. It is acquired as the URL that has been set.

  The comparison unit 26 determines whether or not the URL included in the screen information record read next by the reading unit 22 matches the URL acquired by the function analysis unit 29.

  When the URLs are not matched by the comparison by the comparison unit 16, the rewrite unit 27 selects the URL included in the screen information used for the comparison among the screen information records stored in the screen information file. The URL is rewritten with the URL acquired by the function analysis unit 29 used for the comparison.

  With reference to FIG. 10 and FIG. 11, the operation of the screen sequence confirmation apparatus in the third embodiment will be described. FIG. 10 and FIG. 11 are flowcharts showing the processing procedure when confirming the screen sequence.

  First, the reading unit 22 reads the first screen information record stored in the screen information file (step S301).

  If the screen information record cannot be read in step S301 (step S302; NO), the process ends. On the other hand, when the screen information record can be read (step S302; YES), the transmission unit 23, based on the screen information stored in the screen information record read in step S301, the URL of this screen information. An HTTP request for requesting the source code of the screen stored in the location corresponding to is transmitted to the Web server device corresponding to the host of the screen information (step S303).

  Subsequently, the receiving unit 24 receives an HTTP response transmitted from the Web server device in response to the HTTP request (step S304).

  Subsequently, the extraction unit 25 extracts event handler information from the source code of the screen included in the HTTP response (step S305).

  If event handler information could not be extracted in step S305 (step S306; NO), the output unit 28 sends a message indicating that the URL of the most recently read screen information record and event handler information could not be extracted. Is output to the display device (step S307), and the process ends.

  On the other hand, when event handler information can be extracted in step S305 (step S306; YES), the function analysis unit 29 determines whether or not “value” is registered in the parameter name of the screen information record read most recently. Is determined (step S308). If this determination is NO (step S308; NO), the process ends.

  On the other hand, when it is determined in the determination in step S308 that “value” is registered in the parameter name of the screen information record (step S308; YES), the function analysis unit 29 displays the screen information read most recently. It is determined whether or not a value that matches the parameter value corresponding to the “value” parameter of the record is described in the form tag of the screen source code of the HTTP response received in step S304 (step S309). If this determination is NO (step S309; NO), the process ends.

  On the other hand, if it is determined in step S309 that the value corresponding to the parameter value corresponding to the “value” parameter of the screen information record is described in the form tag of the screen source code (step S309; YES). The function analysis unit 29 analyzes the predetermined function described in the event handler information extracted in step S305, and obtains a URL set corresponding to the parameter value of the “value” parameter (step S310).

  Subsequently, the reading unit 22 reads the next screen information record from the screen information file (step S311). If the screen information record cannot be read (step S312; NO), the process ends.

  On the other hand, when the screen information record can be read (step S312; YES), the comparison unit 26 determines that the URL included in the screen information record most recently read in step S311 is the URL acquired in step S310. Is determined (step S313). If this determination is YES (step S313; YES), it can be determined that there is no change in the screen information record read in step S311. Therefore, the process proceeds to step S315 described later.

  On the other hand, when it is determined in the determination in step S313 that the URL included in the screen information record most recently read in step S311 does not match the URL acquired in step S310 (step S313; NO). It can be determined that the URL of the screen information record read most recently in step S311 has changed. Therefore, the rewriting unit 17 rewrites and updates the URL of the screen information record most recently read in step S311 with the URL acquired in step S310, among the screen information records stored in the screen information file. (Step S314).

  Subsequently, the transmission unit 13 is based on the screen information stored in the screen information record read most recently in step S311 (or updated screen information when the URL is updated in step S314). Then, an HTTP request for requesting the source code of the screen stored in the URL of the screen information is transmitted to the Web server device corresponding to the host of the screen information (step S315). Then, the process proceeds to step S304 described above.

  As described above, according to the screen sequence confirmation device 2 in the third embodiment, for example, the link destination changes depending on the position of the selected radio button. Even in the case of a Web system comprising screens that are not directly described, URLs to other screens can be specified. If the URL to another screen can be specified in this way, the URL of the screen information stored in the screen information file is changed to the latest URL acquired from the Web server device, as in the above-described embodiments. Can be changed. As a result, it is not necessary to manually perform the vulnerability inspection pre-work again, so that work efficiency can be improved. In other words, vulnerability inspection can be performed reliably and efficiently.

  Note that each of the above-described embodiments is merely an example, and does not exclude various modifications and technical applications that are not explicitly described in each embodiment. That is, the present invention can be implemented by being modified into various forms without departing from the spirit of the present invention.

  For example, in each of the above-described embodiments, the screen sequence confirmation apparatus includes all the constituent elements. However, the present invention is not limited to this, and each constituent element may be distributed and provided in a plurality of different apparatuses.

  DESCRIPTION OF SYMBOLS 1, 2 ... Screen sequence confirmation apparatus 11, 21 ... Storage part, 12, 22 ... Reading part, 13, 23 ... Transmission part, 14, 24 ... Reception part, 15, 25 ... Extraction part, 16, 26 ... Comparison part , 17, 27 ... rewrite unit, 18, 28 ... output unit, 29 ... function analysis unit.

Claims (5)

A storage unit for storing screen information having storage location information for specifying a storage location of an information resource related to a screen and parameter information including a parameter name corresponding to the information resource;
A reading unit that reads the screen information stored in the storage unit in the order of display of the screen;
Based on the first storage location information and the first parameter information included in the first screen information read by the reading unit, the server device corresponding to the first storage location information, A transmission unit that transmits a request for the information resource corresponding to the first storage location information;
A receiving unit that receives a response transmitted from the server device in response to the request;
An extraction unit for extracting the second storage location information and the second parameter information from the information resource included in the response;
Included in the second storage location information and the second parameter information extracted by the extraction unit, and the second screen information read out after the first screen information by the reading unit A comparison unit for comparing the third storage location information and the third parameter information, respectively;
When the comparison by the comparison unit does not match the storage location information and the parameter names included in the parameter information all match, the storage unit stores the first information stored in the storage unit. A rewriting unit that rewrites the third storage location information included in the screen information of 2 with the second storage location information extracted by the extraction unit;
A screen sequence confirmation apparatus comprising: The second extracted by the extraction unit when the storage location information does not match each other and the parameter names included in the parameter information all match by the comparison by the comparison unit. Based on the storage location information and the third parameter information, the server device corresponding to the second storage location information is sent to the second information resource corresponding to the second storage location information. A second transmitter for transmitting the request;
A second receiving unit for receiving a second response transmitted from the server device in response to the second request;
A second extraction unit for extracting the fourth storage location information from the information resource included in the second response;
The fourth storage location information extracted by the second extraction unit, and the fifth storage included in the third screen information read after the second screen information by the reading unit. A second comparison unit that compares the location information,
The rewriting unit may include the third information included in the second screen information stored in the storage unit when the storage location information matches each other by the comparison by the second comparison unit. The screen sequence confirmation apparatus according to claim 1, wherein the storage location information is rewritten with the second storage location information extracted by the extraction unit. A storage unit for storing screen information having storage location information for specifying a storage location of an information resource related to a screen and parameter information corresponding to the information resource;
A reading unit that reads the screen information stored in the storage unit in the order of display of the screen;
Based on the first screen information read by the reading unit, the first storage location information is stored in the server device corresponding to the first storage location information included in the first screen information. A transmitting unit for transmitting a request for the information resource corresponding to
A receiving unit that receives a response transmitted from the server device in response to the request;
An extraction unit for extracting event information including a predetermined function from the information resource included in the response;
The event information extracted by the extraction unit when the predetermined parameter value included in the parameter information of the first screen information read by the reading unit is included in the information resource of the response A function analysis unit that analyzes the predetermined function included in the information to obtain the second storage location information corresponding to the predetermined parameter value;
The second storage location information acquired by the function analysis unit, and the third storage location information included in the second screen information read out after the first screen information by the reading unit. A comparison unit for comparing
The third storage location information included in the second screen information stored in the storage unit when the storage location information does not match by the comparison by the comparison unit, A rewriting unit for rewriting with the second storage location information acquired by the function analysis unit;
A screen sequence confirmation apparatus comprising: A storage step of storing screen information having storage location information for specifying a storage location of an information resource related to a screen and parameter information including a parameter name corresponding to the information resource;
A reading step of reading the screen information stored in the storing step in the display order of the screen;
Based on the first storage location information and the first parameter information included in the first screen information read in the reading step, a server device corresponding to the first storage location information is provided. A transmission step of transmitting a request for the information resource corresponding to the first storage location information;
A receiving step of receiving a response transmitted from the server device in response to the request;
An extraction step of extracting second storage location information and second parameter information from the information resource included in the response;
Included in the second storage location information and the second parameter information extracted in the extraction step, and in the second screen information read next to the first screen information in the reading step A comparison step of comparing each of the third storage location information and the third parameter information;
The storage location information stored in the storage step when the storage location information is inconsistent and the parameter names included in the parameter information are all matched by the comparison in the comparison step. Rewriting the third storage location information included in the screen information with the second storage location information extracted by the extraction unit;
The screen sequence confirmation method characterized by including.   A screen sequence confirmation program for causing a computer to execute each step according to claim 4.

Images