GHSA-wr6v-9f75-vh2g

Buildkit's interactive containers API does not validate entitlements check

At a glance

Published
Updated
CVE
CVE-2024-23653
Aliases
GO-2024-2497
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

Affected packages

PackageVersions
Go · github.com/moby/buildkitintroduced 0, fixed 0.12.5

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database