CVE-2024-23653

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.

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.

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.

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.

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.

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.

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.

Impact

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.

Patches

The issue has been fixed in v0.12.5 .

Workarounds

Avoid using BuildKit frontends from untrusted sources. A frontend image is usually specified as the #syntax line on your Dockerfile, or with --frontend flag when using buildctl build command.

References

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.

BuildKit 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.

These are all security issues fixed in the buildkit-0.12.5-2.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the docker-24.0.7_ce-3.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the singularity-ce-4.1.3-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the docker-stable-24.0.9_ce-4.1 package on the GA media of openSUSE Tumbleweed.

This update for docker-stable fixes the following issues:

• Update docker-buildx to v0.19.2. See upstream changelog online at https://github.com/docker/buildx/releases/tag/v0.19.2. Some notable changelogs from the last update:

  • https://github.com/docker/buildx/releases/tag/v0.19.0
  • https://github.com/docker/buildx/releases/tag/v0.18.0

• Add a new toggle file /etc/docker/suse-secrets-enable which allows users to disable the SUSEConnect integration with Docker (which creates special mounts in /run/secrets to allow container-suseconnect to authenticate containers with registries on registered hosts). bsc#1231348 bsc#1232999 In order to disable these mounts, just do echo 0 > /etc/docker/suse-secrets-enable and restart Docker. In order to re-enable them, just do echo 1 > /etc/docker/suse-secrets-enable and restart Docker. Docker will output information on startup to tell you whether the SUSE secrets feature is enabled or not.

This update for docker fixes the following issues:

Vendor latest buildkit v0.11 including bugfixes for the following:

• CVE-2024-23653: BuildKit API doesn't validate entitlement on container creation (bsc#1219438).
• CVE-2024-23652: Fixed arbitrary deletion of files (bsc#1219268).
• CVE-2024-23651: Fixed race condition in mount (bsc#1219267).

This update for docker fixes the following issues:

Vendor latest buildkit v0.11 including bugfixes for the following:

• CVE-2024-23653: BuildKit API doesn't validate entitlement on container creation (bsc#1219438).
• CVE-2024-23652: Fixed arbitrary deletion of files (bsc#1219268).
• CVE-2024-23651: Fixed race condition in mount (bsc#1219267).

This update for docker fixes the following issues:

Vendor latest buildkit v0.11 including bugfixes for the following:

• CVE-2024-23653: BuildKit API doesn't validate entitlement on container creation (bsc#1219438).
• CVE-2024-23652: Fixed arbitrary deletion of files (bsc#1219268).
• CVE-2024-23651: Fixed race condition in mount (bsc#1219267).

This update for docker fixes the following issues:

• CVE-2024-23651: Fixed arbitrary files write due to race condition on mounts (bsc#1219267)
• CVE-2024-23652: Fixed insufficient validation of parent directory on mount (bsc#1219268)
• CVE-2024-23653: Fixed insufficient validation on entitlement on container creation via buildkit (bsc#1219438)

Other fixes:

• Update to Docker 25.0.5-ce (bsc#1223409)

This update for buildah, docker fixes the following issues:

Changes in docker:

• CVE-2024-23651: Fixed arbitrary files write due to race condition on mounts (bsc#1219267)
• CVE-2024-23652: Fixed insufficient validation of parent directory on mount (bsc#1219268)
• CVE-2024-23653: Fixed insufficient validation on entitlement on container creation via buildkit (bsc#1219438)
• CVE-2024-41110: A Authz zero length regression that could lead to authentication bypass was fixed (bsc#1228324)

Other fixes:

• Update to Docker 25.0.6-ce. See upstream changelog online at https://docs.docker.com/engine/release-notes/25.0/#2506

• Update to Docker 25.0.5-ce (bsc#1223409)

• Fix BuildKit's symlink resolution logic to correctly handle non-lexical symlinks. (bsc#1221916)

• Write volume options atomically so sudden system crashes won't result in future Docker starts failing due to empty files. (bsc#1214855)

Changes in buildah:

• Update to version 1.35.4:

  • [release-1.35] Bump to Buildah v1.35.4
  • [release-1.35] CVE-2024-3727 updates (bsc#1224117)
  • integration test: handle new labels in 'bud and test --unsetlabel'
  • [release-1.35] Bump go-jose CVE-2024-28180
  • [release-1.35] Bump ocicrypt and go-jose CVE-2024-28180

• Update to version 1.35.3:

  • [release-1.35] Bump to Buildah v1.35.3
  • [release-1.35] correctly configure /etc/hosts and resolv.conf
  • [release-1.35] buildah: refactor resolv/hosts setup.
  • [release-1.35] rename the hostFile var to reflect
  • [release-1.35] Bump c/common to v0.58.1
  • [release-1.35] Bump Buildah to v1.35.2
  • [release-1.35] CVE-2024-24786 protobuf to 1.33
  • [release-1.35] Bump to v1.35.2-dev

• Update to version 1.35.1:

  • [release-1.35] Bump to v1.35.1
  • [release-1.35] CVE-2024-1753 container escape fix (bsc#1221677)

• Buildah dropped cni support, require netavark instead (bsc#1221243)

• Remove obsolete requires libcontainers-image & libcontainers-storage

• Require passt for rootless networking (poo#156955) Buildah moved to passt/pasta for rootless networking from slirp4netns (https://github.com/containers/common/pull/1846)

• Update to version 1.35.0:

  • Bump v1.35.0
  • Bump c/common v0.58.0, c/image v5.30.0, c/storage v1.53.0
  • conformance tests: don't break on trailing zeroes in layer blobs
  • Add a conformance test for copying to a mounted prior stage
  • fix(deps): update module github.com/stretchr/testify to v1.9.0
  • cgroups: reuse version check from c/common
  • Update vendor of containers/(common,image)
  • fix(deps): update github.com/containers/storage digest to eadc620
  • fix(deps): update github.com/containers/luksy digest to ceb12d4
  • fix(deps): update github.com/containers/image/v5 digest to cdc6802
  • manifest add: complain if we get artifact flags without --artifact
  • Use retry logic from containers/common
  • Vendor in containers/(storage,image,common)
  • Update module golang.org/x/crypto to v0.20.0
  • Add comment re: Total Success task name
  • tests: skip_if_no_unshare(): check for --setuid
  • Properly handle build --pull=false
  • [skip-ci] Update tim-actions/get-pr-commits action to v1.3.1
  • Update module go.etcd.io/bbolt to v1.3.9
  • Revert 'Reduce official image size'
  • Update module github.com/opencontainers/image-spec to v1.1.0
  • Reduce official image size
  • Build with CNI support on FreeBSD
  • build --all-platforms: skip some base 'image' platforms
  • Bump main to v1.35.0-dev
  • Vendor in latest containers/(storage,image,common)
  • Split up error messages for missing --sbom related flags
  • buildah manifest: add artifact-related options
  • cmd/buildah/manifest.go: lock lists before adding/annotating/pushing
  • cmd/buildah/manifest.go: don't make struct declarations aliases
  • Use golang.org/x/exp/slices.Contains
  • Disable loong64 again
  • Fix a couple of typos in one-line comments
  • egrep is obsolescent; use grep -E
  • Try Cirrus with a newer VM version
  • Set CONTAINERS_CONF in the chroot-mount-flags…

This update for docker-stable fixes the following issues:

• CVE-2024-29018: Fixed external DNS request handling from 'internal' networks that could have led to data exfiltration (bsc#1234089).
• CVE-2024-23650: Fixed possibile BuildKit daemon crash via malicious BuildKit client or frontend request (bsc#1219437).

This update for docker-stable fixes the following issues:

• Include historical changelog data from before the docker-stable fork. The initial changelog entry did technically provide all the necessary information, but our CVE tracking tools do not understand how the package is forked and so it seems that this package does not include fixes for ~12 years of updates. So, include a copy of the original package's changelog up until the fork point. (bsc#1250596)

• Remove git-core recommends on SLE. Most SLE systems have installRecommends=yes by default and thus end up installing git with Docker. bsc#1250508

  This feature is mostly intended for developers ('docker build git://') so most users already have the dependency installed, and the error when git is missing is fairly straightforward (so they can easily figure out what they need to install).

• Backport https://github.com/moby/moby/pull/48517. bsc#1247362

• Update to docker-buildx v0.25.0. Upstream changelog: https://github.com/docker/buildx/releases/tag/v0.25.0

• Do not try to inject SUSEConnect secrets when in Rootless Docker mode, as Docker does not have permission to access the host zypper credentials in this mode (and unprivileged users cannot disable the feature using /etc/docker/suse-secrets-enable.) bsc#1240150

• Initial docker-stable fork, forked from Docker 24.0.7-ce release (packaged on 2024-02-14). The original changelog is included below for historical reference.

This update for docker-stable fixes the following issues:

Note this update contains a already fixed references mostly.

• Remove git-core recommends on SLE to avoid pulling it in unnecessary. (bsc#1250508)

  This feature is mostly intended for developers ('docker build git://') so most users already have the dependency installed, and the error when git is missing is fairly straightforward (so they can easily figure out what they need to install).

• Include historical changelog data from before the docker-stable fork. The initial changelog entry did technically provide all the necessary information, but our CVE tracking tools do not understand how the package is forked and so it seems that this package does not include fixes for ~12 years of updates. So, include a copy of the original package's changelog up until the fork point. bsc#1250596

• Update to docker-buildx v0.25.0. Upstream changelog: https://github.com/docker/buildx/releases/tag/v0.25.0

• Update to Go 1.23 for building now that upstream has switched their 23.0.x LTSS to use Go 1.23.

• Do not try to inject SUSEConnect secrets when in Rootless Docker mode, as Docker does not have permission to access the host zypper credentials in this mode (and unprivileged users cannot disable the feature using /etc/docker/suse-secrets-enable.) bsc#1240150

• Initial docker-stable fork, forked from Docker 24.0.7-ce release (packaged on 2024-02-14). The original changelog is included below for historical reference.

This update for docker, docker-stable fixes the following issues:

• CVE-2025-22868: Fixed unexpected memory consumption during token parsing in golang.org/x/oauth2 (bsc#1239185).
• CVE-2025-22869: Fixed Denial of Service in the Key Exchange of golang.org/x/crypto/ssh (bsc#1239322).
• CVE-2024-29018: Fixed external DNS requests from 'internal' networks leading to data exfiltration (bsc#1234089).
• CVE-2024-23650: Fixed BuildKit daemon crash via malicious BuildKit client or frontend request (bsc#1219437).

Other fixes:

• Make container-selinux requirement conditional on selinux-policy (bsc#1237367).
• Updated docker-buildx to 0.19.3.

This update for docker fixes the following issues:

Security fixes:

• CVE-2024-23651: Fixed arbitrary files write due to race condition on mounts (bsc#1219267)
• CVE-2024-23652: Fixed insufficient validation of parent directory on mount (bsc#1219268)
• CVE-2024-23653: Fixed insufficient validation on entitlement on container creation via buildkit (bsc#1219438)
• CVE-2024-41110: A Authz zero length regression that could lead to authentication bypass was fixed (bsc#1228324)

Other changes:

• Update to Docker 25.0.6-ce.
• Fix BuildKit's symlink resolution logic to correctly handle non-lexical symlinks. (bsc#1221916)
• Write volume options atomically so sudden system crashes won't result in future Docker starts failing due to empty files. (bsc#1214855)
• Fixed world writable docker overlay files (bsc#1220339)

This update for buildkit fixes the following issues:

• Update to version 0.12.5:

  • update runc to v1.1.12
  • exec: add extra validation for submount sources (fixes CVE-2024-23651, bsc#1219267)
  • oci: fix error handling on submount calls
  • executor: recheck mount stub path within root after container run (fixes CVE-2024-23652, bsc#1219268)
  • llbsolver: make sure interactive container API validates entitlements (fixes CVE-2024-23653, bsc#1219438)
  • gateway: pass executor with build and not access worker directly
  • pb: add extra validation to protobuf types
  • sourcepolicy: add validations for nil values
  • exporter: add validation for platforms key value
  • exporter: add validation for invalid platorm
  • exporter: validate null config metadata from gateway
  • ci: disable push if not upstream repo
  • hack: use git context only for upstream repo
  • hack/test: allow ALPINE_VERSION to be set from env
  • hack: align syntax
  • vendor: github.com/cyphar/filepath-securejoin v0.2.4
  • tracing: allow the Resource to be set externally

• Update to version 0.12.4:

  • Fix possible concurrent map access on remote cache export
  • Fix hang on debug server listener
  • Fix possible deadlock in History API under high number of parallel builds
  • Fix possible panic on handling deleted records in History API
  • Fix possible data corruption in zstd library

• Update to version 0.12.3:

  • Fix possible duplicate source files in provenance attestation for chained builds
  • Fix possible negative step time in progressbar for step shared with other build request
  • Fix properly closing history and cache DB on shutdown to avoid corruption
  • Fix incorrect error handling for invalid HTTP source URLs
  • Fix fallback cases for ambiguous insecure configuration provided for registry used as push target.
  • Fix possible data race with parallel image config resolves
  • Fix regression in v0.12 for clients waiting on buildkitd to become available
  • Fix Cgroup NS handling for hosts supporting only CgroupV1

• Update to version 0.12.2:

  • Fix possible discarded network error when exporting result to client
  • Avoid unnecessary memory allocations when writing build progress

• Update to version 0.12.1:

  • executor: fix resource sampler goroutine leak
  • [v0.11] make tracing socket forward error non-fatal
  • integration: missing env var to check feature compat
  • test: update pinned busybox image to 1.36
  • test: update pinned alpine image to 3.18
  • vendor: github.com/docker/docker 8e51b8b59cb8 (master, v25.0.0-dev)
  • executor/resource: stub out NewSysSampler on Windows
  • vendor: github.com/docker/cli v24.0.4
  • testutil: move CheckContainerdVersion to a separate package
  • llbsolver: fix policy rule ordering
  • filesync: fix backward compatibility with encoding + and %
  • hack: allow to set GO_VERSION during tests
  • test: always disable tls for dockerd worker
  • buildctl: set max backoff delay to 1 second
  • contenthash: data race
  • filesync: escape special query characters
  • applier: add hack to support docker zstd layers
  • Fix various nits
  • pullprogress data race
  • use sampler lock instead
  • Fix ResolveImageConfig to evaluate source policy
  • sampler data race fix
  • update cgroup parent test to work with cgroupns
  • Revert "specify a ResponseHeaderTimeout value"
  • oci: make sure cgroupns is enabled if supported
  • bash lint fix
  • rename BUILDFLAGS to GOBUILDFLAGS
  • allow ENOTSUP for PSI cgroup files
  • containerimage: use platform matcher to detect platform to unpack
  • exporter: silently skip unpacking unknown reference
  • improve error handling in ReadFile
  • dockerfile: arg for controlling go build flags
  • dockerfile: arg to enable go race detection
  • Add support for health start interval
  • Re-vendor moby/moby
  • filesync: mark if options have been encoded to detect old versions
  • dockerfile: heredoc should use 0644 permissions
  • docs: update README to reference…