CVE-2025-0495 – github.com/docker/buildx

Package

Manager: go
Name: github.com/docker/buildx
Vulnerable Version: >=0 <0.21.3

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C

CVSS v4.0: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N

EPSS: 0.00029 pctl0.06747

Details

buildx allows a possible credential leakage to telemetry endpoint ### Impact Some cache backends allow configuring their credentials by setting secrets directly as attribute values in `cache-to/cache-from` configuration. If this was done by the user, these secure values could be captured together with OpenTelemetry trace as part of the arguments and flags for the traced CLI command. Passing tokens to Github cache backend via environment variables or using registry authentication is not affected. If you passed a token value like this and use a custom OpenTelemetry collector for computing traces you should make sure that your traces are kept secure. OpenTelemetry traces are also saved in BuildKit daemon's history records. ### Patches Issue has been fixed in Buildx v0.21.3 or newer. ### Workarounds Avoid passing cache backend credentials with CLI arguments. Make sure access to traces and BuildKit history records is kept secure.

Metadata

Created: 2025-03-17T21:27:43Z
Modified: 2025-03-17T21:51:49Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/03/GHSA-m4gq-fm9h-8q75/GHSA-m4gq-fm9h-8q75.json
CWE IDs: ["CWE-532"]
Alternative ID: GHSA-m4gq-fm9h-8q75
Finding: F200
Auto approve: 1