GHSA-wr6v-9f75-vh2g
Buildkit's interactive containers API does not validate entitlements check
Quick fix
GHSA-wr6v-9f75-vh2g — github.com/moby/buildkit: upgrade to the fixed version with the command below.
go get github.com/moby/buildkit@v0.12.5Details
### 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
Are you affected?
Enter the version of the package you're using.
Affected packages
0Fixed in: 0.12.5go get github.com/moby/buildkit@v0.12.5References
- https://github.com/moby/buildkit/security/advisories/GHSA-wr6v-9f75-vh2g[WEB]
- https://nvd.nist.gov/vuln/detail/CVE-2024-23653[ADVISORY]
- https://github.com/moby/buildkit/pull/4602[WEB]
- https://github.com/moby/buildkit/commit/5026d95aa3336e97cfe46e3764f52d08bac7a10e[WEB]
- https://github.com/moby/buildkit/commit/92cc595cfb12891d4b3ae476e067c74250e4b71e[WEB]
- https://github.com/moby/buildkit[PACKAGE]
- https://github.com/moby/buildkit/releases/tag/v0.12.5[WEB]