Vulnerabilities

In BuildKit versions prior to v0.34.1, a malicious client with access to the BuildKit control APIs can submit a build request that sets an extended attribute on a file outside the BuildKit state directory.

In BuildKit versions v0.26.0 through v0.34.1, a specific build definition that resolves metadata for the same Git source reference twice can cause the BuildKit daemon to panic and crash, interrupting builds handled by th…

The `github.com/moby/sys/user` package provides Go utilities for parsing and looking up entries in Unix-style user and group database files.

Docker Engine classifies a registry hostname as insecure using an any-match DNS check.

The firewall rules which mark VXLAN datagrams for encryption indiscriminately match both authentic VXLAN datagrams sent from the kernel and forged datagrams sent by user processes.

A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

When proxy networking with CA injection is enabled, a build can modify its CA bundle before cleanup.

A build step for a Git source, crafted in a specific way, can bypass some policy validation rules.

The Dockerfile frontend loaded the Dockerfile and .dockerignore files of a build context into memory without a size limit.

A malicious frontend can submit an LLB definition that causes buildkitd to panic and terminate, interrupting all builds running on that daemon.

BuildKit may be tricked into performing file actions with special file inodes where regular files are expected.

A malicious external BuildKit frontend can send requests using the internal API that can create conditions for a data race that can cause the BuildKit daemon to panic.

A malicious image can advertise DiffIDs from another image while containing different layer contents.

An unauthenticated attacker controlling a registry or OCI-layout blob source could provide blob contents that did not match the claimed digest.

If BuildKit daemon is started with --cdi-disabled it can lead to daemon panic when builds try to use CDI devices.

BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.

BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.

BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner.

The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory.

BuildKit custom frontends or clients using the raw low-level API can set git.checkoutbundle=true when checking out Git sources.

A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic.

A crafted message in the BuildKit low-level build API can be used to remove the contents of the /tmp directory.

A custom client can produce such an upload request to the BuildKit daemon that files can escape from the BuildKit-controlled state directory.

BuildKit's cache mount source= selector on Windows Container on Windows (WCOW) workers does not detect NTFS directory junctions placed inside the cache root.

Moby is an open source container framework.