← Übersicht Nicht im beobachteten Stack

Credentials inlined to Git URLs could end up in provenance attestation in BuildKit

CVE-2023-26054 · ALPINE-CVE-2023-26054 · GHSA-gc89-7gcr-jxqc · UBUNTU-CVE-2023-26054

Mittel · CVSS 6.5 Ubuntu: mediumRed Hat: Moderate Netzwerk · ohne Login · Nutzerinteraktion Kein Fix bekannt

Veröffentlicht
06.03.2023
Zuletzt geändert
03.11.2026
EPSS (30 Tage)
1.0 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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`.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 2 behoben, 4 nicht betroffen.

RHOSSM 2.4 for RHEL 8 Behoben openshift-service-mesh/grafana-rhel8, openshift-service-mesh/istio-cni-rhel8, openshift-service-mesh/istio-must-gather-rhel8, openshift-service-mesh/istio-rhel8-operator, openshift-service-mesh/kiali-rhel8, openshift-service-mesh/kiali-rhel8-operator, openshift-service-mesh/pilot-rhel8, openshift-service-mesh/proxyv2-rhel8, openshift-service-mesh/ratelimit-rhel8 RHSA-2023:5952
Red Hat OpenShift Container Platform 4.13 Behoben openshift4/ose-docker-builder RHSA-2023:3537
Nicht betroffen (4)
OpenShift ServerlessNicht betroffenverwundbarer Code nicht enthaltenopenshift-serverless-1/client-kn-rhel8
Red Hat OpenShift Container Platform 4Nicht betroffenverwundbarer Code nicht enthaltenopenshift4/oc-mirror-plugin-rhel9, openshift4/ose-tools-rhel9
Red Hat OpenShift Container Platform 4.13Nicht betroffenverwundbarer Code nicht enthaltenopenshift4/driver-toolkit-rhel9, openshift4/network-tools-rhel8, openshift4/oc-mirror-plugin-rhel8, openshift4/openshift-route-controller-manager-rhel8, openshift4/ose-agent-installer-api-server-rhel8, openshift4/ose-agent-installer-csr-approver-rhel8, openshift4/ose-aws-ebs-csi-driver-rhel8, openshift4/ose-aws-pod-identity-webhook-rhel8, openshift4/ose-azure-cloud-controller-manager-rhel8, openshift4/ose-azure-cloud-node-manager-rhel8, openshift4/ose-baremetal-installer-rhel8, openshift4/ose-cli, openshift4/ose-cli-artifacts, openshift4/ose-cloud-credential-operator, openshift4/ose-cluster-cloud-controller-manager-operator-rhel8, openshift4/ose-cluster-ingress-operator, openshift4/ose-cluster-monitoring-operator, openshift4/ose-cluster-network-operator, openshift4/ose-cluster-node-tuning-operator, openshift4/ose-cluster-update-keys, openshift4/ose-console, openshift4/ose-csi-driver-shared-resource-rhel8, openshift4/ose-csi-driver-shared-resource-webhook-rhel8, openshift4/ose-deployer, openshift4/ose-gcp-cloud-controller-manager-rhel8 und 24 weitere
Red Hat Quay 3Nicht betroffenverwundbarer Code nicht enthaltenquay/quay-builder-rhel8
Weitere betroffene Pakete (12)
Alpine:v3.18docker23.0.2-r0ALPINE-CVE-2023-26054
Alpine:v3.19docker23.0.2-r0ALPINE-CVE-2023-26054
Alpine:v3.20docker23.0.2-r0ALPINE-CVE-2023-26054
Alpine:v3.21docker23.0.2-r0ALPINE-CVE-2023-26054
Alpine:v3.22docker23.0.2-r0ALPINE-CVE-2023-26054
Alpine:v3.23docker23.0.2-r0ALPINE-CVE-2023-26054
Alpine:v3.24docker23.0.2-r0ALPINE-CVE-2023-26054
CVEmoby/buildkitkein Fix bekanntCVE-2023-26054
Gogithub.com/moby/buildkit0.10.0 → 0.11.4GHSA-gc89-7gcr-jxqc
NVDmobyproject:buildkit0.10.0 → 0.11.4CVE-2023-26054
Ubuntu:20.04:LTSdocker.io-app24.0.5-0ubuntu1~20.04.1UBUNTU-CVE-2023-26054
Ubuntu:22.04:LTSdocker.io-app24.0.5-0ubuntu1~22.04.1UBUNTU-CVE-2023-26054

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login · Nutzerinteraktion) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.