GHSA-m4gq-fm9h-8q75
Suggest an improvement- Source
- https://github.com/advisories/GHSA-m4gq-fm9h-8q75
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2025/03/GHSA-m4gq-fm9h-8q75/GHSA-m4gq-fm9h-8q75.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-m4gq-fm9h-8q75
- Aliases
- Related
- Published
- 2025-03-17T21:27:43Z
- Modified
- 2025-03-18T18:42:17.291743Z
- Severity
-
- 4.1 (Medium) CVSS_V4 - 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 CVSS Calculator
- Summary
- buildx allows a possible credential leakage to telemetry endpoint
- Details
-
Impact
Some cache backends allow configuring their credentials by setting secrets directly as attribute values in
cache-to/cache-fromconfiguration. 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.
- Database specific
{ "nvd_published_at": "2025-03-17T20:15:13Z", "cwe_ids": [ "CWE-532" ], "severity": "MODERATE", "github_reviewed": true, "github_reviewed_at": "2025-03-17T21:27:43Z" }- References
Affected packages
Go / github.com/docker/buildx
Package
- Name
- github.com/docker/buildx
- View open source insights on deps.dev
- Purl
- pkg:golang/github.com/docker/buildx