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

crypto/tls: ensure that we don't resume when tickets are disabled #53085

Closed
tatianab opened this issue May 25, 2022 · 0 comments
Closed

crypto/tls: ensure that we don't resume when tickets are disabled #53085

tatianab opened this issue May 25, 2022 · 0 comments

Comments

@tatianab
Copy link

When SessionTicketsDisabled is enabled, crypto/tls allowed man-in-the-middle
attackers to spoof clients via unspecified vectors.

If the server enables TLS client authentication using certificates (this is
rare) and explicitly sets SessionTicketsDisabled to true in the tls.Config,
then a malicious client can falsely assert ownership of any client
certificate it wishes.

This is CVE-2014-7189, fixed in Go 1.3.2 by https://go.dev/cl/148080043.
Announcement: https://groups.google.com/g/golang-nuts/c/eeOHNw_shwU/m/OHALUmroA5kJ

Issue filed retroactively for the vulnerability database.

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

No branches or pull requests

1 participant