BuildKit is a toolkit for converting source code to build artifacts in an
efficient, expressive and repeatable manner. In affected versions 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: 1) Invoking build directly from a URL with credentials. 2) If the client
sends additional version control system (VCS) info hint parameters on builds
from a local source. Usually, that would mean reading the origin URL from
`.git/config` file. 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. This bug has been fixed in v0.11.4. Users are
advised to upgrade. Users unable to upgrade may disable VCS info hints 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`.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-26054
https://bugzilla.redhat.com/show_bug.cgi?id=2176447
https://www.cve.org/CVERecord?id=CVE-2023-26054
https://github.com/moby/buildkit/commit/75123c696506bdbca1ed69906479e200f1b62604
https://github.com/moby/buildkit/security/advisories/GHSA-gc89-7gcr-jxqc