GitHub Advisoryadvisory · Go

GHSA-wr6v-9f75-vh2g Buildkit's interactive containers API does not validate entitlements check

CRITICAL Published 2024-01-31 Modified 2024-05-20 Official page ↗
Aliases
CVE-2024-23653
Ecosystem
Go
Packages
github.com/moby/buildkit
Severity
Critical
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-863
Reviewed
2024-01-31

Affected packages

• Go github.com/moby/buildkit: < 0.12.5 → fixed in 0.12.5

Description

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

Related

Alias · CVE (1)

  • CVE-2024-23653 BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. vulnerability

Weakness · CWE (1)

  • CWE-863 Incorrect Authorization weakness

References