CVE-2023-26054
published 2023-03-06CVE-2023-26054: 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…
PriorityP433medium6.5CVSS 3.1
AVNACLPRNUIRSUCHINAN
EPSS
1.03%
59.3th percentile
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`.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | moby_buildkit | >= 0.10.0 < 0.11.4 | 0.11.4 |
| moby | buildkit | — | — |
| mobyproject | buildkit | >= 0.10.0 < 0.11.4 | 0.11.4 |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
osv6.5MEDIUM
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Buildkit credentials inlined to Git URLs could end up in provenance attestation
ghsa·2023-03-07
CVE-2023-26054 [MEDIUM] CWE-200 Buildkit credentials inlined to Git URLs could end up in provenance attestation
Buildkit credentials inlined to Git URLs could end up in provenance attestation
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.
```
buildctl build --frontend dockerfile.v0 --context https://@url/repo.git
```
Equivalent in `docker buildx` would be
```
docker buildx build https://@url/repo.git
```
2) If the client sends additional VCS info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from `.git/config` file.
Thanks to Oscar Alberto Tovar for discovering the issue.
### Imp
OSV
Buildkit credentials inlined to Git URLs could end up in provenance attestation
osv·2023-03-07
CVE-2023-26054 [MEDIUM] Buildkit credentials inlined to Git URLs could end up in provenance attestation
Buildkit credentials inlined to Git URLs could end up in provenance attestation
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.
```
buildctl build --frontend dockerfile.v0 --context https://@url/repo.git
```
Equivalent in `docker buildx` would be
```
docker buildx build https://@url/repo.git
```
2) If the client sends additional VCS info hint parameters on builds from a local source. Usually, that would mean reading the origin URL from `.git/config` file.
Thanks to Oscar Alberto Tovar for discovering the issue.
### Imp
OSV
CVE-2023-26054: BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner
osv·2023-03-06·CVSS 6.5
CVE-2023-26054 [MEDIUM] CVE-2023-26054: BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner
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 at
Red Hat
buildkit: Data disclosure in provenance attestation describing a build
vendor_redhat·2023-03-06·CVSS 6.5
CVE-2023-26054 [MEDIUM] CWE-200 buildkit: Data disclosure in provenance attestation describing a build
buildkit: Data disclosure in provenance attestation describing a build
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
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/moby/buildkit/commit/75123c696506bdbca1ed69906479e200f1b62604https://github.com/moby/buildkit/security/advisories/GHSA-gc89-7gcr-jxqchttps://lists.fedoraproject.org/archives/list/[email protected]/message/LYZOKMMVX4SIEHPJW3SJUQGMO5YZCPHC/https://lists.fedoraproject.org/archives/list/[email protected]/message/XNF4OLYZRQE75EB5TW5N42FSXHBXGWFE/https://lists.fedoraproject.org/archives/list/[email protected]/message/ZTE4ITXXPIWZEQ4HYQCB6N6GZIMWXDAI/https://github.com/moby/buildkit/commit/75123c696506bdbca1ed69906479e200f1b62604https://github.com/moby/buildkit/security/advisories/GHSA-gc89-7gcr-jxqchttps://lists.fedoraproject.org/archives/list/[email protected]/message/LYZOKMMVX4SIEHPJW3SJUQGMO5YZCPHC/https://lists.fedoraproject.org/archives/list/[email protected]/message/XNF4OLYZRQE75EB5TW5N42FSXHBXGWFE/https://lists.fedoraproject.org/archives/list/[email protected]/message/ZTE4ITXXPIWZEQ4HYQCB6N6GZIMWXDAI/
2023-03-06
Published