| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/moby/buildkit | ≥ 0.10.0, < 0.11.4 | 0.11.4 |
| buildkit | ≥ 0.10.0, < 0.11.4 | 0.11.4 |
When the user sends a build request that contains a Git URL that contains credentials and the build creates a provenance attestation describing that build, these credentials could be visible from the provenance attestation.
Git URL can be passed in two ways:
buildctl build --frontend dockerfile.v0 --context https://<credentials>@url/repo.git
Equivalent in docker buildx would be
docker buildx build https://<credentials>@url/repo.git
.git/config file.Thanks to Oscar Alberto Tovar for discovering the issue.
When a build is performed under specific conditions where credentials were passed to BuildKit they may be visible to everyone who has access to provenance attestation.
Provenance attestations and VCS info hints were added in version v0.11.0. Previous versions are not vulnerable.
In v0.10, when building directly from Git URL, the same URL could be visible in BuildInfo structure that is a predecessor of Provenance attestations. Previous versions are not vulnerable.
Note: Docker Build-push Github action builds from Git URLs by default but affected by this issue even when working with private repositories because the credentials are passed and not with URLs.
Bug is fixed in v0.11.4 .
It is recommended to pass credentials with build secrets when building directly from Git URL as a more secure alternative than modifying the URL.
In Docker Buildx, VCS info hint can be disabled by setting BUILDX_GIT_INFO=0. buildctl does not set VCS hints based on .git directory, and values would need to be passed manually with --opt.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free