-
Notifications
You must be signed in to change notification settings - Fork 266
crypto: clarify TLS cipher mapping and rename internal maps #2325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
b5ddf21
Bump openshift/api and openshift/client-go
jubittajohn baafe22
Handle TLS profile ciphers unsupported by Go's crypto/tls
jubittajohn 2ef05f5
crypto: clarify cipher mapping documentation and co-locate skip list
sanchezl 5db4427
crypto: rename unexported maps for clarity
sanchezl 54252a6
crypto: rename TLS version maps for clarity
sanchezl b4c85f9
crypto: log silently dropped ciphers at V(4)
sanchezl File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
Are there any known CVEs in golang.org/x/crypto v0.48.0, golang.org/x/net v0.50.0, and golang.org/x/sys v0.41.0?💡 Result:
Yes. 1) golang.org/x/crypto v0.48.0 There are multiple Go security advisories listed for this exact version (as OSV entries): GO-2026-5005, GO-2026-5006, GO-2026-5013, GO-2026-5014, GO-2026-5015, GO-2026-5016, GO-2026-5017, GO-2026-5018, GO-2026-5019, GO-2026-5020, GO-2026-5021, GO-2026-5023, and GO-2026-5033.[1] 2) golang.org/x/net v0.50.0 There is at least one known CVE: CVE-2026-27141 (OSV: GO-2026-4559), which affects golang.org/x/net/http2 in the range 0.50.0 (and before 0.51.0). It is described as a server panic issue triggered by sending certain HTTP/2 frames due to a missing nil check.[2][3] 3) golang.org/x/sys v0.41.0 There is at least one known CVE: OSV entry GO-2026-5024 is listed for golang.org/x/sys v0.41.0, and the OSV record is aliased to CVE-2026-39824.[4][5] If you want, I can enumerate the specific CVEs behind each GO-xxxx advisory for golang.org/x/crypto v0.48.0 as well (the pkg.go.dev page lists the GO-ids, and you’d typically map those to CVEs via each OSV record).
Citations:
🏁 Script executed:
Repository: openshift/library-go
Length of output: 50377
Do not merge: critical CVEs in security-sensitive dependencies.
golang.org/x/net v0.50.0 contains CVE-2026-27141 (HTTP/2 server panic due to missing nil check), golang.org/x/sys v0.41.0 contains CVE-2026-39824, and golang.org/x/crypto v0.48.0 is affected by multiple known Go security advisories (GO-2026-5005, GO-2026-5006, GO-2026-5013, GO-2026-5014, GO-2026-5015, GO-2026-5016, GO-2026-5017, GO-2026-5018, GO-2026-5019, GO-2026-5020, GO-2026-5021, GO-2026-5023, GO-2026-5033). These versions must be updated to release patches or explicitly justified if usage context mitigates the risk.
🤖 Prompt for AI Agents