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.

Sign up for GitHub

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

Jump to bottom

security: fix CVE-2023-29409 [1.19 backport] #61579

Closed
gopherbot opened this issue Jul 25, 2023 · 2 comments
Closed

security: fix CVE-2023-29409 [1.19 backport] #61579

gopherbot opened this issue Jul 25, 2023 · 2 comments
Labels
CherryPickApproved Used during the release process for point releases FrozenDueToAge release-blocker Security
Milestone
Go1.19.12

Comments

@gopherbot
Copy link
Contributor

@neild requested issue #61460 to be considered for backport to the next 1.19 minor release.

@gopherbot please open backport issues
@gopherbot gopherbot added CherryPickCandidate Used during the release process for point releases Security labels Jul 25, 2023
@gopherbot gopherbot mentioned this issue Jul 25, 2023
Closed
@gopherbot gopherbot added this to the Go1.19.12 milestone Jul 25, 2023
@gopherbot
Copy link
Contributor Author

Change https://go.dev/cl/514915 mentions this issue: [release-branch.go1.19] crypto/tls: restrict RSA keys in certificates to <= 8192 bits

gopherbot pushed a commit that referenced this issue Aug 1, 2023
@rolandshoemaker @dr2chase
[release-branch.go1.19] crypto/tls: restrict RSA keys in certificates…
2300f7e 
… to <= 8192 bits

Extremely large RSA keys in certificate chains can cause a client/server
to expend significant CPU time verifying signatures. Limit this by
restricting the size of RSA keys transmitted during handshakes 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.

Thanks to Mateusz Poliwczak for reporting this issue.

Updates #61460
Fixes #61579
Fixes CVE-2023-29409

Change-Id: Ie35038515a649199a36a12fc2c5df3af855dca6c
Reviewed-on: https://team-review.git.corp.google.com/c/golang/go-private/+/1912161
Reviewed-by: Damien Neil <[email protected]>
Reviewed-by: Tatiana Bradley <[email protected]>
Run-TryBot: Roland Shoemaker <[email protected]>
(cherry picked from commit d865c715d92887361e4bd5596e19e513f27781b7)
Reviewed-on: https://team-review.git.corp.google.com/c/golang/go-private/+/1965487
Reviewed-on: https://go-review.googlesource.com/c/go/+/514915
Run-TryBot: David Chase <[email protected]>
Reviewed-by: Matthew Dempsky <[email protected]>
TryBot-Bypass: David Chase <[email protected]>
@gopherbot
Copy link
Contributor Author

Closed by merging 2300f7e to release-branch.go1.19.

@dr2chase dr2chase added the CherryPickApproved Used during the release process for point releases label Aug 1, 2023
@gopherbot gopherbot removed the CherryPickCandidate Used during the release process for point releases label Aug 1, 2023
@golang golang locked and limited conversation to collaborators Jul 31, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
CherryPickApproved Used during the release process for point releases FrozenDueToAge release-blocker Security
Projects
None yet
Milestone
Go1.19.12
Development

No branches or pull requests
3 participants
@neild @dr2chase @gopherbot