BuildKit interactive containers API does not validate entitlements check
cve-program · CVE-2024-23653
PublishedBuildKit 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.
Read the publisher's advisoryeuvd · EUVD-2024-0453
PublishedBuildKit 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.
Read the publisher's advisorynvd · CVE-2024-23653
PublishedBuildKit 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.
Read the publisher's advisoryosv · GHSA-wr6v-9f75-vh2g
Published### 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
Read the publisher's advisoryosv · GO-2024-2497
PublishedBuildKit 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2024-23653 · CVE overview and exploitation status
cve-program · CVE-2024-23653
- https://github.com/moby/buildkit/security/advisories/GHSA-wr6v-9f75-vh2g
- https://github.com/moby/buildkit/pull/4602
- https://github.com/moby/buildkit/releases/tag/v0.12.5
euvd · EUVD-2024-0453
- https://github.com/moby/buildkit/security/advisories/GHSA-wr6v-9f75-vh2g
- https://github.com/moby/buildkit/pull/4602
- https://github.com/moby/buildkit/releases/tag/v0.12.5
nvd · CVE-2024-23653
- https://github.com/moby/buildkit/pull/4602
- https://github.com/moby/buildkit/releases/tag/v0.12.5
- https://github.com/moby/buildkit/security/advisories/GHSA-wr6v-9f75-vh2g
osv · GHSA-wr6v-9f75-vh2g
- https://github.com/moby/buildkit/security/advisories/GHSA-wr6v-9f75-vh2g
- https://nvd.nist.gov/vuln/detail/CVE-2024-23653
- https://github.com/moby/buildkit/pull/4602
- https://github.com/moby/buildkit/commit/5026d95aa3336e97cfe46e3764f52d08bac7a10e
- https://github.com/moby/buildkit/commit/92cc595cfb12891d4b3ae476e067c74250e4b71e
- https://github.com/moby/buildkit
- https://github.com/moby/buildkit/releases/tag/v0.12.5
osv · GO-2024-2497
Related changes
Linked by CVE identifierNo related changes are available here.