Описание
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.
A flaw was found in the moby buildkit. When a build is performed under specific conditions where credentials were passed to BuildKit, it may be visible to everyone with access to provenance attestation.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| OpenShift Serverless | openshift-serverless-1/client-kn-rhel8 | Not affected | ||
| Red Hat OpenShift Container Platform 4 | openshift4/oc-mirror-plugin-rhel9 | Not affected | ||
| Red Hat OpenShift Container Platform 4 | openshift4/ose-tools-rhel8 | Not affected | ||
| Red Hat Quay 3 | quay/quay-builder-rhel8 | Not affected | ||
| Red Hat OpenShift Container Platform 4.13 | openshift4/ose-docker-builder | Fixed | RHSA-2023:3537 | 13.06.2023 |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | openshift-service-mesh/grafana-rhel8 | Fixed | RHSA-2023:5952 | 19.10.2023 |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | openshift-service-mesh/istio-cni-rhel8 | Fixed | RHSA-2023:5952 | 19.10.2023 |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | openshift-service-mesh/istio-must-gather-rhel8 | Fixed | RHSA-2023:5952 | 19.10.2023 |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | openshift-service-mesh/istio-rhel8-operator | Fixed | RHSA-2023:5952 | 19.10.2023 |
| Red Hat OpenShift Service Mesh 2.4 for RHEL 8 | openshift-service-mesh/kiali-rhel8 | Fixed | RHSA-2023:5952 | 19.10.2023 |
Показывать по
Дополнительная информация
Статус:
6.5 Medium
CVSS3
Связанные уязвимости
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 visib...
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
Buildkit credentials inlined to Git URLs could end up in provenance attestation
6.5 Medium
CVSS3