First published: Mon Mar 17 2025(Updated: )
### 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.
Credit: security@docker.com
Affected Software | Affected Version | How to fix |
---|---|---|
Docker Buildx | ||
go/github.com/docker/buildx | <=0.21.2 | 0.21.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-0495 is classified as a medium severity vulnerability affecting Docker Buildx.
To fix CVE-2025-0495, update Docker Buildx to the latest version that addresses this vulnerability.
CVE-2025-0495 specifically affects Docker Buildx, which is a CLI plugin for Docker.
The potential risks of CVE-2025-0495 include exposure of sensitive credentials through user input in cache configurations.
As a workaround for CVE-2025-0495, avoid using user input for sensitive attributes in cache-to/cache-from configurations.