CVE-2025-0495

ADVISORY - github

Summary

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.

EPSS Score: 0.00039 (0.119)

Common Weakness Enumeration (CWE)

ADVISORY - nist

Insertion of Sensitive Information into Log File

ADVISORY - github

Insertion of Sensitive Information into Log File

ADVISORY - gitlab

OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities

Insertion of Sensitive Information into Log File

OWASP Top Ten 2013 Category A9 - Using Components with Known Vulnerabilities


Sign in to Docker Scout

See which of your images are affected by this CVE and how to fix them by signing into Docker Scout.

Sign in