Ecosyste.ms: Advisories

Security Advisories: GSA_kwCzR0hTQS13cjZ2LTlmNzUtdmgyZ84AA4-q

Buildkit's interactive containers API does not validate entitlements check

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

Permalink: https://github.com/advisories/GHSA-wr6v-9f75-vh2g
JSON: https://advisories.ecosyste.ms/api/v1/advisories/GSA_kwCzR0hTQS13cjZ2LTlmNzUtdmgyZ84AA4-q
Source: GitHub Advisory Database
Origin: Unspecified
Severity: Critical
Classification: General
Published: 10 months ago
Updated: 6 months ago

CVSS Score: 9.8
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Identifiers: GHSA-wr6v-9f75-vh2g, CVE-2024-23653
References:

• https://github.com/moby/buildkit/security/advisories/GHSA-wr6v-9f75-vh2g
• https://github.com/moby/buildkit/pull/4602
• https://nvd.nist.gov/vuln/detail/CVE-2024-23653
• https://github.com/moby/buildkit/releases/tag/v0.12.5
• https://github.com/moby/buildkit/commit/5026d95aa3336e97cfe46e3764f52d08bac7a10e
• https://github.com/moby/buildkit/commit/92cc595cfb12891d4b3ae476e067c74250e4b71e
• https://github.com/advisories/GHSA-wr6v-9f75-vh2g

Repository: https://github.com/moby/buildkit
Blast Radius: 30.0

Affected Packages