Executable File Vulnerability Correction Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional techniques require deep knowledge and experience to analyze software vulnerabilities, as changes in the compiler and link environment can complicate identifying corrected vulnerability parts in executable files, making it difficult for analysts with insufficient knowledge to perform effective analysis.
Innovation Solution
A device that includes units for extracting differences in executable files before and after vulnerability correction, calculating features of these differences, and determining similarity between them, allowing for automated specification of vulnerability correction parts without relying on extensive analyst expertise.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If binary comparison tools are used to find and compare semblance functions between executable files, then vulnerability correction parts can be identified, but deep knowledge and experience of analysts are required to specify correction parts from comparison results
Solution Approach 1:
The patent introduces an intermediary system that includes a difference extraction unit, feature calculation unit, and similarity calculation unit. This intermediary automatically processes executable files, extracts differences, calculates features, and determines similarity between corrected and uncorrected versions, eliminating the need for analysts to manually interpret complex binary comparison results
Solution Approach 2:
The patent replaces the mechanical manual analysis process with an automated computational system. Instead of analysts manually examining binary comparison results, the system automatically extracts differences, calculates features such as instruction frequency and code structure characteristics, and computes similarity scores to identify vulnerability correction parts
2Measurement precision
If compiler and link environment differences are considered in executable file comparison, then more accurate vulnerability analysis can be performed, but the complexity of identifying correction parts increases
Solution Approach 1:
The patent changes the parameters used for comparison by extracting specific features from executable files, such as instruction frequency, code structure characteristics, and functional behavior metrics. These parameter transformations allow accurate vulnerability identification while abstracting away compiler and link environment differences
Solution Approach 2:
The patent segments the executable file analysis into distinct components: difference extraction, feature calculation, and similarity evaluation. This segmentation allows each component to handle specific aspects of the comparison independently, managing complexity while maintaining accuracy in identifying vulnerability correction parts
Data Source
AI summary
A difference extracting unit extracts, from an executable file converted from a source code and an executable file converted from a source code after vulnerability correction is made to the source code, a difference of a part where the vulnerability correction is made. A feature calculating unit calculates features of the difference extracted by the difference extracting unit. A difference extracting unit extracts, from an executable file converted from a source code and an executable file converted from a source code after correction is made to the source code, a difference of a predetermined part. A similarity calculating unit calculates similarity between the difference of the predetermined part calculated by the difference extracting unit and the features of the difference of the part where the vulnerability correction is made calculated by the feature calculating unit.