CVE-2024-23653: BuildKit interactive containers API does not validate entitlements check

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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

• agent/weakness
• agent/title
• agent/type
• agent/first-publish-date
• agent/severity
• agent/description
• agent/author
• collector/nvd-api
• source/NVD
• agent/software-canonical-lookup
• agent/remedy
• agent/softwarecombine
• collector/nvd-cve
• agent/event
• collector/epss-latest
• source/FIRST
• agent/epss
• collector/github-advisory-latest
• source/GitHub
• alias/GHSA-wr6v-9f75-vh2g
• alias/CVE-2024-23653
• agent/references
• agent/tags
• collector/github-advisory
• collector/mitre-cve
• source/MITRE
• agent/last-modified-date
• agent/trending
• vendor/mobyproject
• canonical/mobyproject buildkit
• package-manager/go