crypto/tls: large handshake records may cause panics (CVE-2022-41724)

[rolandshoemaker]

Both clients and servers may send large TLS handshake records which cause servers and clients,
respectively, to panic when attempting to construct responses.

This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption
(by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request
client certificates (by setting Config.ClientAuth >= RequestClientCert).

Thanks to Marten Seemann for reporting this issue.

This is a PRIVATE issue for CVE-2022-41724, tracked in http://b/261456191 and fixed by http://tg/1679436.

/cc @golang/security and @golang/release

[rolandshoemaker]

@gopherbot please open backport issues.

[gopherbot]

Backport issue(s) opened: #58358 (for 1.19), #58359 (for 1.20).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases.

[gopherbot]

Change https://go.dev/cl/468125 mentions this issue: crypto/tls: replace all usages of BytesOrPanic

[gopherbot]

Change https://go.dev/cl/468121 mentions this issue: [release-branch.go1.20] crypto/tls: replace all usages of BytesOrPanic

[gopherbot]

Change https://go.dev/cl/468117 mentions this issue: [release-branch.go1.19] crypto/tls: replace all usages of BytesOrPanic