Information processing program, information processing method and information processing device

The information processing device efficiently determines patch priorities by associating program functions with memory blocks and managing access prohibitions, addressing inefficiencies and malfunctions in patch application.

JP2024168862AInactive Publication Date: 2024-12-05FUJITSU LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023085881
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-25
Publication Date
2024-12-05
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing methods for applying software patches can lead to programs malfunctioning due to indiscriminate application, causing inefficiencies and increased processing load and memory consumption.

Method used

An information processing device that associates program functions with memory blocks and manages access prohibitions to efficiently determine which patches to prioritize based on actual function execution history, reducing the need for continuous call history recording.

Benefits of technology

This approach allows for efficient patch prioritization, minimizing program disruptions and reducing memory consumption while ensuring timely application of critical patches.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024168862000001_ABST
    Figure 2024168862000001_ABST
Patent Text Reader

Abstract

To enable a patch of a preferential application object to be efficiently determined.SOLUTION: A processing part creates correspondence information for associating each of a plurality of functions included in a program with a memory block in which an execution code corresponding to the functions is arranged when the program is loaded. The processing part sets a plurality of memory blocks related to the execution code of the program to access inhibition. The processing part releases the access inhibition of the memory block when access the memory block set to the access inhibition is detected during the execution of the program. The processing part acquires block information showing the memory block from which the access inhibition is released. The processing part determines whether to make a patch related to vulnerability shown by vulnerability information to the program a preferential application object on the basis of information showing a first function specified on the basis of the vulnerability information among the plurality of functions, the correspondence information and the block information.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing program, an information processing method, and an information processing device. [Background technology]

[0002] When a vulnerability is discovered in software, the software developer or other parties provide a patch to address the vulnerability. As a result, technology has been developed to update software by applying patches.

[0003] For example, there has been proposed a method of automatically determining whether or not application software should be updated based on startup information indicating the number of times the application software has been started, and automatically updating the application software to the latest version if an update condition is met.

[0004] There has also been proposed a method for monitoring the use of executable content at an endpoint such as a computer, calculating a score indicating the frequency of use of the executable content, and selectively applying a patch to the executable content based on the score.

[0005] There is also a proposal for a method for collecting, by a calculator, behavioral characteristics relating to the use of license options for a software product in the form of a customer-specific data set, and for evaluating the data set by the calculator to determine which components of the software product require an update and for performing the update.

[0006] In addition, a system has been proposed for online upgrade of a database environment using transparently patched seed data tables. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] JP 2004-355563 A [Patent Document 2] US Patent Application Publication No. 2012 / 0054729 [Patent Document 3] JP 2015-141719 A [Patent Document 4] US Patent Application Publication No. 2014 / 0101645 Summary of the Invention [Problem to be solved by the invention]

[0008] Patches related to some functions included in software programs are sometimes provided. However, when applying a patch, there is a possibility that a program that was previously working may no longer work, so it is not advisable to blindly apply the patch provided.

[0009] One possible solution to this problem would be to use a debugger or the like to record the call history of a function each time it is called during program execution, and when new vulnerability information is obtained, use the call history to quickly apply only the patches related to the functions that were actually executed.

[0010] However, this method records the call history every time a function is called, which causes problems such as the processing load for recording the call history affecting the execution speed of the program and the large memory consumption required to hold the call history.

[0011] In one aspect, the present invention aims to enable efficient determination of patches to be applied with priority. [Means for solving the problem]

[0012] In one aspect, an information processing program is provided. The information processing program causes a computer to execute the following process. When loading the program, the computer creates correspondence information that associates each of a plurality of functions included in the program with a memory block in which an executable code corresponding to the function is placed. The computer sets a plurality of memory blocks related to the executable code of the program as access-prohibited. When the computer detects an access to a memory block set as access-prohibited during execution of the program, the computer lifts the access prohibition of the memory block. The computer obtains block information indicating the memory block for which the access prohibition has been lifted. The computer determines whether or not to preferentially apply a patch related to a vulnerability indicated in the vulnerability information to the program, based on information indicating a first function identified based on vulnerability information among the plurality of functions, the correspondence information, and the block information.

[0013] In one embodiment, there is provided an information processing method executed by a computer.In another embodiment, there is provided an information processing device having a storage unit and a processing unit. Effect of the Invention

[0014] On the one hand, it allows for efficient determination of which patches should be applied with priority. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram illustrating an information processing apparatus according to a first embodiment. [Diagram 2] FIG. 11 illustrates an example of hardware of an information processing apparatus according to a second embodiment. [Diagram 3] FIG. 2 is a diagram illustrating an example of functions of an information processing device. [Figure 4] 11A and 11B are diagrams illustrating examples of a function table and an access management table. [Diagram 5] 13 is a flowchart illustrating an example of a program execution process. [Figure 6] 13 is a flowchart illustrating an example of a patch application determination process. [Figure 7] 13 is a flowchart illustrating an example of a pre-reboot process. [Figure 8] 13 is a flowchart illustrating an example of a post-restart program execution process. [Figure 9] FIG. 13 is a diagram illustrating an example of setting a function table. [Figure 10] FIG. 13 illustrates an example of updating the access management table; [Figure 11] FIG. 13 illustrates an example of patch application determination. [Figure 12] FIG. 13 is a diagram illustrating an example of identifying a function related to vulnerability information. [Figure 13] FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] The present embodiment will be described below with reference to the drawings. [First embodiment] A first embodiment will be described.

[0017] FIG. 1 is a diagram illustrating an information processing apparatus according to a first embodiment. The information processing device 10 determines which patch should be applied preferentially to a program. The information processing device 10 may be called a computer. The information processing device 10 includes a storage unit 11 and a processing unit 12.

[0018] The storage unit 11 may be a volatile semiconductor memory such as a random access memory (RAM), or may be a non-volatile storage such as a hard disk drive (HDD) or a flash memory. The processing unit 12 is, for example, a processor such as a central processing unit (CPU), a graphics processing unit (GPU), or a digital signal processor (DSP). However, the processing unit 12 may include an electronic circuit for a specific purpose such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The processor executes a program stored in a memory such as a RAM (which may be the storage unit 11). A set of multiple processors may be called a "multiprocessor" or simply a "processor."

[0019] When a program is loaded, the processing unit 12 creates the correspondence information 11a and stores it in the storage unit 11. The correspondence information 11a is information that associates each of a plurality of functions included in the program with a memory block in which an execution code corresponding to the function is placed. The execution code is also called executable code or object code. A memory block is a unit of memory area such as a RAM into which the program is loaded. For example, the correspondence information 11a holds a correspondence relationship between a function name and identification information of a memory block. Specifically, the correspondence information 11a includes a correspondence relationship between a function name "function F1" and identification information "#1" of a memory block. Here, the function with the function name "function F1" is simply written as function F1. Also, the memory block with identification information "#1" is simply written as memory block #1. Also, the correspondence information 11a includes a correspondence relationship between a function F2 and memory block #1 and a correspondence relationship between a function F3 and memory block #2.

[0020] The processing unit 12 sets a plurality of memory blocks related to the execution code of the program as access-prohibited. When the processing unit 12 detects an access to a memory block set as access-prohibited during execution of the program, the processing unit 12 releases the access prohibition to the memory block. Here, the processing unit 12 can detect an access to a memory block set as access-prohibited as an exception in an OS (Operating System). In addition, once the access prohibition to the memory block is released, access to the memory block becomes possible, and the processing of the program continues in a state in which the access prohibition to the memory block is maintained as released. The processing unit 12 acquires block information indicating the memory block for which the access prohibition has been released.

[0021] Here, the following examples of block information are possible: When multiple memory blocks related to the executable code of a program are set as access-prohibited, the processing unit 12 generates block information 11b1 in which the access prohibition flag is set to "1" (or "TRUE") for each of the multiple memory blocks. Here, the access prohibition flag = "1" (or "TRUE") indicates that access is prohibited. The access prohibition flag = "0" (or "FALSE") indicates that the access prohibition has been lifted.

[0022] When the processing unit 12 detects an access to a memory block during program execution, the processing unit 12 updates the access prohibition flag of the memory block in the block information 11b1 from "1" to "0." Block information 11b2 illustrates a case in which an access to memory block #1 is detected during program execution, and the access prohibition flag of memory block #1 is updated from "1" to "0." In this case, the processing unit 12 can identify memory block #1 for which access prohibition has been released, based on the block information 11b2.

[0023] The processing unit 12 judges whether or not to preferentially apply a patch related to a vulnerability indicated in the vulnerability information to a program based on information indicating a first function identified based on the vulnerability information among a plurality of functions, the correspondence information 11a, and the block information 11b2. Here, the vulnerability information is information indicating a vulnerability related to a program part such as a library or a component. The vulnerability information is downloaded, for example, via a network. A patch is data for correcting a vulnerability of a program part in which a vulnerability has been found, and is also called a correction program.

[0024] For example, suppose that vulnerability of a certain program part is indicated in the vulnerability information D1, and the program part is used in a function F2. In this case, the processing unit 12 acquires information indicating the function F2 identified based on the vulnerability information D1. The function F2 is an example of a first function. The identification of the function F2 based on the vulnerability information D1 may be performed by the processing unit 12 or by a user. For example, by storing information indicating the correspondence between the program part and the function that uses the program part in advance in the storage unit 11, the processing unit 12 may identify the function F2 from the program part indicated in the vulnerability information D1 based on the information and the vulnerability information D1.

[0025] The processing unit 12 identifies the memory block #1 corresponding to the function F2 based on the correspondence information 11a. The processing unit 12 identifies that the access prohibition flag corresponding to the memory block #1 is "0" based on the block information 11b2. Then, since the function F2 may have been executed, there is a possibility that vulnerable code has been executed, so the processing unit 12 prioritizes application of a patch related to the vulnerability indicated in the vulnerability information D1. Here, if the program execution record indicates that the function F2 may have been executed, there is a high possibility that the function F2 will be executed in the future. And, there is a high possibility that damage due to a vulnerability will occur due to the execution of the function F2, compared to a function that is not executed. Therefore, there is a high need to apply a patch related to the vulnerability indicated in the vulnerability information D1 as soon as possible.

[0026] Also, for example, suppose that a vulnerability of a certain program part is indicated in the vulnerability information D2, and the program part is used in a function F3. In this case, the processing unit 12 acquires information indicating the function F3 identified based on the vulnerability information D2. The function F3 is an example of a first function. As described above, the identification of the function F3 based on the vulnerability information D2 may be performed by the processing unit 12 or by a user.

[0027] The processing unit 12 identifies the memory block #2 corresponding to the function F3 based on the correspondence information 11a. The processing unit 12 identifies that the access prohibition flag corresponding to the memory block #2 is "1" based on the block information 11b2. Then, since the function F3 has not been executed, the processing unit 12 excludes the patch related to the vulnerability indicated in the vulnerability information D2 from the target of preferential application. Here, if the function F3 has not been executed in the program execution history, it is highly likely that the function F3 will not be executed in the future. Therefore, the possibility of damage caused by the vulnerability included in the function F3 is lower than that of a function that may have been executed. Therefore, the patch related to the vulnerability indicated in the vulnerability information D2 does not need to be applied immediately, and may be applied after it is confirmed that there is no impact on the operation of the program, for example.

[0028] For example, the processing unit 12 may output information indicating that the patch for the vulnerability information D1 is to be applied preferentially and the patch for the vulnerability information D2 is not to be applied preferentially. By referring to the information, the user can confirm that the patch for the vulnerability information D1 should be applied preferentially to the program in question, and that the patch for the vulnerability information D2 does not need to be applied preferentially. In this case, the user applies the patch for the vulnerability information D1 to the program in question preferentially, and does not apply the patch for the vulnerability information D2 for the time being.

[0029] As described above, according to the information processing device 10, when a program is loaded, correspondence information 11a is created that associates each of a plurality of functions included in the program with a memory block in which an execution code corresponding to the function is placed. A plurality of memory blocks related to the execution code of the program are set to be access-prohibited. When an access to a memory block set to be access-prohibited is detected during execution of the program, the access prohibition of the memory block is lifted. Block information 11b2 indicating the memory block for which the access prohibition has been lifted is acquired. Based on information indicating a first function identified from the vulnerability information among the plurality of functions, the correspondence information 11a, and the block information 11b2, it is determined whether or not a patch related to the vulnerability indicated in the vulnerability information is to be applied preferentially to the program.

[0030] This allows the information processing device 10 to efficiently determine which patch is to be applied with priority. During program execution, the number of times that the detection of access prohibition to one memory block and the release of access occur is at most once. Therefore, the information processing device 10 can identify functions that may have actually been executed while suppressing the influence on the execution of the program. Therefore, the information processing device 10 is useful for narrowing down patches that should be applied urgently, for example, in measures against vulnerabilities in programs in actual operation. In addition, the information processing device 10 can suppress the amount of information used in the process of patch application judgment to the amount of information equivalent to the correspondence information 11a and the block information 11b1 (or the block information 11b2). Therefore, memory consumption is reduced compared to a method in which the call history of a function is recorded every time the function is called.

[0031] By distinguishing between patches that are to be applied with priority and patches that are not to be applied with priority in this way, the information processing device 10 can avoid applying patches carelessly to programs, thereby reducing the risk that a program will not operate due to the application of a patch.

[0032] [Second embodiment] Next, a second embodiment will be described. FIG. 2 illustrates an example of hardware of an information processing apparatus according to the second embodiment.

[0033] The information processing device 100 has a processor 101, a RAM 102, a HDD 103, a GPU 104, an input interface 105, a medium reader 106, and a communication interface 107. These units of the information processing device 100 are connected to a bus inside the information processing device 100. The processor 101 corresponds to the processing unit 12 of the first embodiment. The RAM 102 or the HDD 103 corresponds to the storage unit 11 of the first embodiment.

[0034] The processor 101 is an arithmetic device that executes program instructions. The processor 101 is, for example, a CPU. The processor 101 loads at least a part of the program and data stored in the HDD 103 into the RAM 102 and executes the program. The processor 101 may include multiple processor cores. The information processing device 100 may have multiple processors. The processing described below may be executed in parallel using multiple processors or processor cores. A set of multiple processors may also be called a "multiprocessor" or simply a "processor."

[0035] The RAM 102 is a volatile semiconductor memory that temporarily stores programs executed by the processor 101 and data used in calculations by the processor 101. Note that the information processing device 100 may include a type of memory other than a RAM, or may include multiple memories.

[0036] The HDD 103 is a non-volatile storage device that stores software programs such as an OS, middleware, and application software, and data. The information processing device 100 may include other types of storage devices such as a flash memory or an SSD (Solid State Drive), or may include multiple non-volatile storage devices.

[0037] The GPU 104 outputs an image to a display 111 connected to the information processing device 100 in accordance with an instruction from the processor 101. As the display 111, any type of display can be used, such as a CRT (Cathode Ray Tube) display, a liquid crystal display (LCD: Liquid Crystal Display), a plasma display, or an organic EL (OEL: Organic Electro-Luminescence) display.

[0038] The input interface 105 acquires an input signal from an input device 112 connected to the information processing device 100, and outputs the signal to the processor 101. The input device 112 may be a pointing device such as a mouse, a touch panel, a touch pad, or a trackball, a keyboard, a remote controller, or a button switch. In addition, a plurality of types of input devices may be connected to the information processing device 100.

[0039] The medium reader 106 is a reading device that reads programs and data recorded on a recording medium 113. For example, a magnetic disk, an optical disk, a magneto-optical disk (MO: Magneto-Optical disk), a semiconductor memory, etc. can be used as the recording medium 113. Magnetic disks include flexible disks (FD: Flexible Disks) and HDDs. Optical disks include compact discs (CDs) and digital versatile discs (DVDs).

[0040] The medium reader 106 copies, for example, the program or data read from the recording medium 113 to another recording medium such as the RAM 102 or the HDD 103. The read program is executed, for example, by the processor 101. Note that the recording medium 113 may be a portable recording medium, and may be used for distributing the program or data. Also, the recording medium 113 and the HDD 103 may be referred to as computer-readable recording media.

[0041] The communication interface 107 is connected to a network 114 and communicates with other information processing devices via the network 114. The communication interface 107 may be a wired communication interface connected to a wired communication device such as a switch or a router, or a wireless communication interface connected to a wireless communication device such as a base station or an access point.

[0042] FIG. 3 is a diagram illustrating an example of functions of the information processing device. The information processing device 100 has a memory area 120, a management information storage unit 130, a vulnerability information storage unit 140, a program load unit 150, an exception processing unit 160, and a patch application determination unit 170. The memory area 120 is a part of the storage area of ​​the RAM 102. The management information storage unit 130 and the vulnerability information storage unit 140 use the storage areas of the RAM 102 and the HDD 103. The program load unit 150, the exception processing unit 160, and the patch application determination unit 170 are realized by the CPU 101 executing an information processing program stored in the RAM 102.

[0043] Memory area 120 is an area on RAM 102 into which executable code of a program used by a user is loaded. Memory area 120 has a plurality of memory blocks partitioned into predetermined sizes. The plurality of memory blocks include memory blocks #1, #2, #3, .... The program includes a plurality of functions. Executable code corresponding to each of the plurality of functions is placed in one of the plurality of memory blocks. For example, various OSS (Open Source Software) are incorporated into the program. For example, the functions included in the program use OSS libraries or components. In addition, when a vulnerability is discovered in the OSS, for example, vulnerability information indicating the vulnerability is made public on a predetermined website on the Internet.

[0044] The management information storage unit 130 has a function table 131 and an access management table 132. The function table 131 and the access management table 132 are stored. The function table 131 is information indicating in which memory block of the memory area 120 an execution code corresponding to each function is located. The function table 131 is held in a non-volatile storage area of ​​the management information storage unit 130.

[0045] The access management table 132 is information indicating whether or not each memory block in the memory area 120 is set to be inaccessible. As will be described later, when a program is loaded, all memory blocks in which each executable code of the program is to be placed are set to be inaccessible.

[0046] In addition, the access management table 132 may be the control information itself used to control access prohibition to memory blocks by the OS or the like, or it may be information provided separately from the control information simply to enable reference of the access prohibition status for each memory block.

[0047] The vulnerability information storage unit 140 stores vulnerability information 141. The vulnerability information 141 is information on vulnerabilities found in libraries or components of OSS. For example, the vulnerability information 141 is downloaded from a predetermined server computer via the Internet.

[0048] The program load unit 150 loads a program. That is, the program load unit 150 places the execution code of the program in the memory area 120. When loading the program, the program load unit 150 analyzes the execution code of the entire program, identifies memory blocks in which the execution code corresponding to each function is placed, and generates a function table 131. The program load unit 150 also sets all memory blocks in which the execution code corresponding to each function is placed as inaccessible. At this time, the program load unit 150 sets in the access management table 132 that all the memory blocks are inaccessible.

[0049] During program execution, the exception processing unit 160 detects an access to a memory block set as being prohibited as an exception, and lifts the access prohibition to the memory block as exception processing. The exception processing unit 160 sets in the access management table 132 that the access prohibition to the memory block has been lifted. With the access prohibition lifted, the memory block can be accessed, and program processing continues. The exception processing unit 160 can also detect an access to a memory block set as being prohibited as, for example, an OS exception.

[0050] The patch application determination unit 170 determines whether or not a patch that addresses a vulnerability indicated in the vulnerability information 141 is to be applied preferentially to a program, based on the function table 131 and the access management table 132. The patch application determination unit 170 determines whether or not there is a possibility that the corresponding function has been executed, based on the function table 131 and the access management table 132. If there is a possibility that the corresponding function has been executed, the patch application determination unit 170 determines that the corresponding patch is to be applied preferentially. On the other hand, if the corresponding function has not been executed, the patch application determination unit 170 determines that the corresponding patch is not to be applied preferentially.

[0051] FIG. 4 illustrates an example of the function table and the access management table. The function table 131 includes fields for function name and placement block. The function name field stores the name of the function. The placement block field stores identification information (e.g., an identification number) of a memory block in which execution code corresponding to the function of the function name is placed.

[0052] For example, function table 131 has a record with a function name "Function F1" and a placement block "#1." This record indicates that the function with the function name "Function F1" is placed in memory block #1. In the following description, the function with the function name "Function F1" will be written simply as "Function F1."

[0053] Moreover, the function table 131 further includes a record indicating that, for example, the function F2 is arranged in the memory block #1 and the function F3 is arranged in the memory block #2. The function table 131 is an example of the correspondence information 11a according to the first embodiment.

[0054] The access management table 132 includes items for memory block and access prohibition flag. The memory block item registers identification information of the memory block. The access prohibition flag item registers an access prohibition flag. Here, an access prohibition flag = "1" indicates that the memory block is inaccessible. An access prohibition flag = "0" indicates that the memory block is not inaccessible, i.e., the access prohibition of the memory block has been lifted.

[0055] The access management table 132 is an example of the block information 11b1 and the block information 11b2 according to the first embodiment. When loading a program, program load unit 150 sets the access prohibition flags of all memory blocks in access management table 132 to "1." When exception handling unit 160 detects an exception indicating that an access to a prohibited memory block has occurred, it releases the access prohibition of the memory block and updates the access prohibition flag of the memory block in access management table 132 to "0."

[0056] In this case, an exception occurs at most once for each memory block. In other words, even if a memory block that has been reset to "0" is accessed thereafter, no exception occurs. Therefore, the impact of the processing by the exception processing unit 160 on the execution speed of the program is small.

[0057] Next, the processing procedure of the information processing device 100 will be described. FIG. 5 is a flowchart showing an example of a program execution process. (S10) The program load unit 150 analyzes the executable file of the program to identify memory blocks in which each function included in the program is to be allocated.

[0058] (S11) The program load unit 150 sets the function table 131 based on the analysis result of step S10, and saves the function table 131. The function table 131 is stored in a non-volatile storage area such as the HDD 103.

[0059] (S12) The program load unit 150 creates the access management table 132 and sets all access prohibition flags to 1. Accordingly, all memory blocks in which the execution code corresponding to each function is placed are set to be access prohibited.

[0060] (S13) The program load unit 150 starts executing the program. (S14) When an access to a memory block occurs, the OS of the information processing device 100 judges whether or not it is the first access to the memory block. If it is the first access to the memory block, the OS generates an exception because it is an access to a memory block that is prohibited from being accessed, and the process proceeds to step S15. If it is the second or subsequent access to the memory block, the process proceeds to step S17.

[0061] (S15) The exception processing unit 160 detects the occurrence of an exception caused by an access to a memory block that is set as being access-prohibited. (S16) The exception processing unit 160 resets the access prohibition flag of the corresponding memory block in the access management table 132 to 0. Accordingly, the prohibition of access to the corresponding memory block is lifted.

[0062] (S17) The OS of the information processing device 100 continues the execution of the program. Then, the process proceeds to step S14. Thereafter, the processes from step S14 onwards are repeated until the execution of the program is completed.

[0063] FIG. 6 is a flowchart illustrating an example of a patch application determination process. The following procedure is executed, for example, when new vulnerability information 141 is acquired by the information processing device 100. The following procedure may be executed during execution of a program to be executed according to the procedure of FIG.

[0064] (S20) Upon acquiring the vulnerability information 141, the patch application determining unit 170 stores it in the vulnerability information storage unit 140. (S21) The patch application determination unit 170 acquires, from among a plurality of functions included in a program, functions that have vulnerabilities from the vulnerability information 141. For example, the patch application determination unit 170 identifies an OSS library in which a vulnerability has been discovered based on the vulnerability information 141, and acquires functions that use the library as functions that have vulnerabilities.

[0065] (S22) The patch application determining unit 170 acquires a vulnerable function and a memory block (location block) corresponding to the vulnerable function from the function table 131. (S23) The patch application determining unit 170 determines whether the access prohibition flag of the corresponding memory block in the access management table 132 is 0. If the access prohibition flag of the corresponding memory block is 0, the process proceeds to step S24. If the access prohibition flag of the corresponding memory block is 1, the process proceeds to step S25.

[0066] (S24) The patch application determination unit 170 determines that the patch related to the vulnerability is to be applied with priority. The patch application determination unit 170 outputs information indicating that the patch related to the vulnerability is to be applied with priority. For example, the patch application determination unit 170 may display on the display 111 a message indicating that the patch related to the vulnerability needs to be applied as soon as possible. Then, the patch application determination process ends.

[0067] (S25) The patch application determination unit 170 determines that the patch related to the vulnerability is not a target for priority application. The patch application determination unit 170 outputs information indicating that the patch related to the vulnerability is not a target for priority application. For example, the patch application determination unit 170 may display on the display 111 a message indicating that the patch related to the vulnerability does not need to be applied immediately. Then, the patch application determination process ends.

[0068] In this way, the patch application determining unit 170 can lower the priority of patch application related to functions that are not used in actual operation. Next, a processing procedure for restarting the information processing device 100 or restarting a program being operated will be described.

[0069] FIG. 7 is a flowchart illustrating an example of pre-reboot processing. (S30) The patch application determining unit 170 stores the information of the access management table 132 in a non-volatile storage device such as the HDD 103.

[0070] (S31) The OS of the information processing device 100 restarts the information processing device 100 or restarts the programs being operated. In this way, the patch application determining unit 170 stores the information of the access management table 132 in a non-volatile storage device such as the HDD 103, making it possible to store data on the access status over a long period of program operation.

[0071] FIG. 8 is a flowchart showing an example of a post-restart program execution process. The post-restart program execution process differs from the procedure in Fig. 5 in that step S10a is executed instead of steps S10 to S12. Therefore, in the following, step S10a will be mainly described, and a description of steps S13 to S17 will be omitted.

[0072] (S10a) The patch application determining unit 170 reads out the information of the access management table 132 stored in the non-volatile storage area, and sets it in the access management table 132 in the RAM 102. As a result, the access management table 132 is restored to the state before the reboot. Then, the process proceeds to step S13.

[0073] In this way, even if the information processing device 100 or the program is restarted while the program is in operation, the information processing device 100 can start executing the program by inheriting the contents of the access management table 132 before the restart even after the restart.

[0074] Next, a specific example of a method for setting the function table 131 will be described. FIG. 9 is a diagram showing an example of setting the function table. For example, the execution codes of functions F1 and F2 are placed in memory block #1 of memory area 120. Also, the execution code of function F3 is placed in memory block #2 of memory area 120. In this case, program load unit 150 sets in function table 131 a record of function name "function F1" and placement block "#1", a record of function name "function F2" and placement block "#1", and a record of function name "function F3" and placement block "#2".

[0075] FIG. 10 illustrates an example of an update of the access management table. 10A illustrates an example of the access management table 132 in the initial state, that is, when all memory blocks are set to be inaccessible when a program is loaded. In the initial state, the access prohibition flag "1" is set for all memory blocks in the access management table 132.

[0076] 10B shows an example of updating the access management table 132 when memory block #1 is accessed for the first time after a program is loaded and the access prohibition for memory block #1 is lifted. For example, when function F2 or function F1 is executed, access to memory block #1 occurs and the access prohibition for memory block #1 is lifted. In this case, the access prohibition flag corresponding to memory block #1 is updated from "1" to "0".

[0077] Next, a specific example of patch applicability determination based on the vulnerability information 141, the function table 131, and the access management table 132 will be described. FIG. 11 illustrates an example of a patch application determination.

[0078] The patch application determination unit 170 identifies an OSS library reported to have a vulnerability from the vulnerability information 141. The patch application determination unit 170 identifies a function F2 that uses the library based on correspondence information between a plurality of functions included in the program to be maintained and the library used by the function. Note that the identification of the function F2 based on the vulnerability information 141 may be performed by a user, and the patch application determination unit 170 may receive an input of the identified function F2 from the user.

[0079] Next, the patch application determining unit 170 identifies a memory block #1 corresponding to the function F2 identified from the vulnerability information 141, based on the function table 131. Furthermore, the patch application determining unit 170 determines, based on the access management table 132, whether the access prohibition flag corresponding to the memory block #1 is “0” (access prohibition released).

[0080] When the patch application determination unit 170 determines that the access prohibition flag corresponding to memory block #1 is "0" (access prohibition released), it determines that the patch related to the vulnerability indicated in the vulnerability information 141 is to be applied preferentially. This is because, when the access prohibition flag corresponding to memory block #1 is "0" (access prohibition released), function F2 may have been executed and function F2 may be executed in the future.

[0081] Next, an example of a process for identifying a function related to the vulnerability information 141 will be described. FIG. 12 is a diagram illustrating an example of identifying a function related to vulnerability information. For example, the management information storage unit 130 may store in advance a function management table 133. The function management table 133 indicates the correspondence between a function name and the name of a program component (program component name) used by the function with that function name. The program component is, for example, an OSS library or component. For example, the function management table 133 indicates the correspondence between a function F1 and a program component X used by the function F1, and the correspondence between a function F2 and a program component Y used by the function F2.

[0082] Here, it is assumed that the vulnerability information 141 indicates that the program component Y has a vulnerability. In this case, the patch application determination unit 170 can identify the function F2 in which the program component Y in which the vulnerability is found is used, based on the vulnerability information 141 and the function management table 133. However, as described above, the patch application determination unit 170 may accept an input of the function F2 identified by the user based on the vulnerability information 141, and perform patch application determination based on the function table 131 and the access management table 132.

[0083] Next, a comparative example for acquiring the execution record of a function will be described. FIG. 13 is a diagram showing a comparative example. An information processing device 200 in the comparative example executes a program 211 on a debugger, and records a call history of a function included in a program 221 every time the function is called. The information processing device 200 has a memory area 210, a function call history table 220, and a function call monitoring unit 230.

[0084] The memory area 210 is an area on the RAM into which the program 211 is loaded. The function call history table 220 is information that holds the function call history. Each time a function is called, the function call monitoring unit 230 records a record indicating that the function has been called in the function call history table 220. The function call monitoring unit 230 is implemented, for example, as a debugger function. When vulnerability information is acquired, it is determined based on the function call history table 220 whether or not a function related to the vulnerability information has been executed, and if executed, it is determined that a patch for the vulnerability information is to be applied.

[0085] In the method of the comparative example, a record is added to the function call history table 220 every time a function is called, resulting in a large memory consumption. Also, the function call monitoring unit 230 is executed every time a function is called, resulting in a high processing load and affecting the execution speed of the program 211. Also, since the program 211 is run on a debugger, it is difficult to use the method of the comparative example for a program in actual operation.

[0086] On the other hand, according to the information processing device 100, by associating memory blocks with functions and obtaining access status for each memory block, the granularity of obtaining the execution results of the functions becomes coarse, but the impact on the execution speed of the program being executed is suppressed. This allows the information processing device 100 to efficiently determine which patches should be applied first.

[0087] For example, the information processing device 100 can reduce the load to about one tens of thousands of times lower than the comparative method using the debugger. The information processing device 100 has a smaller effect on the execution speed of a running program than the comparative method, so the function of the information processing device 100 is particularly useful for vulnerability countermeasures for programs in actual operation. In addition, the information processing device 100 can reduce the amount of information used in the process of determining whether a patch is applied to an amount of information equivalent to the function table 131 and the access management table 132. Therefore, unlike the comparative method in which the call history of a function is recorded every time the function is called, the data of the call history is not continuously added, and memory consumption is reduced compared to the comparative method.

[0088] By thus distinguishing between patches that are to be applied with priority and patches that are not to be applied with priority, the information processing device 100 can avoid applying patches indiscriminately to programs and reduce the risk that the program will stop working as a result of applying a patch.

[0089] As described above, the information processing device 100 executes, for example, the following process. When a program is loaded, the processor 101 creates correspondence information that associates each of a plurality of functions included in the program with a memory block in which execution code corresponding to the function is placed. The processor 101 sets a plurality of memory blocks related to the execution code of the program as access-prohibited. When the processor 101 detects an access to a memory block set as access-prohibited during execution of the program, the processor 101 releases the access prohibition of the memory block. The processor 101 acquires block information indicating the memory block for which the access prohibition has been released. The processor 101 determines whether or not to preferentially apply a patch related to a vulnerability indicated in the vulnerability information to the program, based on information indicating a first function identified based on vulnerability information among the plurality of functions, the correspondence information, and the block information.

[0090] This allows the information processing apparatus 100 to efficiently determine patches to be applied with priority. Here, the function table 131 is an example of correspondence information. The access management table 132 is an example of block information.

[0091] For example, the processor 101 detects an access to a memory block set as an access-prohibited memory block as an exception. This enables the information processing device 100 to easily identify a function that may have been executed without executing special software such as a debugger.

[0092] Furthermore, processor 101 identifies a first memory block in which execution code corresponding to the first function is placed, based on the correspondence information. Processor 101 determines whether or not access prohibition to the first memory block has been lifted, based on the block information. If access prohibition to the first memory block has been lifted, processor 101 determines that a patch related to the vulnerability indicated in the vulnerability information is to be applied with priority. If access prohibition to the first memory block has not been lifted, processor 101 determines that the patch is not to be applied with priority.

[0093] This allows the information processing device 100 to appropriately narrow down the patches to be applied with priority, and reduces the risk of a program ceasing to operate due to an indiscriminate application of a patch to the program. Narrowing down the patches to be applied with priority also has the advantage of reducing the number of patches to be applied urgently, thereby reducing the time that the program is interrupted due to patch application. For example, patches that do not need to be applied urgently may be applied at a time when a service interruption by the program is scheduled, such as during regular maintenance.

[0094] The processor 101 saves the block information stored in the volatile first storage device in the non-volatile second storage device when the information processing device 100 (computer) is stopped or the execution of a program is stopped. The processor 101 reads the block information saved in the second storage device and stores the block information in the first storage device when the information processing device 100 is started or the execution of a program is started.

[0095] This allows the information processing device 100 to store, for a long period of time, block information corresponding to the access management table 132. Here, the RAM 102 is an example of a first storage device, and the HDD 103 is an example of a second storage device.

[0096] Furthermore, the vulnerability information indicates, for example, a vulnerability found in the first program part. In this case, the processor 101 may identify the first function in which the first program part is used based on the vulnerability information and information indicating a correspondence between each of the multiple functions and the program parts used in the function.

[0097] This enables the information processing device 100 to reduce the user's work of identifying the first function based on the vulnerability information 141, and to further increase the efficiency of determining which patches are to be applied preferentially. Here, the above-mentioned function management table 133 is an example of information indicating the correspondence between each of a plurality of functions and the program parts used in the function.

[0098] The information processing of the first embodiment can be realized by causing the processing unit 12 to execute a program. The information processing of the second embodiment can be realized by causing the processor 101 to execute a program. The program can be recorded in a computer-readable recording medium 113.

[0099] For example, the program can be distributed by distributing recording medium 113 on which the program is recorded. Alternatively, the program may be stored in another computer and distributed via a network. The computer may store (install) the program recorded in recording medium 113 or a program received from another computer in a storage device such as RAM 102 or HDD 103, and read and execute the program from the storage device. [Explanation of symbols]

[0100] 10. Information processing device 11 Storage section 11a Compatibility Information 11b1,11b2 Block Information 12 Processing section D1,D2 Vulnerability information

Claims

1. On the computer, creating, when loading a program, correspondence information that associates each of a plurality of functions included in the program with a memory block in which an execution code corresponding to the function is allocated; Setting a plurality of memory blocks related to the execution code of the program to be inaccessible; When an access to the memory block set as being access-prohibited is detected during execution of the program, the access prohibition to the memory block is lifted; acquiring block information indicating the memory block for which the access prohibition has been lifted; determining whether or not to apply a patch related to the vulnerability indicated by the vulnerability information to the program on a preferential basis, based on information indicating a first function identified based on the vulnerability information among the plurality of functions, the correspondence information, and the block information; An information processing program that executes processing.

2. detecting an access to the memory block set to be inaccessible as an exception; 2. The information processing program according to claim 1, which causes the computer to execute a process.

3. identifying a first memory block in which an execution code corresponding to the first function is placed based on the correspondence information, and determining whether the access prohibition to the first memory block has been released based on the block information; determining that the patch is to be applied with priority when the access prohibition to the first memory block has been released, and determining that the patch is not to be applied with priority when the access prohibition to the first memory block has not been released; 2. The information processing program according to claim 1, which causes the computer to execute a process.

4. When the computer is stopped or the execution of the program is stopped, the block information stored in the volatile first storage device is saved in a non-volatile second storage device; When the computer is started or the execution of the program is started, the block information stored in the second storage device is read, and the block information is stored in the first storage device.

2. The information processing program according to claim 1, which causes the computer to execute a process.

5. The vulnerability information indicates a vulnerability found in a first program part, identifying the first function in which the first program part is used, based on the vulnerability information and information indicating a correspondence between each of the plurality of functions and a program part used in the function; 2. The information processing program according to claim 1, which causes the computer to execute a process.

6. The computer creating, when loading a program, correspondence information that associates each of a plurality of functions included in the program with a memory block in which an execution code corresponding to the function is allocated; Setting a plurality of memory blocks related to the execution code of the program to be inaccessible; When an access to the memory block set as being access-prohibited is detected during execution of the program, the access prohibition to the memory block is lifted; acquiring block information indicating the memory block for which the access prohibition has been lifted; determining whether or not to apply a patch related to the vulnerability indicated by the vulnerability information to the program on a preferential basis, based on information indicating a first function identified based on the vulnerability information among the plurality of functions, the correspondence information, and the block information; Information processing methods.

7. a storage unit that stores correspondence information that associates each of a plurality of functions included in a program with a memory block in which an execution code corresponding to the function is allocated; a processing unit that creates the correspondence information when the program is loaded, sets a plurality of memory blocks associated with an executable code of the program as being inaccessible, and when an access to the memory block set as being inaccessible is detected during execution of the program, lifts the access prohibition of the memory block, obtains block information indicating the memory block for which the access prohibition has been lifted, and determines whether or not a patch related to a vulnerability indicated in the vulnerability information is to be applied preferentially to the program, based on information indicating a first function among the plurality of functions that is identified based on vulnerability information, the correspondence information, and the block information; An information processing device having the above configuration.

Citation Information

Patent Citations

  • Automatic updating method for application software, information terminal, update processing method for application software and database center for application software

    JP2004355563A

  • Method for usage-controlled updating of software product

    JP2015141719A

  • Safely Updating Latent Applications to Reduce Attack Surface

    US20120054729A1

  • Online upgrading of a database environment using transparently-patched seed data tables

    US20140101645A1