Update gorilla/websocket to v1.5.3 - #160
Open
ai-collaboration-app[bot] wants to merge 1 commit into
Open
Conversation
GHSA-w67g-5rqw-f597: versions below v1.5.3 derive the WebSocket frame mask key from math/rand rather than a cryptographic source. The CLI links it through k8s.io/client-go's transport/websocket and tools/remotecommand, so it is reachable from the exec path. The dependency stays indirect and the Go directive is unchanged, so release builds keep the go1.25.13 toolchain pinned by #159. Ticket: StackVista/cve-reporter#32 Finding revision: sha256:584c08ac7ac36342068919d81349c67b61457518511df9a00b23644728294094 Co-authored-by: Cve Ticket Reconciler <cve-ticket-reconciler@stackstate.invalid>
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
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.
Clears
GHSA-w67g-5rqw-f597(medium) from the publishedstackstate-cli2images:gorilla/websocketbelow v1.5.3 masks WebSocket frames with a key frommath/rand. It is linked viak8s.io/client-go'stransport/websocketandtools/remotecommand, so the exec path reaches it.Indirect-only bump; the
godirective is untouched, so release builds keep the go1.25.13 toolchain from #159.Ticket: https://github.com/StackVista/cve-reporter/issues/32
Finding revision:
sha256:584c08ac7ac36342068919d81349c67b61457518511df9a00b23644728294094Validated on a representative image built from this branch with
docker/Dockerfile.goreleaser:go test ./...all green,sts versionruns, Trivy vulnerability 0 high/critical, Trivy secret 0, Grype 0 matches. The advisory no longer appears under either Grype 0.117.0 or 0.112.0.Reviewer note — this will not clear the ticket's remaining high on its own. That row (
CVE-2026-46600onstdlib go1.25.13) is a Grype 0.112.0 false positive: the upstream range starts at 1.26.0, and Grype 0.117.0 does not report it on the same DB build. It needs a Grype bump incve-reporter, not a change here. Do not move the CLI to Go 1.26.x for it — 1.25.13 has no known stdlib advisories today, while 1.26.5 has eight.