8.4 HIGH
- CVSS version: 3.1
- Attack vector (AV): LOCAL
- Attack complexity (AC): LOW
- Privileges required (PR): NONE
- User interaction (UI): NONE
- Scope (S): UNCHANGED
- Confidentiality impact (C): HIGH
- Integrity impact (I): HIGH
- Availability impact (A): HIGH
BuildKit vulnerable to malicious frontend causing file escape outside of storage root
BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. Prior to version 0.28.1, when using a custom BuildKit frontend, the frontend can craft an API message that causes files to be written outside of the BuildKit state directory for the execution context. The issue has been fixed in v0.28.1. The vulnerability requires using an untrusted BuildKit frontend set with `#syntax` or `--build-arg BUILDKIT_SYNTAX`. Using these options with a well-known frontend image like `docker/dockerfile` is not affected.
References
-
https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj x_refsource_CONFIRM
-
https://github.com/moby/buildkit/releases/tag/v0.28.1 x_refsource_MISC
Affected products
- ==< 0.28.1
Matching in nixpkgs
pkgs.buildkit
Concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
pkgs.buildkit-nix
Nix frontend for BuildKit
pkgs.buildkite-cli
Command line interface for Buildkite
pkgs.buildkite-agent
Build runner for buildkite.com
pkgs.buildkite-agent-metrics
Command-line tool (and Lambda) for collecting Buildkite agent metrics
pkgs.buildkite-test-collector-rust
Rust adapter for Buildkite Test Analytics
pkgs.terraform-providers.buildkite
None
Package maintainers
-
@vdemeester Vincent Demeester <vincent@sbr.pm>
-
@developer-guy Batuhan Apaydın <developerguyn@gmail.com>
-
@LeSuisse Thomas Gerbet <thomas@gerbet.me>
-
@techknowlogick techknowlogick <techknowlogick@gitea.com>
-
@jsoo1 John Soo <jsoo1@asu.edu>
-
@mostlyobvious Paweł Pacana <pawel.pacana@gmail.com>
-
@zimbatm zimbatm <zimbatm@zimbatm.com>
-
@cole-h Cole Helbling <cole.e.helbling@outlook.com>
-
@grahamc Graham Christensen <graham@grahamc.com>
-
@groodt Greg Roodt <groodt@gmail.com>
-
@jfroche Jean-François Roche <jfroche@pyxel.be>