Search for packages
| purl | pkg:golang/github.com/moby/buildkit@0.12.5 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
| This package is not known to be affected by vulnerabilities. | ||
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-9j8p-hqfn-q7bj | BuildKit vulnerable to possible host system access from mount stub cleaner ### Impact A malicious BuildKit frontend or Dockerfile using `RUN --mount` could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system. ### Patches The issue has been fixed in v0.12.5 ### Workarounds Avoid using BuildKit frontend from an untrusted source or building an untrusted Dockerfile containing `RUN --mount` feature. ### References |
CVE-2024-23652
GHSA-4v98-7qmw-rqr8 |
| VCID-ba18-6srf-ufbu | BuildKit vulnerable to possible race condition with accessing subpaths from cache mounts ### Impact Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container. ### Patches The issue has been fixed in v0.12.5 ### Workarounds Avoid using BuildKit frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with `--mount=type=cache,source=...` options. ### References https://www.openwall.com/lists/oss-security/2019/05/28/1 |
CVE-2024-23651
GHSA-m3r6-h7wv-7xxv |
| VCID-dmsf-7cxm-xff5 | 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 |
CVE-2024-23653
GHSA-wr6v-9f75-vh2g |
| VCID-f5eu-ram7-v3fr | BuildKit vulnerable to possible panic when incorrect parameters sent from frontend ### Impact A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic. ### 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 |
CVE-2024-23650
GHSA-9p26-698r-w4hx |
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2026-04-01T12:50:03.558169+00:00 | GithubOSV Importer | Fixing | VCID-9j8p-hqfn-q7bj | https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/01/GHSA-4v98-7qmw-rqr8/GHSA-4v98-7qmw-rqr8.json | 38.0.0 |
| 2026-04-01T12:50:03.338158+00:00 | GithubOSV Importer | Fixing | VCID-ba18-6srf-ufbu | https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/01/GHSA-m3r6-h7wv-7xxv/GHSA-m3r6-h7wv-7xxv.json | 38.0.0 |
| 2026-04-01T12:50:01.449326+00:00 | GithubOSV Importer | Fixing | VCID-f5eu-ram7-v3fr | https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/01/GHSA-9p26-698r-w4hx/GHSA-9p26-698r-w4hx.json | 38.0.0 |
| 2026-04-01T12:49:58.886006+00:00 | GithubOSV Importer | Fixing | VCID-dmsf-7cxm-xff5 | https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/01/GHSA-wr6v-9f75-vh2g/GHSA-wr6v-9f75-vh2g.json | 38.0.0 |