CVE-2022-30629: Session tickets lack random ticket_age_add in crypto/tls
A flaw was found in the crypto/tls golang package. When session tickets are generated by crypto/tls, it is missing the ticket expiration. This issue may allow an attacker to observe the TLS handshakes to correlate successive connections during session resumption.
Other sources
Golang Go could allow a remote attacker to obtain sensitive information, caused by an issue with session tickets generated by crypto/tls did not contain a randomly generated ticketageadd. By comparing ticket ages during session resumption, an attacker could exploit this vulnerability to observe TLS handshakes information to correlate successive connections.
— IBM
Non-random values for ticketageadd in session tickets in crypto/tls before Go 1.17.11 and Go 1.18.3 allow an attacker that can observe TLS handshakes to correlate successive connections by comparing ticket ages during session resumption.
Session tickets lack random ticketageadd in crypto/tls
— Microsoft
We have just released Go versions 1.18.3 and 1.17.11, minor point releases.
crypto/tls: session tickets lack random ticketageadd
Session tickets generated by crypto/tls did not contain a randomly generated ticketageadd. This allows an attacker that can observe TLS handshakes to correlate successive connections by comparing ticket ages during session resumption.
References: https://go.dev/issue/52814 https://groups.google.com/g/golang-announce/c/TzIC9-t8Ytg
Upstream Commits: Master : https://github.com/golang/go/commit/fe4de36198794c447fbd9d7cc2d7199a506c76a5 Branch.go1.17 : https://github.com/golang/go/commit/c15a8e2dbb5ac376a6ed890735341b812d6b965c Branch.go1.18 : https://github.com/golang/go/commit/c838098c327a1b6d63446f4722e943b02d235d78
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
- RHSA-2022:6345
- RHSA-2022:6430
- RHSA-2022:6290
- RHSA-2022:6040
- RHSA-2022:6042
- RHSA-2022:6277
- RHSA-2022:6152
- RHSA-2022:6348
- RHSA-2022:6346
- RHSA-2022:6347
- RHSA-2022:6370
- RHSA-2023:0630
- RHSA-2023:3642
- RHSA-2022:5866
- RHSA-2022:5775
- RHSA-2023:2758
- RHSA-2022:5799
- RHSA-2023:2253
- RHSA-2023:2282
- RHSA-2023:2283
- RHSA-2023:2367
- RHSA-2022:9047
- RHSA-2022:6102
- RHSA-2022:6103
- RHSA-2022:6535
- RHSA-2023:3914
- RHSA-2023:4488
- RHSA-2023:1275
- RHSA-2023:0407
- RHSA-2022:8750
- RHSA-2023:0408
- RHSA-2023:1529
- IBM-7173596
Frequently Asked Questions
What is CVE-2022-30629?
CVE-2022-30629 is a vulnerability that affects the crypto/tls package in Go versions before 1.17.11 and 1.18.3.
How does CVE-2022-30629 impact the affected software?
CVE-2022-30629 allows an attacker to observe TLS handshakes and correlate successive connections during session resumption.
What is the severity of CVE-2022-30629?
CVE-2022-30629 has a severity rating of 3.1 (low).
What is the remedy for CVE-2022-30629?
The remedy for CVE-2022-30629 is to update to Go versions 1.17.11 or 1.18.3.
Where can I find more information about CVE-2022-30629?
You can find more information about CVE-2022-30629 at the following references: [Link 1](https://go.dev/issue/52814), [Link 2](https://groups.google.com/g/golang-announce/c/TzIC9-t8Ytg), [Link 3](https://github.com/golang/go/commit/fe4de36198794c447fbd9d7cc2d7199a506c76a5).