CVE-2025-0495 fix: update buildx to v0.21.3#6
Open
rcmadhankumar wants to merge 1 commit intoSUSE:suse-v2.33.1from
Open
CVE-2025-0495 fix: update buildx to v0.21.3#6rcmadhankumar wants to merge 1 commit intoSUSE:suse-v2.33.1from
rcmadhankumar wants to merge 1 commit intoSUSE:suse-v2.33.1from
Conversation
-- CVE-2025-0495: docker-compose: buildx: credential leakage to telemetry endpoints when credentials allowed to be set as attribute values in cache-to/cache-from configuration Buildx is a Docker CLI plugin that extends build capabilities using BuildKit. Cache backends support credentials by setting secrets directly as attribute values in cache-to/cache-from configuration. When supplied as user input, these secure values may be inadvertently captured in OpenTelemetry traces as part of the arguments and flags for the traced CLI command. OpenTelemetry traces are also saved in BuildKit daemon's history records. buildx v0.21.3 has the fix for the issue reference: GHSA-m4gq-fm9h-8q75 Fixes CVE-2025-0495 Fixes bsc#1239766
| default: | ||
| return nil, fmt.Errorf("agent: failed to list keys, unexpected message type %T", msg) | ||
| } | ||
| panic("unreachable") |
Member
There was a problem hiding this comment.
This is overriding changes for an existing backport; ref: bsc#1253584
| for len(constraints) != 0 { | ||
| switch constraints[0] { | ||
| case agentConstrainLifetime: | ||
| if len(constraints) < 5 { |
Member
There was a problem hiding this comment.
Same; this is also part of bsc#1253584
| if !ok { | ||
| return errors.Errorf("invalid value %s", field) | ||
| } | ||
| key = strings.TrimSpace(strings.ToLower(key)) |
Member
There was a problem hiding this comment.
Can you please check files under buildflags/ to see if they are supposed to be part of this backport? I'm using https://github.com/docker/buildx/pull/3067/commits as reference
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
--
CVE-2025-0495: docker-compose: buildx: credential leakage to telemetry endpoints when credentials allowed to be set as attribute values in cache-to/cache-from configuration
Buildx is a Docker CLI plugin that extends build capabilities using BuildKit.
Cache backends support credentials by setting secrets directly as attribute values in cache-to/cache-from configuration. When supplied as user input, these secure values may be inadvertently captured in OpenTelemetry traces as part of the arguments and flags for the traced CLI command. OpenTelemetry traces are also saved in BuildKit daemon's history records.
buildx v0.21.3 has the fix for the issue
reference: GHSA-m4gq-fm9h-8q75
Fixes CVE-2025-0495
Fixes bsc#1239766
What I did
Related issue
(not mandatory) A picture of a cute animal, if possible in relation to what you did