Container Image Remediation for Base-Image Vulnerability Propagation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software containers often inherit vulnerabilities from their origin images, leading to cascading security issues that existing techniques fail to effectively address.

Innovation Solution

A method and system for software container remediation that identifies vulnerabilities in origin images and rebuilds derived images using non-vulnerable origin images, recursively analyzing ancestor images to replace references and eliminate vulnerabilities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If container images are built by adding layers to base images, then development efficiency and reusability are improved, but vulnerabilities in base images are propagated to all derived images

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the container image into a base image and multiple derived images with layers. By identifying which derived images are actually deployed (rather than treating all images uniformly), the system can selectively remediate only the necessary images, maintaining the benefits of layer-based development while addressing security issues in specific instances.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of image vulnerability status by detecting vulnerabilities in base images and then remediating them by rebuilding affected derived images. This parameter change approach allows the system to maintain the efficient layer-based build process while transforming vulnerable images into secure ones through targeted rebuilding.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If all derived images are rebuilt when a base image vulnerability is found, then security is improved, but time consumption and resource usage increase

Engineering Contradiction:
ImprovesecurityVSAvoidremediation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies local quality by distinguishing between different types of derived images - those that are actually deployed versus those that are not. The system remediates only the deployed derived images that are affected by base image vulnerabilities, rather than uniformly rebuilding all derived images. This selective approach maintains security where needed while avoiding unnecessary time and resource consumption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements partial action by rebuilding only the subset of derived images that are both affected by vulnerabilities and actually deployed. This avoids the excessive action of rebuilding all possible derived images, thereby reducing remediation time and resource usage while still achieving the security goal of fixing vulnerable deployed containers.

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If vulnerability scanning is performed on all container images, then detection accuracy is improved, but system complexity and overhead increase

Engineering Contradiction:
Improvevulnerability detection accuracyVSAvoidscanning system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent performs preliminary action by scanning base images before they are used to build derived images. By detecting vulnerabilities in base images upfront and maintaining a record of which base images are vulnerable, the system can later efficiently identify which derived images need remediation without having to scan every derived image individually, thereby reducing overall system complexity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism that tracks the relationship between base images and derived images, along with vulnerability information. This intermediary layer allows the system to leverage the scan results from base images to determine which derived images are affected, avoiding the need for complex scanning of every derived image and reducing overall system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20260017383A1Techniques for software container remediation
Publication Date: 2026.01.15 WIZ INC
  • US20260017383A1 patent drawing
  • US20260017383A1 patent drawing
  • US20260017383A1 patent drawing

AI summary

A system and method for software container remediation. A method includes determining that a vulnerability of a software container resides in a first origin image of the software container at least partially by identifying a plurality of derived container images referencing the origin image which have the vulnerability, wherein a first derived container image of the plurality of derived container images is used to run the software container; and rebuilding the first derived container image using contents of a second origin image, wherein the second origin image avoids the vulnerability.