# US 2025/0165613 A1 · Vulnerability response based on interface instrumentation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0165613 A1
- Document ID: US20250165613A1
- Status: Published application
- Kind: A1
- Application number: 18/526,085
- Filed: 2023-12-01
- Published: 2025-05-22
- Earliest claimed: 2023-11-16
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Max Fabian Gilbert; Reinhold Geiselhart; Felix Beier; Knut Stolze
- Web page: https://patentgrep.com/patent/US20250165613A1

## CPC

- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 21/52: during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow}
- G06F 21/554: {involving event detection and direct action}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A computer-implemented method for protecting a software code against a security vulnerability, wherein the software code comprises at least one software code component, some of which comprising a function call, whereby each function call represents a dependency is disclosed. The method comprises integrating a dependency profiler with the at least one software code component, intercepting, at runtime of the software code component, the function call to at least one API of the service component, thereby detecting dynamically dependencies, recording a sequence of usage of the detected dependencies in a profiler report, and performing a response action based on known vulnerabilities in the sequence of the usage of the detected dependencies

## Claims

### Claim 1

A computer-implemented method for protecting a software code against a security vulnerability, wherein the software code comprises at least one software code component, some of which comprising a function call to a service component, whereby each function call represents a dependency, the method comprising:
integrating a dependency profiler with the at least one software code component;
intercepting, at runtime of the software code component, the function call to at least one API of the service component, thereby detecting dynamically dependencies;
recording a sequence of usage of the detected dependencies in a profiler report; and
performing a response action based on known vulnerabilities in the sequence of the usage of the detected dependencies.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising:
performing the response action if the scoring value of the dependency is larger than a predefined threshold value.

### Claim 3 (depends on 2)

The method according to claim 2, wherein the performing of the response action comprises:
determining a reaction type dependent on the scoring value of a predefined sequence of dependencies.

### Claim 4 (depends on 1)

The method according to claim 1, further comprising:
retrieving information about known vulnerabilities including information about dangerous sequences of dependencies having a potential for causing a security issue with the service component.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising:
retrieving information about known vulnerabilities including information about dangerous function call parameter values, each of which being indicative of a potential security issue with the service component.

### Claim 6 (depends on 1)

The method according to claim 1, further comprising:
marking a service component relating to the dependency as to be updated depending on the reaction type.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the integrating a dependency profiler with the at least one software code component further comprises:
generating the wrapper code for a called library dynamically.

### Claim 8 (depends on 1)

The method according to claim 1, wherein the reaction type comprises at least one from the group consisting of:
generating an alert;
blocking an API specific functionality of the software code component;
blocking the function call to the service component;
terminating an execution of the software code component;
marking the dependent component as “to be updated”;
changing function call parameters, thereby circumventing a vulnerability; and
changing a function call sequence, thereby circumventing a vulnerability.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the dependency profiler changes function call arguments for the function call to the service component based on values of the function call arguments being known to be vulnerable for the software code.

### Claim 10 (depends on 1)

The method according to claim 1, wherein the profile wrapper changes the sequence of function calls to the service component based on specific sequences of function calls being known to be vulnerable for the software code.

### Claim 11 (depends on 8)

The method according to claim 8, further comprising:
allow-listing a function call in case a vulnerability for values of the function call arguments are known.

### Claim 12

A runtime dependency security computer system for protecting a software code against a security vulnerability, the system comprising:
one or more processors and a memory operatively coupled to the one or more processors, wherein the memory stores program code portions which, when executed by the one or more processors, enable the one or more processors to:
integrate a dependency profiler with the at least one software code component;
intercept, at runtime of the software code component, the function call to at least one API of the service component, thereby detecting dynamically dependencies;
record a sequence of usage of the detected dependencies in a profiler report; and
perform a response action based on known vulnerabilities in the sequence of the usage of the detected dependencies.

### Claim 13 (depends on 12)

The computer system according to claim 12, wherein the processor performs the response action based on the scoring of the dependency being larger than a predefined threshold value.

### Claim 14 (depends on 12)

The computer system according to claim 12, wherein the processor performs the response action:
determine a reaction type depending on the scoring value of a predefined sequence of dependencies.

### Claim 15 (depends on 12)

The computer system according to claim 12, wherein the processor:
retrieves information about known vulnerabilities including information about dangerous sequences of dependencies having a potential for causing a security issue with the service component.

### Claim 16 (depends on 12)

The computer system according to claim 12, wherein the processor marks a service component relating to the dependency as to be updated depending on the reaction type.

### Claim 17 (depends on 12)

The computer system according to claim 12, wherein the processor, when integrating a dependency profiler with the at least one software code component, generates the wrapper code for a called library dynamically.

### Claim 18 (depends on 12)

The computer system according to claim 12, wherein the reaction type comprises at least one from the group consisting of:
generating an alert;
blocking an API specific functionality of the software code component;
blocking the function call to the service component;
terminating an execution of the software code component;
marking the dependent component as “to be updated”;
changing function call parameters, thereby circumventing a vulnerability; and
changing a function call sequence, thereby circumventing a vulnerability.

### Claim 19 (depends on 12)

The computer system according to claim 12, wherein the processor is also enabled to:
allow-list a function call in case a vulnerability for values of the function call arguments are known.

### Claim 20

A computer program product for securing a software code against a security vulnerability, wherein the software code comprises at least one software code component, some of which comprising a function call to a service component, whereby each function call represents a dependency:
the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions being executable by one or more computing systems or controllers to cause the one or more computing systems to:
integrate a dependency profiler with the at least one software code component;
intercept, at runtime of the software code component, the function call to at least one API of the service component, thereby detecting dynamically dependencies;
record a sequence of usage of the detected dependencies in a profiler report; and
perform a response action based on known vulnerabilities in the sequence of the usage of the detected dependencies.
