Vulnerability Inference for Shared Software Resources

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The extent of vulnerability from a compromised shared software resource is difficult to determine due to its widespread use across multiple applications and processes, as developers and users often lack knowledge of dependencies, making it a significant security threat.

Innovation Solution

A method and system that connect to a computer to enumerate installed shared software resources, identify vulnerable resources, and remediate affected processes by updating, uninstalling, or terminating them, using package management systems and metadata to track dependencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If shared software resources are widely distributed and used across multiple applications, then the utility and versatility of the shared resource increases, but the extent of vulnerability and security risk increases

Engineering Contradiction:
Improveutility of shared resourceVSAvoidextent of vulnerability
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system segments the vulnerability assessment process into distinct components: enumerating installed resources, identifying vulnerable resources through version checking, determining dependent processes, and remediating specific processes. This segmentation allows comprehensive security assessment without requiring complete system shutdown or complex global analysis.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by proactively scanning for vulnerable shared resources before they can be exploited. It preemptively identifies vulnerable processes and applies remedies (updates, terminations, or isolations) before security breaches occur, preventing rather than merely detecting threats.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If developers and users do not track dependencies of shared software resources, then the complexity of software management is reduced, but the ability to determine vulnerability extent deteriorates

Engineering Contradiction:
Improvesoftware management complexityVSAvoidknowledge of dependencies
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The system performs self-service by automatically enumerating installed shared software resources, retrieving their version information, identifying vulnerabilities, and determining dependent processes without requiring manual tracking by developers or users. The system independently gathers all necessary dependency information through automated scanning and analysis.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring the software environment, comparing installed resource versions against vulnerability databases, and using the results to identify affected processes. This feedback loop enables dynamic vulnerability assessment and automated remediation without manual intervention.

Inventive Principle:
Principle #23Feedback

3Reliability

If automated vulnerability scanning and remediation is implemented, then the security response time is improved, but the device complexity and resource consumption increase

Engineering Contradiction:
Improvesecurity response timeVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system achieves multi-functionality by combining multiple security operations into a single integrated platform: resource enumeration, version verification, vulnerability identification, process dependency analysis, and remediation execution. This universal approach improves security response time while avoiding the complexity of multiple separate tools and manual coordination.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11783047B1Vulnerability inference for identifying vulnerable processes
Publication Date: 2023.10.10 RAPID7 INC
  • US11783047B1 patent drawing
  • US11783047B1 patent drawing
  • US11783047B1 patent drawing

AI summary

Systems and methods for determining an extent of a vulnerability on a computer and remediating the vulnerability. An installed resource set comprising shared software resources installed on the computer is enumerated. A vulnerable resource is identified in the installed resource set. A vulnerable process set including at least one vulnerable process that uses the vulnerable resource is enumerated. And, the vulnerable process is remediated.