Automated Vulnerability Mitigation via Tainted Path Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for identifying and mitigating software security vulnerabilities in source code are labor-intensive and often require manual validation, leading to potential security issues being deployed due to lack of time or resources.

Innovation Solution

A method that builds a path graph from source code, identifies tainted paths corresponding to vulnerabilities, and automatically mitigates vulnerabilities by applying instant-fix calls at target nodes with the highest confidence scores, thereby reducing manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If static code analysis tools are used to scan source code for vulnerabilities, then potential security issues can be detected, but manual implementation and validation of fixes remains labor-intensive

Engineering Contradiction:
Improvesecurity vulnerability detectionVSAvoidmanual fix implementation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system automatically generates remediation code and applies fixes without requiring manual intervention. The vulnerability mitigation system performs self-service by detecting vulnerabilities, generating appropriate fix code, and applying the remediation automatically, thereby eliminating the labor-intensive manual implementation and validation process while maintaining reliable security detection

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary analysis of the source code to identify vulnerabilities before they can be exploited. By conducting static code analysis in advance and preparing remediation strategies beforehand, the system enables proactive security mitigation rather than reactive manual fixing after deployment

Inventive Principle:
Principle #10Preliminary action

2Reliability

If developers manually validate and implement vulnerability fixes, then security issues can be addressed, but time and resources are consumed leading to potential deployment of vulnerable applications

Engineering Contradiction:
Improvevulnerability remediationVSAvoidvulnerability remediation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The automated vulnerability mitigation system performs remediation without requiring developer time for manual validation and implementation. The system autonomously generates and applies fixes, dramatically reducing the time loss associated with manual vulnerability remediation while ensuring reliable security improvements are deployed

Inventive Principle:
Principle #25Self-service

3Reliability

If comprehensive static code analysis is performed on all execution paths, then complete vulnerability coverage is achieved, but system complexity increases

Engineering Contradiction:
Improvevulnerability detection coverageVSAvoidcode analysis system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts and focuses analysis on specific tainted paths that are most likely to contain vulnerabilities, rather than analyzing every possible execution path equally. By isolating and concentrating computational resources on high-risk code paths identified through taint analysis, the system achieves comprehensive vulnerability coverage while managing system complexity through selective rather than exhaustive analysis

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20250047704A1Method, system, and computer program product for automatically mitigating vulnerabilities in source code
Publication Date: 2025.02.06 LUCENT SKY CORP
  • US20250047704A1 patent drawing
  • US20250047704A1 patent drawing
  • US20250047704A1 patent drawing

AI summary

A method, a system, and a computer program product for automatically mitigating vulnerabilities in a source code are provided. The method includes the following steps. First, a path graph is built according to the source code, where the path graph includes at least one path, and each of the at least one path includes multiple nodes. A tainted path is identified from the path graph, where the tainted path corresponds to at least one vulnerability. Multiple candidate nodes are located from the tainted path based on an existence of a tainted object. A confidence score of a first instant-fix call respectively corresponds to each of the candidate nodes is determined, and a candidate node having a maximum confidence score among the candidate nodes is set as a target node. The at least one vulnerability in the target node is mitigated automatically by applying the first instant-fix call.