QID 356362

On unix platforms, the go runtime does not behave differently when a binary is run with the setuid/setgid bits.
This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.
If a setuid/setgid binary is executed with standard i/o file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges.
Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers. (
( CVE-2023-29403) the http/1 client does not fully validate the contents of the host header.
A maliciously crafted host header can inject additional headers or entire requests.
With fix, the http/1 client now refuses to send requests containing an invalid request.
Host or request.
Url.host value. (
( CVE-2023-29406) 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. (
( CVE-2023-29409)

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.