WO2024214261A1 - 解析装置、解析方法及び解析プログラム - Google Patents

解析装置、解析方法及び解析プログラム Download PDF

Info

Publication number
WO2024214261A1
WO2024214261A1 PCT/JP2023/015089 JP2023015089W WO2024214261A1 WO 2024214261 A1 WO2024214261 A1 WO 2024214261A1 JP 2023015089 W JP2023015089 W JP 2023015089W WO 2024214261 A1 WO2024214261 A1 WO 2024214261A1
Authority
WO
WIPO (PCT)
Prior art keywords
virtual machine
instruction
execution trace
analysis
unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2023/015089
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
利宣 碓井
裕平 川古谷
誠 岩村
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NTT Inc
Original Assignee
Nippon Telegraph and Telephone Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nippon Telegraph and Telephone Corp filed Critical Nippon Telegraph and Telephone Corp
Priority to JP2025513732A priority Critical patent/JPWO2024214261A1/ja
Priority to PCT/JP2023/015089 priority patent/WO2024214261A1/ja
Publication of WO2024214261A1 publication Critical patent/WO2024214261A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/55—Detecting local intrusion or implementing counter-measures
    • G06F21/56—Computer malware detection or handling, e.g. anti-virus arrangements

Definitions

  • the present invention relates to an analysis device, an analysis method, and an analysis program.
  • Script analysis techniques are used for a variety of purposes, such as compiler optimization for just-in-time (JIT) compilation, software testing and debugging, fuzzing, and malware analysis.
  • Dynamic analysis is a technique that analyzes the behavior of a program by actually executing it and observing its behavior.
  • Static analysis is a technique that analyzes the functions of a program by interpreting its meaning without executing it.
  • Script execution method and analysis Scripts are executed by a script engine (also called an interpreter).
  • a script input to a script engine is generally converted into bytecode at execution time, and the bytecode is interpreted and executed by a virtual machine (VM). For this reason, it is common to statically analyze a script before execution, and to dynamically analyze the bytecode at execution time.
  • VM virtual machine
  • Bytecode is an intermediate representation converted from a script, and is composed of a set of instructions that the VM can interpret and execute (VM instructions). Each VM instruction is responsible for a small unit of operation to realize the function of the script, and the operations include, for example, arithmetic operations, logical operations, data transfer, comparison, and branching.
  • a VM instruction consists of an opcode (called a VM opcode) that indicates which operation it is, and an operand (called a VM operand) that is the target of the operation.
  • a VM instruction takes an object to be operated on as input, and outputs the result of the operation as necessary.
  • an addition VM instruction takes an augend and an addend as input, and outputs the sum.
  • Input and output for VM instructions are generally passed via data areas called virtual stacks or virtual registers.
  • references to constants and variables are made via a data structure called a symbol table.
  • VM's Instruction Set Architecture ISA
  • obfuscated malicious scripts may be analyzed.
  • Obfuscation is a technique that hampers analysis and makes the script difficult to interpret.
  • conditional branch which is realized by a set of VM instructions
  • Understanding the conditional expressions related to the branch is important for understanding the behavior, and such analysis is indispensable. Therefore, analysis of the bytecode at the VM instruction level is important.
  • Some script engines provide analysis support functions, such as debuggers and bytecode disassemblers, which can be used to perform the analysis.
  • script debuggers generally provide analysis at the expression or statement level of the script, and often do not have the functionality for analysis at the VM instruction level.
  • ISA is essential to constructing basic analysis tools such as bytecode disassemblers and debuggers. Furthermore, the results of ISA analysis are also used when constructing advanced analysis engines such as dynamic bytecode instrumentation, symbolic execution, and taint analysis.
  • the internal specifications including the ISA, are not publicly available.
  • the source code is not available, so the ISA cannot be understood without reverse engineering.
  • Non-Patent Document 1 a method has been proposed in which an execution trace is obtained for a VM whose internal specifications are unknown, and the semantics of the VM instructions are learned and obtained using a program synthesis technique that uses Monte Carlo tree search.
  • the method described in Non-Patent Document 1 makes it possible to grasp the semantics of the instructions of an unknown VM and analyze the ISA.
  • Non-Patent Document 2 a method has been proposed for inferring the data flow of an instruction from a set of inputs and outputs for an instruction for a processor with an unknown instruction set architecture.
  • the method described in Non-Patent Document 2 makes it possible to partially grasp the semantics of an unknown VM's instructions, which can be useful in elucidating the ISA.
  • Non-Patent Document 1 uses program synthesis that infers from input and output, so the target VM instructions are limited to limited operations such as arithmetic operations and logical operations, and the analysis of the ISA is also limited to a certain part.
  • Non-Patent Document 2 like Non-Patent Document 1, relies on inference from input and output, so there is a problem in that the target is limited. Also, the method described in Non-Patent Document 2 has the problem that while it clarifies the data flow, it does not clarify the operation itself.
  • Non-Patent Documents 1 and 2 are not targeted at VMs of script engines, and therefore cannot be directly applied.
  • the present invention has been made in consideration of the above, and aims to provide an analysis device, analysis method, and analysis program that can analyze the ISA of a wide variety of VMs whose specifications are unknown by analyzing the VM of a script engine and the operations performed by the VM commands and their inputs and outputs.
  • the analysis device of the present invention is characterized by having a first analysis unit that analyzes the virtual machine of the script engine based on a first execution trace obtained by executing a first test script while monitoring the binary of the script engine, and a second analysis unit that analyzes the instruction set architecture, which is the system of instructions for the virtual machine, to collect virtual machine instructions, determines the operation of the collected virtual machine instructions, and detects the input and output of the virtual machine instructions using a second test script.
  • the present invention by analyzing the VM of a script engine and the operations performed by the VM commands and their inputs and outputs, it is possible to analyze the ISA of a wide variety of VMs whose specifications are unknown.
  • FIG. 1 is a diagram illustrating an example of the configuration of a script engine.
  • FIG. 2 is a diagram showing pseudo code of a VM included in the script engine.
  • FIG. 3 is a diagram illustrating an example of a configuration of an analysis device according to an embodiment.
  • FIG. 4 is a diagram showing an example of a first test script used for detecting a virtual program counter (VPC).
  • FIG. 5 is a diagram illustrating an example of the second test script.
  • FIG. 6 is a diagram showing an example of the second test script.
  • FIG. 7 is a diagram showing an example of the second test script.
  • FIG. 8 is a diagram illustrating an example of an execution trace.
  • FIG. 9 illustrates an example of a VM execution trace.
  • FIG. 1 is a diagram illustrating an example of the configuration of a script engine.
  • FIG. 2 is a diagram showing pseudo code of a VM included in the script engine.
  • FIG. 3 is a diagram illustrating an example of a configuration of an
  • FIG. 10 is a diagram illustrating the process of the VM instruction boundary detection unit.
  • FIG. 11 is a diagram illustrating the process of the virtual program counter detection unit.
  • FIG. 12 is a diagram illustrating the process of the dispatcher detection unit.
  • FIG. 13 is a diagram illustrating the process of the VM command operation determination unit.
  • FIG. 14 is a flowchart illustrating a processing procedure of the analysis process according to the embodiment.
  • FIG. 15 is a flowchart illustrating the procedure of the first execution trace acquisition process shown in FIG.
  • FIG. 16 is a flowchart illustrating a procedure of the VM instruction boundary detection process illustrated in FIG.
  • FIG. 17 is a flowchart illustrating the processing procedure of the virtual program counter detection processing shown in FIG.
  • FIG. 15 is a flowchart illustrating the procedure of the first execution trace acquisition process shown in FIG.
  • FIG. 16 is a flowchart illustrating a procedure of the VM instruction boundary detection process illustrated in FIG.
  • FIG. 17 is a flowchar
  • FIG. 18 is a flowchart illustrating the procedure of the dispatcher detection process shown in FIG.
  • FIG. 19 is a diagram illustrating the VM execution trace acquisition process shown in FIG.
  • FIG. 20 is a flowchart illustrating the procedure of the VM command collection process illustrated in FIG.
  • FIG. 21 is a flowchart illustrating the procedure of the VM command operation determination process illustrated in FIG. 14 .
  • FIG. 22 is a flowchart illustrating the procedure of the VM command operation determination process illustrated in FIG. 14 .
  • FIG. 23 is a flowchart showing the procedure of the second execution trace acquisition process shown in FIG.
  • FIG. 24 is a flowchart illustrating a processing procedure of the VM command input/output detection processing illustrated in FIG.
  • FIG. 25 is a diagram illustrating an example of a computer that realizes the analysis device by executing a program.
  • An analysis device executes a first test script while monitoring a binary of a script engine, and acquires a branch trace and a memory access trace as a first execution trace.
  • the analysis device analyzes a virtual machine (VM) based on the first execution trace, and acquires a VM instruction boundary, a virtual program counter (VPC), and a dispatcher as architecture information.
  • VM virtual machine
  • VPC virtual program counter
  • the analysis device executes the second test script while monitoring the VPC and the dispatcher to obtain a first VM execution trace.
  • the analysis device analyzes the VM execution trace to collect VM instructions and determine the operation of the VM instructions using a predetermined algorithm.
  • the analysis device uses the second test script and the script engine binary to obtain a second execution trace that targets only the VM instructions to be determined, and analyzes the second execution trace to detect the input and output of the VM instructions and obtain information on the instruction set architecture (ISA).
  • ISA instruction set architecture
  • the analysis device analyzes the VM of a script engine, and analyzes the operations performed by the VM commands and their inputs and outputs, thereby analyzing the ISAs of a wide variety of VMs whose specifications are unknown.
  • Figure 1 is a diagram for explaining an example of the configuration of a script engine.
  • script engine 1 has a bytecode compiler 2 and a VM 3.
  • bytecode compiler 2 has a syntax analysis unit 4 and a bytecode generation unit 5.
  • VM 3 has a code cache unit 6, a fetch unit 7, a decode unit 8, and an execution unit 9. These fetch unit 7, decode unit 8, and execution unit 9 are executed repeatedly and are called an interpreter loop. Then, script engine 1 accepts the input of a script.
  • the syntax analysis unit 4 receives the script as input, and through lexical and syntactic analysis generates an Abstract Syntax Tree (AST), which it outputs to the bytecode generation unit 5.
  • the bytecode generation unit 5 receives the AST as input, converts it into bytecode, and stores it in the code cache unit 6.
  • the fetch unit 7 fetches the VM opcode from the code cache unit 6 and outputs it to the decode unit 8.
  • the VM opcode refers to the opcode portion of the VM instruction.
  • the decode unit 8 receives the VM opcode as input, interprets the VM opcode using a decoder/dispatcher, and dispatches it to the corresponding program.
  • the execution unit 9 executes the program corresponding to the VM instruction. The contents written in the script are executed by executing the VM instructions one after another through a repeated interpreter loop.
  • FIG 2 is a diagram showing pseudocode of the VM of the script engine.
  • the pseudocode first initializes the VPC (line 1).
  • the while loop is the interpreter loop (lines 2 to 7).
  • the fetch unit 7 obtains the VM opcode of the VM instruction at the position pointed to by the VPC in the code cache that holds the bytecode (line 3).
  • the decoder uses a Switch statement to interpret the VM instruction (line 4), and the dispatcher calls the instruction handler based on the VM opcode (lines 5 and on).
  • the instruction handler then performs the operation corresponding to the instruction. Input and output are performed using a virtual stack and virtual registers (line 6), and constants and variables are referenced via a symbol table (line 7).
  • Fig. 3 is a diagram illustrating an example of the configuration of the analysis device 10 according to the embodiment.
  • the analysis device 10 has an input unit 11, a control unit 12, a storage unit 13, and an output unit 14.
  • the analysis device 10 accepts inputs of a test script, a script engine binary, and a seed script.
  • the input unit 11 is composed of input devices such as a keyboard and a mouse, and accepts information input from the outside and inputs it to the control unit 12.
  • the input unit 11 also has a communication interface for sending and receiving various information to and from other devices connected via a wired connection or a network, etc., and accepts input of information sent from other devices.
  • the input unit 11 accepts input of test scripts and script engine binaries, and outputs them to the control unit 12.
  • the test script is a script that is input when dynamically analyzing the script engine to obtain an execution trace and a VM execution trace, and includes a first test script for VM analysis and a second test script for ISA analysis. Details of the test scripts will be described later.
  • the script engine binary is an executable file that constitutes the script engine.
  • the script engine binary may be composed of multiple executable files.
  • test script configuration Let us explain about test scripts.
  • a test script is a script that is input when dynamically analyzing a script engine. This test script focuses on the number of branch instruction executions and memory reads and writes, and is used to capture the difference in the behavior of the script engine that occurs when the test script is executed a different number of times. This test script is prepared before the analysis and is created manually. Creating it requires knowledge of the specifications of the target script language.
  • FIG. 4 shows an example of a first test script used to detect VPCs.
  • the first test script uses a repetitive process (line 2).
  • the first test script changes the execution conditions and generates differences by increasing or decreasing the number of repetitions (line 2) and the number of repeated statements (lines 3 to 5) in the test script.
  • the second test script is intended to execute the VM instruction to be analyzed for ISA analysis. However, it is not known at the stage of creating the second test script what operation instructions the VM has. For this reason, a second test script is created for each operation provided by the scripting language. The second test script is executed to determine the VM instruction that corresponds to this operation. Examples of operations include arithmetic operations, logical operations, comparisons, and manipulation of variables and constants.
  • FIG. 5 shows an example of a second test script.
  • the second test script shown in FIG. 5 was created to test an addition operation.
  • the second test script is created according to the following criteria. First, write the minimum expressions and statements related to the operation to be judged (addition in the example in Figure 5). Second, use a distinctive value that is useful for matching as the value to be operated on. If there are multiple values, use different values with small differences ("0x12345678" and "0x12345679" in the example in Figure 5). Third, do not operate on constants, but use one or more variables.
  • FIGS. 6 and 7 are diagrams showing other examples of the second test script.
  • the second test script in FIG. 6 was created to judge an equality comparison operation.
  • the second test script in FIG. 7 was created to judge a local variable storage operation.
  • the storage unit 13 is realized by a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk, and stores the processing program that operates the analysis device 10 and data used during execution of the processing program.
  • the storage unit 13 has an execution trace database (DB) 131, a VM execution trace DB 133, and an architecture information DB 132 that stores architecture information acquired by the virtual machine analysis unit 121 and the instruction set architecture analysis unit 122.
  • DB execution trace database
  • the execution trace DB 131 and the VM execution trace DB 133 store the execution traces and VM execution traces acquired by the first execution trace acquisition unit 1211, the second execution trace acquisition unit 1224, and the VM execution trace acquisition unit 1221, respectively.
  • the execution trace DB 131 and the VM execution trace DB 133 are managed by the analysis device 10.
  • the execution trace DB 131 and the VM execution trace DB 133 may be managed by another device (such as a server).
  • the first execution trace acquisition unit 1211, the second execution trace acquisition unit 1224, and the VM execution trace acquisition unit 1221 output the acquired execution traces and VM execution traces to a management server or the like for the execution trace DB 131 and the VM execution trace DB 133 via the communication interface of the output unit 14, and store them in the execution trace DB 131 and the VM execution trace DB 133.
  • Fig. 8 is a diagram showing an example of an execution trace. As described above, an execution trace is composed of a branch trace and a memory access trace. Fig. 8 shows an excerpt of an execution trace. The structure of an execution trace will be described below with reference to Fig. 8.
  • Trace indicates whether the log line is a branch trace or a memory access trace.
  • a branch trace log line has the format shown, for example, in lines 1 to 10 of Figure 8, and consists of three elements: type, src, and dst.
  • type indicates whether the executed branch instruction was a call instruction, a jmp instruction, or a ret instruction.
  • src indicates the address of the branch source, and dst indicates the address of the branch destination.
  • a log line of a memory access trace has the format shown, for example, in lines 11 to 13 of Figure 8, and consists of three elements: type, target, and value.
  • Type indicates whether the memory access is a read or write.
  • Target indicates the memory address that is the target of the memory access. Value stores the result of the memory access.
  • a VM execution trace is a diagram showing an example of a VM execution trace.
  • a VM execution trace is a record of a VM opcode and a VPC.
  • Fig. 9 shows a part of a VM execution trace. The configuration of a VM execution trace will be described below with reference to Fig. 9.
  • a log line of a VM execution trace is, for example, in the format shown in Figure 9, and consists of two elements: vpc and vmop (vm opcode).
  • vpc indicates the value of the VPC.
  • vmop indicates the value of the VM opcode that is virtually assigned to each pointer that points to the beginning of the VM instruction handler to be executed, obtained from the pointer cache.
  • the control unit 12 has an internal memory for storing programs that define various processing procedures and the necessary data, and executes various processes using these.
  • the control unit 12 is an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).
  • the control unit 12 has a virtual machine analysis unit 121 (first analysis unit) and an instruction set architecture analysis unit 122 (second analysis unit).
  • the virtual machine analysis unit 121 analyzes the VM of the script engine.
  • the virtual machine analysis unit 121 obtains a plurality of first execution traces by changing the conditions at the time of execution, analyzes the plurality of first execution traces using differential execution analysis, and obtains the VPC.
  • the virtual machine analysis unit 121 also analyzes the script engine binary to obtain the boundaries and dispatchers of VM instructions.
  • the virtual machine analysis unit 121 has a first execution trace acquisition unit 1211 (first acquisition unit), a VM instruction boundary detection unit 1212 (first detection unit), a virtual program counter detection unit 1213 (second detection unit), and a dispatcher detection unit 1214 (third detection unit).
  • the first execution trace acquisition unit 1211 receives the first test script and the script engine binary as input.
  • the first execution trace acquisition unit 1211 executes the first test script while monitoring the execution of the script engine binary, thereby acquiring the first execution trace.
  • An execution trace is composed of a branch trace and a memory access trace.
  • a branch trace records the type of branch instruction at the time of execution, the branch source address, and the branch destination address.
  • a memory access trace records the type of memory operation at the time of execution (read/write), and the memory address and value of the operation target. It is known that branch traces and memory access traces can be obtained by hooking a memory operation instruction, inserting code for log output, and executing it.
  • the first execution trace obtained by the first execution trace acquisition unit 1211 is stored in the execution trace DB 131.
  • the VM instruction boundary detection unit 1212 clusters the first execution trace to detect the boundaries of each VM instruction.
  • the VM instruction boundary detection unit 1212 clusters the first execution trace to detect clusters with a threshold or more of execution counts as VM instructions. In clustering, consecutive code regions that are executed multiple times are detected. For example, executed instructions that are close in distance to each other in the code may be grouped together, common subsequences of executed code blocks may be searched for, or other methods may be used.
  • the analysis device 10 detects the start and end points of consecutive instruction sequences that make up the detected VM instruction as boundaries.
  • the VM instruction boundaries detected here are used in VPC detection and dispatcher detection.
  • the virtual program counter detection unit 1213 extracts and analyzes the first execution trace for the first test script stored in the execution trace DB 131, and detects the VPC.
  • the virtual program counter detection unit 1213 analyzes the multiple first execution traces using differential execution analysis focusing on the number of memory reads and the boundaries of each VM instruction detected by the VM instruction boundary detection unit 1212, and detects the VPC.
  • the virtual program counter detection unit 1213 uses the fact that a read into the memory that holds the VPC always occurs after the execution of each VM instruction, and detects the VPC by discovering the destination of this read.
  • the virtual program counter detection unit 1213 uses differential execution analysis focusing on the number of memory reads to detect VPCs.
  • the virtual program counter detection unit 1213 compares the first execution traces of multiple test scripts acquired using the first test script, and finds memories for which the number of memory reads changes in proportion to both the increase or decrease in the number of repetitions and the number of repeated statements.
  • the virtual program counter detection unit 1213 then refers to the boundaries of each VM instruction detected by the VM instruction boundary detection unit 1212, and narrows down the memory values that have been read to those that always point to the start point of the VM instruction.
  • the virtual program counter detection unit 1213 detects this memory as a VPC.
  • the dispatcher detection unit 1214 extracts each VM instruction portion from the script engine binary based on the boundaries of the VM instructions detected by the VM instruction boundary detection unit 1212, and detects the portions with high similarity between each VM instruction as dispatchers.
  • the dispatcher is realized by referencing the pointer cache and jumping to the pointer of the next VM instruction handler.
  • Dispatchers are placed in a distributed manner at the rear of each VM instruction handler, and the code therein is generally highly identical.
  • the analysis device detects dispatchers using a specified method by searching for code with high similarity that exists at the rear of such VM instruction handlers. To detect the portions with high similarity, for example, a sequence alignment algorithm or other methods may be used.
  • the instruction set architecture analysis unit 122 analyzes the instruction set architecture, which is the system of VM instructions.
  • the instruction set architecture analysis unit 122 collects VM instructions and judges the operation of the collected VM instructions.
  • the instruction set architecture analysis unit 122 uses a second test script to obtain a memory access trace that targets only the VM instruction to be judged as a second execution trace, and detects the input and output of the VM instruction by analyzing the second execution trace.
  • the instruction set architecture analysis unit 122 has a VM execution trace acquisition unit 1221 (second acquisition unit), a VM instruction collection unit 1222 (first collection unit), a VM instruction operation determination unit 1223 (first determination unit), a second execution trace acquisition unit 1224 (third acquisition unit), and a VM instruction input/output detection unit 1225 (fourth detection unit).
  • the VM execution trace acquisition unit 1221 receives as input a second test script (described later) that uses values characteristic of the operation target and a script engine binary.
  • the VM execution trace acquisition unit 1221 acquires a VM execution trace by monitoring the VPC and the pointer of the VM instruction handler dispatched by the dispatcher.
  • the VM execution trace acquisition unit 1221 acquires a VM execution trace, which is an execution trace executed on the VM, by executing the second test script while monitoring the execution of the script engine binary.
  • the VM execution trace acquisition unit 1221 executes a large number of second test scripts to acquire a VM execution trace.
  • the VM execution trace acquisition unit 1221 links a pointer to the VM instruction with the VM instruction, and virtually assigns a VM opcode as an identifier to each.
  • a VM execution trace is an execution trace executed in a VM, in which a VM opcode is virtually assigned as an identifier, and in which a pointer to the executed VM handler and a VPC are recorded.
  • a VM execution trace is a record of a pointer to an executed VM instruction handler and a VPC.
  • a VM execution trace is composed of a VPC and a VM opcode for each executed VM instruction.
  • the recording of a VPC can be achieved by monitoring the memory of the VPC detected by the virtual program counter detection unit 1213.
  • a VM opcode is an identifier virtually assigned to each of a pointer to a VM instruction and a VM instruction that are linked together.
  • the VM execution trace acquired by the VM execution trace acquisition unit 1221 is stored in the VM execution trace DB 133.
  • the VM instruction collection unit 1222 receives the VPC and dispatcher as input, executes the second test script while monitoring the VPC and dispatcher, and obtains a VM execution trace.
  • the VM instruction collection unit 1222 collects VM instructions from the VM execution trace.
  • the VM instruction operation determination unit 1223 uses a predetermined algorithm to determine the operation of a VM instruction.
  • the VM instruction operation determination unit 1223 analyzes the VM execution trace acquired using a test script (second test script) for a specific operation, and determines the VM opcode that carries out that operation.
  • the VM opcode indicates which operation the VM instruction is.
  • the VM command operation determination unit 1223 creates a list of unknown VM opcodes for each VM execution trace.
  • the VM command operation determination unit 1223 determines a priority based on the number of unknown VM opcodes in the list, and determines which VM opcode is responsible for the operation being determined based on this priority and the number of unknown VM opcodes. For example, the VM command operation determination unit 1223 makes a determination based on the priority being the inverse of the number of unknown VM opcodes in the list.
  • the second execution trace acquisition unit 1224 uses the second test script to acquire a second execution trace that targets only the VM instruction to be judged.
  • the second execution trace acquisition unit 1224 executes the second test script while monitoring the execution of the script engine binary, thereby acquiring a new memory access trace as the second execution trace.
  • the VM instruction I/O detection unit 1225 analyzes the second execution trace to detect the input and output of VM instructions. It obtains information on the instruction set architecture (ISA). Using the memory access trace, which is the second execution trace, the VM instruction I/O detection unit 1225 compares the characteristic values used as the operation target of the second test script, and detects the code that reads and writes the matched memory as the location where the input and output appear. The VM instruction I/O detection unit 1225 outputs the detected input and output of VM instructions from the output unit 14 (described below) as information on the instruction set architecture (ISA).
  • ISA instruction set architecture
  • the output unit 14 is, for example, a liquid crystal display or a printer, and outputs various information including information related to the analysis device 10.
  • the output unit 14 may also be an interface that handles the input and output of various data between an external device and the output unit 14, and may output various information to the external device.
  • the VM instruction boundary detection unit 1212 detects the boundaries of each VM instruction. At this time, the VM instruction boundary detection unit 1212 detects VM instructions and their boundaries for threaded code type VMs that do not have an interpreter loop and therefore have difficulty grasping the boundaries of VM instructions. Specifically, the VM instruction boundary detection unit 1212 extracts a first execution trace from the execution trace DB 131. Then, as shown in FIG. 10, the VM instruction boundary detection unit 1212 clusters the first execution trace using a predetermined method, and detects clusters whose execution count is equal to or greater than a threshold as VM instructions (e.g., VM instruction handlers 1 to 3). The VM instruction boundary detection unit 1212 detects the start and end points of the consecutive instruction sequence that constitutes the VM instruction as boundaries.
  • a threshold as VM instructions
  • the virtual program counter detection unit 1213 detects the VPC and the pointer cache. The detection of the virtual program counter is realized by analyzing the log of the memory access trace of the acquired first execution trace. The virtual program counter detection unit 1213 uses differential execution analysis focusing on the number of times memory is read. FIG. 11 is a diagram for explaining the processing of the virtual program counter detection unit 1213.
  • the virtual program counter detection unit 1213 extracts one execution trace by the first test script from the execution trace DB 131.
  • the number of times the VPC is read is proportional to the number of repetitions in the test script and the number of statements in the repetitive process. If the number of repetitions is N and the number of repeated statements is M, then approximately MN VPC reads will occur. For this reason, the virtual program counter detection unit 1213 extracts memory that has increased by 4MN and 9MN in the execution trace for the first test script in which N and M have been increased to 2N and 2M, respectively, and 3N and 3M. Specifically, as shown in FIG. 11, the virtual program counter detection unit 1213 extracts memory areas that have a monotonically increasing read/write for each VM instruction execution ((1) in FIG. 11).
  • the virtual program counter detection unit 1213 detects as a VPC a memory value that has been read and that always points to the start point of a VM instruction. Specifically, the virtual program counter detection unit 1213 compares the VPC's pointing destination with the address of the VM instruction handler, and narrows it down to matching memory areas ((2) in FIG. 11).
  • the dispatcher detection unit 1214 detects a dispatcher by analyzing the binary of the script engine using a predetermined method.
  • FIG. 12 is a diagram for explaining the process of the dispatcher detection unit 1214.
  • the dispatcher detection unit 1214 detects dispatchers. Based on the boundaries of VM instructions detected by the VM instruction boundary detection unit 1212, the dispatcher detection unit 1214 extracts each VM instruction portion from the script engine binary. Then, based on the assumption that the similarity of dispatcher code is high (FIG. 12 (1)), the dispatcher detection unit 1214 calculates the similarity between the codes of each VM instruction and detects the portion with high similarity between all VM instructions as the dispatcher. The dispatcher detection unit 1214 can detect the code that is commonly executed in the latter half of the VM instructions as the dispatcher (FIG. 12 (1)).
  • the second test script only performs a single operation to be judged, so it is expected that only the VM instruction responsible for that operation will be executed. In this case, it can be easily judged because only that one VM opcode appears in the VM execution trace.
  • multiple VM instructions may be executed even for a test script with a single operation.
  • VM instructions are also executed that handle reading constants and variables, storing them in variables, etc. This is because there is a dependency between the VM instructions that make up the addition formula, making it more difficult to judge.
  • the VM command operation determination unit 1223 performs the determination using an algorithm that prioritizes clarifying commands that are easier to determine. Even if there is a dependency between the VM commands described above, the determination is possible if the VM command on which the command is dependent is identified first, so the VM command operation determination unit 1223 gradually advances the determination while resolving the dependency.
  • Fig. 13 is a diagram for explaining the processing of the VM command operation determination unit 1223.
  • the VM command operation determination unit 1223 analyzes the VM execution trace acquired by the second test script for a specific operation and determines the VM opcode that performs that operation.
  • the VM command operation determination unit 1223 receives as input the VM execution traces for multiple operations (for example, operations 1 to 5 illustrated in FIG. 13) acquired using multiple second test scripts, and outputs the VM opcodes that perform those operations as the determination results, using the algorithm described below.
  • the VM instruction operation determination unit 1223 creates a list of unknown VM opcodes for each VM execution trace (see FIG. 13). Then, the VM instruction operation determination unit 1223 sets the priority to the inverse of the number of unknown VM opcodes in the list, and makes a determination by repeating the following first to third steps.
  • the VM command operation determination unit 1223 performs a first procedure to determine that this VM opcode is responsible for the operation to be determined.
  • the VM command operation determination unit 1223 performs a second procedure in which it detects a unique VM opcode from the difference with other lists and determines that the unknown VM opcode is responsible for the operation to be determined.
  • the VM command operation determination unit 1223 performs a third procedure, which reflects the determination results from the first and second procedures to all lists and updates the priorities.
  • the VM instruction operation determination unit 1223 determines that this unknown opcode is the VM instruction responsible for operation 1 ((1) in FIG. 13). Then, the VM instruction operation determination unit 1223 reflects the determination result in all lists and updates the priority ((2) in FIG. 13). As a result, all of the opcodes "VMOP1_Unknown" in the list are updated to the opcode "VMOP1_Known”.
  • the VM instruction operation determination unit 1223 determines that this opcode is the VM instruction responsible for operation 2 ((3) in FIG. 13). The determination result is then reflected in all lists, and the priorities are updated ((4) in FIG. 13). As a result, all of the opcodes "VMOP2_Unknown" in the lists are updated to the opcode "VMOP2_Known”.
  • the VM command operation determination unit 1223 detects unknown VM opcodes specific to each list from the differences with other lists.
  • the VM command operation determination unit 1223 detects the VM opcode "VMOP3_Unknown” that is not present in operations 4 and 5, and determines that this VM opcode "VMOP3_Unknown” is the VM command responsible for operation 3 ((5) in FIG. 13).
  • the VM command operation determination unit 1223 detects the VM opcode "VMOP6_Unknown” that is not present in operations 3 and 5, and determines that this VM opcode "VMOP6_Unknown” is the VM command responsible for operation 4 ((5) in FIG. 13).
  • the VM instruction operation determination unit 1223 detects the VM opcode "VMOP7_Unknown” that is not present in operations 3 and 4, and determines that this VM opcode "VMOP7_Unknown” is the VM instruction responsible for operation 5 ((5) in FIG. 13).
  • the VM instruction input/output detection unit 1225 analyzes the memory access trace (second execution trace) acquired by the second execution trace acquisition unit 1224 using the second test script, and detects input/output of a VM instruction.
  • VM instruction operands are generally passed on a virtual stack or virtual registers, and variables and constants are managed in a symbol table.
  • the subscript of a record in the symbol table is passed to the VM instruction operand, and the actual value does not appear.
  • the VM instruction I/O detection unit 1225 identifies code that accesses the actual value by comparing values using memory access traces.
  • the VM instruction input/output detection unit 1225 determines during memory access tracing that the period from the dispatch of a VM instruction to the next dispatch is memory access due to that VM instruction.
  • the VM command I/O detection unit 1225 compares the read/write value with the value used for the operation target in the second test script. This comparison is performed by using a value that is characteristic of the operation target in the second test script.
  • the VM instruction I/O detection unit 1225 detects the matched code that reads and writes memory as a location where VM instruction I/O appears.
  • the VM instruction I/O detection unit 1225 obtains VM instruction I/O by monitoring the reads and writes at this location.
  • Fig. 14 is a flowchart showing the procedure of the analysis process according to the embodiment.
  • the input unit 11 receives a test script and a script engine binary as input (step S1).
  • the test script includes a first test script and a second test script.
  • the first execution trace acquisition unit 1211 performs a first execution trace acquisition process in which the first test script is executed while monitoring the binary of the script engine to acquire a branch trace and a memory access trace (step S2).
  • the VM instruction boundary detection unit 1212 detects VM instructions and performs VM instruction boundary detection processing to detect VM instruction boundaries (step S3).
  • the virtual program counter detection unit 1213 extracts and analyzes the execution trace for the first test script stored in the execution trace DB 131, and performs virtual program counter detection processing to discover the VPC (step S4).
  • the dispatcher detection unit 1214 performs dispatcher detection processing to extract each VM command portion from the script engine binary and detect the portion with high similarity between each VM command as a dispatcher (step S5).
  • the VM execution trace acquisition unit 1221 receives the test script and the script engine binary as input, and executes the test script while monitoring the execution of the script engine binary, thereby performing a VM execution trace acquisition process to acquire a VM execution trace (step S6).
  • the VM instruction collection unit 1222 performs a VM instruction collection process to collect VM instructions from the VM execution trace (step S7).
  • the VM command operation determination unit 1223 performs a VM command operation determination process that determines the operation of the VM command using a predetermined algorithm (step S8).
  • the second execution trace acquisition unit 1224 performs a second execution trace acquisition process using the second test script to acquire a second execution trace that targets only the VM instruction to be judged (step S9).
  • the VM instruction input/output detection unit 1225 analyzes the second execution trace and performs a VM instruction input/output detection process to detect the input/output of the VM instruction (step S10).
  • the output unit 14 outputs the operation and input/output of the VM instruction detected in steps S8 and S10 (step S11).
  • Fig. 15 is a flowchart showing the processing procedure of the first execution trace acquisition process shown in Fig. 14.
  • the first execution trace acquisition unit 1211 receives the first test script and the script engine binary as input (step S21). Then, the first execution trace acquisition unit 1211 hooks the received script engine to acquire a branch trace (step S22). The first execution trace acquisition unit 1211 also hooks the received script engine to acquire a memory access trace (step S23).
  • the first execution trace acquisition unit 1211 inputs the first test script received in this state into the script engine and executes it (step S24), and stores the first execution trace acquired thereby in the execution trace DB 131 (step S25).
  • the first execution trace acquisition unit 1211 determines whether or not all of the input first test scripts have been executed (step S26). If all of the input first test scripts have been executed (step S26: Yes), the first execution trace acquisition unit 1211 ends the process. On the other hand, if all of the input first test scripts have not been executed (step S26: No), the first execution trace acquisition unit 1211 returns to the execution of the first test script in step S24 and continues the process.
  • Fig. 16 is a flowchart showing the processing procedure of the VM instruction boundary detection process shown in Fig. 14.
  • the VM instruction boundary detection unit 1212 extracts a first execution trace from the execution trace DB 131 (step S31).
  • the VM instruction boundary detection unit 1212 clusters the first execution trace using a predetermined method (step S32). Any method may be used for the clustering.
  • the VM instruction boundary detection unit 1212 detects clusters whose execution count is equal to or exceeds a threshold as VM instructions (step S33). Then, the VM instruction boundary detection unit 1212 determines the start and end points of the continuous instruction sequence that constitutes the VM instruction as boundaries (step S34). The VM instruction boundary detection unit 1212 outputs the VM instruction boundary as a return value (step S35), and ends the VM instruction boundary detection process.
  • Fig. 17 is a flowchart showing the processing procedure of the virtual program counter detection process shown in Fig. 14.
  • the virtual program counter detection unit 1213 extracts one first execution trace by the first test script from the execution trace DB 131 (step S41). Next, the virtual program counter detection unit 1213 focuses on memory access traces in the first execution trace, and counts up the number of reads for each memory read destination (step S42).
  • the virtual program counter detection unit 1213 receives as input the first test script used to obtain the first execution trace (step S43), and analyzes the first test script to obtain the number of repetitions and the number of repeated statements (step S44).
  • the virtual program counter detection unit 1213 extracts another first execution trace by the first test script, which has a different number of repetitions and number of repeated statements, from the execution trace DB 131 (step S45). Then, the virtual program counter detection unit 1213 focuses on the memory access trace and counts the number of reads for each memory read destination (step S46). The virtual program counter detection unit 1213 also receives as input the first test script used to obtain the first execution trace (step S47), and analyzes the first test script to obtain the number of repetitions and the number of repeated statements (step S48).
  • the virtual program counter detection unit 1213 narrows down the memory read destinations to only those whose read counts change in proportion to the number of repetitions or the increase or decrease in the number of repeated statements (step S49). Furthermore, the virtual program counter detection unit 1213 narrows down the memory read destinations narrowed down in step S49 to those whose read memory values always point to the start point of the VM instruction (step S50).
  • the virtual program counter detection unit 1213 determines whether the memory read destinations have been narrowed down to only one (step S51). If the virtual program counter detection unit 1213 has not narrowed down the memory read destinations to only one (step S51: No), the process returns to step S45, where the virtual program counter detection unit 1213 extracts the next first execution trace and continues processing. On the other hand, if the virtual program counter detection unit 1213 has narrowed down the memory read destinations to only one (step S51: Yes), the virtual program counter detection unit 1213 stores the narrowed down memory read destination in the architecture information DB 132 as a virtual program counter (step S52), and ends processing.
  • Fig. 18 is a flowchart showing the processing procedure of the dispatcher detection process shown in Fig. 14.
  • the dispatcher detection unit 1214 receives the script engine binary as input (step S61).
  • the dispatcher detection unit 1214 receives the boundaries of VM commands from the VM command boundary detection unit 1212 (step S62).
  • the dispatcher detection unit 1214 extracts each VM instruction portion from the script engine binary based on the boundaries of the VM instructions received from the VM instruction boundary detection unit 1212 (step S63).
  • the dispatcher detection unit 1214 calculates the similarity between the codes of each VM instruction using a predetermined method (step S64). Any method for calculating the similarity may be used as long as it is a method that can calculate the similarity between codes.
  • the dispatcher detection unit 1214 extracts the part with high similarity among all VM commands based on the similarity calculated in step S64 (step S65). The dispatcher detection unit 1214 then determines whether it is the end part of the VM command (step S66).
  • step S66: No If it is not the end of the VM command (step S66: No), the dispatcher detection unit 1214 returns to step S65 and continues processing. If it is the end of the VM command (step S66: Yes), the dispatcher detection unit 1214 outputs the extracted part as a dispatcher (step S67) and ends processing.
  • Fig. 19 is a flowchart showing the procedure of the VM execution trace acquisition process shown in Fig. 14.
  • the VM execution trace acquisition unit 1221 receives the second test script and the script engine binary as input (step S71). Then, the VM execution trace acquisition unit 1221 applies a hook to the received script engine to record the VPC and VM opcode (step S72).
  • the VM execution trace acquisition unit 1221 inputs the second test script received in this state into the script engine and executes it (step S73), and stores the VM execution trace acquired thereby in the VM execution trace DB 133 (step S74).
  • the VM execution trace acquisition unit 1221 determines whether or not all of the input second test scripts have been executed (step S75). If all of the input second test scripts have been executed (step S75: Yes), the VM execution trace acquisition unit 1221 ends the process. If all of the input second test scripts have not been executed (step S75: No), the VM execution trace acquisition unit 1221 returns to the execution of the second test script in step S73 and continues the process.
  • Fig. 20 is a flowchart showing the procedure of the VM command collection process shown in Fig. 14.
  • the VM command collection unit 1222 receives the VPC and dispatcher as input (step S81) and acquires various scripts from the Internet (step S82). The VM command collection unit 1222 executes the scripts while monitoring the VPC and dispatcher, and acquires a VM execution trace (step S83).
  • the VM instruction collection unit 1222 acquires VM instructions from the VM execution trace (step S84) and adds them to a list of VM instructions (step S85). If the VM instruction collection unit 1222 finds a VM instruction that is not in the list (step S86: No), it returns to step S82. If the VM instruction collection unit 1222 finds no VM instructions that are not in the list (step S86: Yes), it returns the list of VM instructions (step S87) and ends the VM instruction collection process.
  • FIG. 21 and Fig. 22 are flowcharts showing the processing procedure of the VM command operation determination process shown in Fig. 14.
  • the VM command operation determination unit 1223 receives VM execution traces as input (step S91) and creates a list of VM opcodes for each VM execution trace, along with known and unknown information (step S92).
  • the VM command operation determination unit 1223 calculates the inverse of the number of unknown VM opcodes in the list as the priority (step S93).
  • the VM command operation determination unit 1223 extracts the list with the highest priority (step S94). The VM command operation determination unit 1223 determines whether the number of unknown VM opcodes is 1 (step S95).
  • step S95 If the number of unknown VM opcodes is 1 (step S95: Yes), the VM command operation determination unit 1223 determines that the unknown VM opcode is responsible for the operation to be determined (step S96).
  • step S95 If the number of unknown VM opcodes is not 1 (step S95: No), the VM command operation determination unit 1223 determines whether the number of unknown VM opcodes is greater than 1 (step S97).
  • step S97 If the number of unknown VM opcodes is less than 1 (step S97: No), the VM instruction operation determination unit 1223 determines that the operation to be determined does not exist in the VM instruction (step S98).
  • step S97 If the number of unknown VM opcodes is greater than 1 (step S97: Yes), the VM command operation determination unit 1223 calculates the difference with other lists (step S99).
  • the VM command operation determination unit 1223 detects an unknown VM opcode specific to the list and determines that the detected VM opcode is responsible for the operation to be determined (step S100).
  • the VM command operation determination unit 1223 reflects the newly determined VM opcodes in all lists (step S101).
  • the VM command operation determination unit 1223 recalculates the priorities and updates the lists (step S102).
  • the VM command operation determination unit 1223 determines whether all lists have been processed (step S103).
  • step S104 retrieves the next list (step S104), returns to step S95, and processes the next list.
  • step S103 If all the lists have been processed (step S103: Yes), the VM command operation determination unit 1223 outputs the VM opcode and its operation as a result of the determination (step S105).
  • Fig. 23 is a flowchart showing the processing procedure of the second execution trace acquisition process shown in Fig. 14.
  • the second execution trace acquisition unit 1224 receives the second test script and the script engine binary as input (step S111). Next, the second execution trace acquisition unit 1224 receives the VM instruction for which the execution trace is to be acquired as input (step S112).
  • the second execution trace acquisition unit 1224 hooks the dispatcher of the script engine to observe the VM opcode (step S113).
  • the second execution trace acquisition unit 1224 hooks the script engine to acquire a memory access trace (step S114).
  • the second execution trace acquisition unit 1224 extracts one second test script (step S115) and inputs the second test script into the script engine for execution (step S116).
  • the second execution trace acquisition unit 1224 acquires a memory access trace from the observation of the VM opcode, limited to when the target VM instruction is being executed (step S117), and stores the acquired memory access trace as a second execution trace in the execution trace DB 131 (step S118).
  • the second execution trace acquisition unit 1224 determines whether or not all of the input second test scripts have been executed (step S119).
  • step S119: No the second execution trace acquisition unit 1224 receives the next second test script (step S120) and returns to step S115 to continue processing. If all of the input second test scripts have been executed (step S119: Yes), the second execution trace acquisition unit 1224 ends the second execution trace acquisition process.
  • Fig. 24 is a flowchart showing the processing procedure of the VM command input/output detection process shown in Fig. 14.
  • the VM command input/output detection unit 1225 receives the second test script and the second execution trace as input (step S131).
  • the VM command I/O detection unit 1225 extracts all characteristic values used in the second test script (step S132). In the example of Figure 5, these are "0x12345678" and "0x12345679".
  • the VM instruction I/O detection unit 1225 extracts one value (step S133).
  • the VM instruction I/O detection unit 1225 searches for a memory read value in the second execution trace that can be compared with the extracted value (step S134).
  • the VM instruction I/O detection unit 1225 extracts the address of the found memory read code from the second execution trace (step S135), and extracts this code as code that accesses an input value (step S136).
  • the VM command input/output detection unit 1225 determines whether all values have been processed (step S137).
  • step S137 If not all values have been processed (step S137: No), the VM command I/O detection unit 1225 extracts the next value (step S138), returns to step S134, and continues processing.
  • step S137 If all values have been processed (step S137: Yes), the VM command I/O detection unit 1225 calculates the value of the operation result of the second test script (step S139). In the example of FIG. 5, this is "0x2468acf1", which is the sum of "0x12345678" and "0x12345679".
  • the VM command I/O detection unit 1225 searches for a memory write value in the second execution trace that can be compared with the calculated value (step S140).
  • the VM instruction I/O detection unit 1225 extracts the address of the found memory write code from the second execution trace (step S141), and extracts this code as code that accesses an output value (step S142).
  • the VM command input/output detection unit 1225 outputs the input/output code extracted in steps S136 and S142 (step S143).
  • the analysis device 10 executes the first test script while monitoring the binary of the script engine, and acquires a memory access trace as a first execution trace.
  • the analysis device 10 analyzes the VM of the script engine based on the first execution trace.
  • the analysis device 10 acquires architecture information of the VPC and the dispatcher.
  • the analysis device 10 analyzes the instruction set architecture, which is the system of instructions for the virtual machine, collects VM instructions, determines the operation of the collected VM instructions, and detects the input and output of the VM instructions using a second test script, thereby obtaining ISA information on the operation of the VM instructions and the input and output of the VM instructions.
  • the instruction set architecture which is the system of instructions for the virtual machine
  • the analysis device 10 executes the second test script while monitoring the VPC and the dispatcher to obtain a VM execution trace.
  • the analysis device 10 analyzes this VM execution trace to collect VM instructions and create a list of unknown VM opcodes among the VM opcodes, and uses this list and a predetermined algorithm to determine the operation of the VM instructions.
  • the analysis device 10 uses the second test script to obtain a memory access trace that targets only the VM instruction to be determined as a second execution trace, and analyzes the second execution trace to detect the input and output of the VM instructions.
  • the analysis device 10 can detect various architectural information by analyzing the execution trace and VM execution trace obtained, even for script engines whose VM internal specifications are unknown, and can determine the ISA without requiring manual reverse engineering.
  • the analysis device 10 can automatically determine the ISA for a variety of script engines as long as a test script is prepared, making it possible to analyze the ISA of a wide variety of VMs whose specifications are unknown, without the need for individual design or execution.
  • the analysis device 10 can analyze the script engine and determine the ISA, thereby enabling analysis at the VM command level for script engines of a wide variety of script languages.
  • the analysis device 10 is useful for clarifying the ISA of VMs in a wide variety of script engines, and is suitable for performing analysis even on scripts that are difficult to analyze at the VM instruction level due to the absence of an analysis support function or an unknown VM ISA.
  • the analysis device 10 can be used to create bytecode disassemblers, debuggers, and tracers, and can also be used to realize engines such as dynamic bytecode instrumentation, symbolic execution, and taint analysis.
  • these tools can be used for a variety of purposes, such as software testing and debugging, fuzzing, and malware analysis.
  • Each component of the analysis device 10 shown in Fig. 3 is a functional concept, and does not necessarily have to be physically configured as shown in the figure.
  • the specific form of distribution and integration of the functions of the analysis device 10 is not limited to that shown in the figure, and all or part of it can be functionally or physically distributed or integrated in any unit depending on various loads, usage conditions, etc.
  • each process performed by the analysis device 10 may be realized, in whole or in part, by a CPU and a program that is analyzed and executed by the CPU. Furthermore, each process performed by the analysis device 10 may be realized as hardware using wired logic.
  • [program] 25 is a diagram showing an example of a computer in which analysis device 10 is realized by executing a program.
  • Computer 1000 has, for example, memory 1010 and CPU 1020.
  • Computer 1000 also has hard disk drive interface 1030, disk drive interface 1040, serial port interface 1050, video adapter 1060, and network interface 1070. Each of these components is connected by bus 1080.
  • the memory 1010 includes a ROM 1011 and a RAM 1012.
  • the ROM 1011 stores a boot program such as a BIOS (Basic Input Output System).
  • BIOS Basic Input Output System
  • the hard disk drive interface 1030 is connected to a hard disk drive 1090.
  • the disk drive interface 1040 is connected to a disk drive 1100.
  • a removable storage medium such as a magnetic disk or optical disk is inserted into the disk drive 1100.
  • the serial port interface 1050 is connected to a mouse 1110 and a keyboard 1120, for example.
  • the video adapter 1060 is connected to a display 1130, for example.
  • the hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, the program that defines each process of the analysis device 10 is implemented as a program module 1093 in which code executable by the computer 1000 is written.
  • the program module 1093 is stored, for example, in the hard disk drive 1090.
  • a program module 1093 for executing processes similar to the functional configuration of the analysis device 10 is stored in the hard disk drive 1090.
  • the hard disk drive 1090 may be replaced by an SSD (Solid State Drive).
  • the setting data used in the processing of the above-mentioned embodiment is stored as program data 1094, for example, in memory 1010 or hard disk drive 1090.
  • the CPU 1020 reads the program module 1093 or program data 1094 stored in memory 1010 or hard disk drive 1090 into RAM 1012 as necessary and executes it.
  • the program module 1093 and program data 1094 may not necessarily be stored in the hard disk drive 1090, but may be stored in a removable storage medium, for example, and read by the CPU 1020 via the disk drive 1100 or the like.
  • the program module 1093 and program data 1094 may be stored in another computer connected via a network (such as a LAN (Local Area Network), WAN (Wide Area Network)).
  • the program module 1093 and program data 1094 may then be read by the CPU 1020 from the other computer via the network interface 1070.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • General Health & Medical Sciences (AREA)
  • Virology (AREA)
  • Health & Medical Sciences (AREA)
  • Debugging And Monitoring (AREA)
PCT/JP2023/015089 2023-04-13 2023-04-13 解析装置、解析方法及び解析プログラム Ceased WO2024214261A1 (ja)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2025513732A JPWO2024214261A1 (https=) 2023-04-13 2023-04-13
PCT/JP2023/015089 WO2024214261A1 (ja) 2023-04-13 2023-04-13 解析装置、解析方法及び解析プログラム

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/015089 WO2024214261A1 (ja) 2023-04-13 2023-04-13 解析装置、解析方法及び解析プログラム

Publications (1)

Publication Number Publication Date
WO2024214261A1 true WO2024214261A1 (ja) 2024-10-17

Family

ID=93059167

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/015089 Ceased WO2024214261A1 (ja) 2023-04-13 2023-04-13 解析装置、解析方法及び解析プログラム

Country Status (2)

Country Link
JP (1) JPWO2024214261A1 (https=)
WO (1) WO2024214261A1 (https=)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022079840A1 (ja) * 2020-10-14 2022-04-21 日本電信電話株式会社 解析機能付与装置、解析機能付与方法および解析機能付与プログラム
WO2022180702A1 (ja) * 2021-02-24 2022-09-01 日本電信電話株式会社 解析機能付与装置、解析機能付与プログラム及び解析機能付与方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022079840A1 (ja) * 2020-10-14 2022-04-21 日本電信電話株式会社 解析機能付与装置、解析機能付与方法および解析機能付与プログラム
WO2022180702A1 (ja) * 2021-02-24 2022-09-01 日本電信電話株式会社 解析機能付与装置、解析機能付与プログラム及び解析機能付与方法

Also Published As

Publication number Publication date
JPWO2024214261A1 (https=) 2024-10-17

Similar Documents

Publication Publication Date Title
JP7517585B2 (ja) 解析機能付与装置、解析機能付与プログラム及び解析機能付与方法
Hu et al. Binary code clone detection across architectures and compiling configurations
CN111125716B (zh) 一种以太坊智能合约漏洞检测方法及装置
Cesare et al. Classification of malware using structured control flow
Hu et al. Cross-architecture binary semantics understanding via similar code comparison
CN112733137A (zh) 一种面向漏洞检测的二进制代码相似性分析方法
US20090328002A1 (en) Analysis and Detection of Responsiveness Bugs
CN106407809A (zh) 一种Linux平台恶意软件检测方法
KR101583932B1 (ko) 프로그램의 시그니처를 생성하는 시그니처 생성 장치 및 방법, 시그니처의 악성 코드를 검출하는 악성 코드 검출 장치 및 방법
JP7077909B2 (ja) デッドコード解析プログラム、デッドコード解析方法及びデッドコード解析装置
Gu et al. Deepprof: Performance analysis for deep learning applications via mining gpu execution patterns
JP7568131B2 (ja) 解析機能付与方法、解析機能付与装置及び解析機能付与プログラム
Saumya et al. Xstressor: Automatic generation of large-scale worst-case test inputs by inferring path conditions
KR101583133B1 (ko) 스택 기반 소프트웨어 유사도 평가 방법 및 장치
JP7838662B2 (ja) 脆弱性発見装置、脆弱性発見方法及び脆弱性発見プログラム
WO2024214261A1 (ja) 解析装置、解析方法及び解析プログラム
WO2024214263A1 (ja) 解析機能付与装置、解析機能付与方法及び解析機能付与プログラム
JP7568128B2 (ja) 解析機能付与方法、解析機能付与装置及び解析機能付与プログラム
JP7568129B2 (ja) 解析機能付与方法、解析機能付与装置及び解析機能付与プログラム
Alrabaee et al. Compiler provenance attribution
WO2024214262A1 (ja) 解析機能付与装置、解析機能付与方法及び解析機能付与プログラム
WO2024214260A1 (ja) 解析装置、解析方法及び解析プログラム
WO2024214264A1 (ja) 解析装置、解析方法及び解析プログラム
JP7800716B2 (ja) 解析機能付与装置、解析機能付与方法および解析機能付与プログラム
Liu et al. Automatic Software Vulnerability Detection in Binary Code

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23933037

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2025513732

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2025513732

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23933037

Country of ref document: EP

Kind code of ref document: A1