First published: Wed Jan 31 2024(Updated: )
### 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
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
go/github.com/moby/buildkit | <0.12.5 | 0.12.5 |
Mobyproject Buildkit | <0.12.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-23653 has a high severity due to the potential for running containers with elevated privileges.
To fix CVE-2024-23653, upgrade to BuildKit version 0.12.5 or later.
Affected versions of BuildKit range up to but not including version 0.12.5.
CVE-2024-23653 allows unauthorized access to run interactive containers with elevated privileges.
CVE-2024-23653 specifically affects Mobyproject BuildKit.