Skip to content
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

update: go #1149

Closed
dongsupark opened this issue Aug 3, 2023 · 0 comments · Fixed by flatcar/scripts#1041
Closed

update: go #1149

dongsupark opened this issue Aug 3, 2023 · 0 comments · Fixed by flatcar/scripts#1041
Labels
advisory security advisory security security concerns

Comments

@dongsupark
Copy link
Member

Name: go
CVEs: CVE-2023-29409
CVSSs: n/a
Action Needed: update to >= 1.20.7 or >= 1.19.12

Summary: Extremely large RSA keys in certificate chains can cause a client/server to expend significant CPU time verifying signatures. With fix, the size of RSA keys transmitted during handshakes is restricted to <= 8192 bits. Based on a survey of publicly trusted RSA keys, there are currently only three certificates in circulation with keys larger than this, and all three appear to be test certificates that are not actively deployed. It is possible there are larger keys in use in private PKIs, but we target the web PKI, so causing breakage here in the interests of increasing the default safety of users of crypto/tls seems reasonable.

See also https://groups.google.com/g/golang-announce/c/X0b6CsSAaYI.

refmap.gentoo: TBD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advisory security advisory security security concerns
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant