Targeted Web Vulnerability Testing via Static-Dynamic Analysis

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for identifying vulnerabilities in client-side web applications are inefficient, as they often require extensive dynamic analysis of all web pages, which is time-consuming and resource-intensive, especially when most pages do not contain vulnerabilities.

Innovation Solution

A method that combines static analysis to identify potential vulnerabilities in web pages, followed by targeted dynamic analysis using a subset of test payloads for confirmed vulnerabilities and a reduced set for non-vulnerable pages, optimizing the use of resources by dynamically analyzing only those pages flagged as vulnerable.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If extensive dynamic analysis is performed on all web pages, then vulnerability detection completeness is improved, but time consumption and resource expenditure increase

Engineering Contradiction:

Improvevulnerability detection completenessVSAvoidtime consumption

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system performs static analysis on all web pages before dynamic analysis to pre-identify pages containing vulnerable script code. This preliminary action filters out safe pages, allowing dynamic analysis to be focused only on potentially vulnerable pages, thereby reducing overall time consumption while maintaining detection completeness

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The analysis process is divided into two distinct stages: static analysis (code examination) and dynamic analysis (runtime testing). By segmenting the workflow and applying different analysis methods to different pages based on static analysis results, the system optimizes resource allocation and reduces unnecessary dynamic analysis time

Inventive Principle:

Principle #1Segmentation

2Reliability

If extensive dynamic analysis is performed on all web pages, then vulnerability detection completeness is improved, but resource expenditure increases

Engineering Contradiction:

Improvevulnerability detection completenessVSAvoidresource expenditure

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

Static analysis is performed as a preliminary filtering step to identify pages containing vulnerable script code patterns. This pre-screening action prevents resource-intensive dynamic analysis from being applied to safe pages, significantly reducing overall resource expenditure while preserving detection completeness for actually vulnerable pages

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system applies dynamic analysis selectively rather than universally - performing full dynamic analysis only on pages identified as potentially vulnerable through static analysis, and applying reduced or no dynamic analysis to pages confirmed safe by static analysis, thereby optimizing resource usage

Inventive Principle:

Principle #16Partial or excessive action

3Loss of time

If static analysis is used to identify potential vulnerabilities, then time consumption is reduced, but false positives increase

Engineering Contradiction:

Improvetime consumptionVSAvoidfalse positive rate

Core Design Contradiction:

Loss of timeVSMeasurement precision

Solution Approach 1:

The system uses a two-stage feedback mechanism where static analysis results feed into dynamic analysis planning, and dynamic analysis results feed back to confirm or refute static analysis findings. This feedback loop allows the system to resolve false positives by verifying static analysis predictions through actual dynamic testing on flagged pages

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS9971896B2Targeted security testing

Publication Date: 2018.05.15 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

Source code of a plurality of web pages including script code is statically analyzed. A page including a potential vulnerability is identified based on the static analysis. A page not including a potential vulnerability is identified based on the static analysis. The web page including the potential vulnerability is dynamically analyzed using a set of test payloads. The page not including the potential vulnerability is dynamically analyzed using a subset of the set of test payloads, the subset including fewer test payloads than the set of test payloads.