CVE-2023-26054: Infoleak
First published: Mon Mar 06 2023(Updated: )
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://<credentials>@url/repo.git ``` Equivalent in `docker buildx` would be ``` docker buildx build https://<credentials>@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. ### Impact 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](https://github.com/docker/build-push-action) builds from Git URLs by default but **is not** affected by this issue even when working with private repositories because the credentials are passed [with build secrets](https://github.com/docker/build-push-action/blob/v4.0.0/src/context.ts#L203) and not with URLs. ### Patches Bug is fixed in v0.11.4 . ### Workarounds 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`. ### References - Inline credentials in URLs deprecated in RFC3986 https://www.rfc-editor.org/rfc/rfc3986#section-3.2.1
Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Mobyproject Buildkit | >=0.10.0<0.11.4 | |
| go/github.com/moby/buildkit | >=0.10.0<0.11.4 | 0.11.4 |
| redhat/buildkit | <0.11.4 | 0.11.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/moby/buildkit/security/advisories/GHSA-gc89-7gcr-jxqc
- https://nvd.nist.gov/vuln/detail/CVE-2023-26054
- https://github.com/moby/buildkit/commit/75123c696506bdbca1ed69906479e200f1b62604
- https://www.rfc-editor.org/rfc/rfc3986#section-3.2.1
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LYZOKMMVX4SIEHPJW3SJUQGMO5YZCPHC/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZTE4ITXXPIWZEQ4HYQCB6N6GZIMWXDAI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XNF4OLYZRQE75EB5TW5N42FSXHBXGWFE/
- https://github.com/advisories/GHSA-gc89-7gcr-jxqc (Advisory)
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2176448
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2177587
- https://access.redhat.com/errata/RHSA-2023:3537
- https://access.redhat.com/security/cve/cve-2023-26054
- https://access.redhat.com/errata/RHSA-2023:5952
- https://bugzilla.redhat.com/show_bug.cgi?id=2176447
Frequently Asked Questions
What is CVE-2023-26054?
CVE-2023-26054 is a vulnerability that allows credentials passed in Git URLs to be visible in the provenance attestation.
How does CVE-2023-26054 affect BuildKit?
CVE-2023-26054 affects BuildKit by allowing credentials to be exposed in the provenance attestation when a build request contains a Git URL with credentials.
What is the severity of CVE-2023-26054?
CVE-2023-26054 has a severity rating of 6.5 (medium).
How do I fix CVE-2023-26054 on BuildKit?
To fix CVE-2023-26054 on BuildKit, update to version 0.11.4 or higher.
Where can I find more information about CVE-2023-26054?
You can find more information about CVE-2023-26054 at the following references: [GitHub Security Advisory](https://github.com/moby/buildkit/security/advisories/GHSA-gc89-7gcr-jxqc), [NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-26054), [GitHub Commit](https://github.com/moby/buildkit/commit/75123c696506bdbca1ed69906479e200f1b62604).
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/remedy
- agent/severity
- agent/softwarecombine
- agent/tags
- agent/type
- agent/weakness
- collector/github-advisory
- alias/GHSA-gc89-7gcr-jxqc
- alias/CVE-2023-26054
- collector/github-advisory-latest
- collector/nvd-api
- collector/nvd-cve
- collector/nvd-index
- collector/redhat-bugzilla
- source/Red Hat
- agent/software-canonical-lookup
- package-manager/go
- vendor/mobyproject
- canonical/mobyproject buildkit
- version/mobyproject buildkit/0.10.0
- package-manager/redhat