BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.
CVE-2024-23653 - Critical Severity Vulnerability
Vulnerable Libraries - github.com/docker/cli-v20.10.6+incompatible, github.com/Docker/Docker-v20.10.9+incompatible
github.com/docker/cli-v20.10.6+incompatible
The Docker CLI
Library home page: https://proxy.golang.org/github.com/docker/cli/@v/v20.10.6+incompatible.zip
Path to dependency file: /portainer-develop/portainer-develop/api/go.mod
Path to vulnerable library: /portainer-develop/portainer-develop/api/go.mod
Dependency Hierarchy: - :x: **github.com/docker/cli-v20.10.6+incompatible** (Vulnerable Library)
github.com/Docker/Docker-v20.10.9+incompatible
Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
Library home page: https://proxy.golang.org/github.com/!docker/!docker/@v/v20.10.9+incompatible.zip
Path to dependency file: /portainer-develop/portainer-develop/api/go.mod
Path to vulnerable library: /portainer-develop/portainer-develop/api/go.mod
Dependency Hierarchy: - :x: **github.com/Docker/Docker-v20.10.9+incompatible** (Vulnerable Library)
Found in HEAD commit: ec9d972edb7fb1ea028782bd0f770272d89e0c60
Found in base branch: main
Vulnerability Details
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.
Publish Date: 2024-01-31
URL: CVE-2024-23653
CVSS 3 Score Details (9.8)
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: https://github.com/moby/buildkit/security/advisories/GHSA-wr6v-9f75-vh2g
Release Date: 2024-01-31
Fix Resolution: v0.12.5
Step up your Open Source Security Game with Mend here