Skip to main content

Exposure of Sensitive Information to an Unauthorized Actor


Severity Medium
Score 6.5/10


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: Invoking build directly from a URL with credentials, and 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. when building directly from Git URL, the same URL could be visible in "BuildInfo" structure which is a predecessor of Provenance attestations. 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". This vulnerability affects versions 0.11.0-rc1 before 0.11.4.

  • LOW
  • NONE
  • NONE
  • HIGH
  • NONE

CWE-200 - Information Exposure

An information exposure vulnerability is categorized as an information flow (IF) weakness, which can potentially allow unauthorized access to otherwise classified information in the application, such as confidential personal information (demographics, financials, health records, etc.), business secrets, and the application's internal environment.

Advisory Timeline

  • Published