Connection correlation via zero-valued ticket_age_add
Published Aug 9, 2022 · Updated Mar 6, 2026
Insufficient randomness in crypto/tls before Go 1.17.11 and Go 1.18.0 through 1.18.2 allows attackers to correlate TLS connections. The serverHandshakeStateTLS13.sendSessionTickets routine writes ticket_age_add as zero instead of generating a random 32-bit value for each session ticket. The attack requires visibility into an original TLS 1.3 handshake and its resumed connection, and the consequence is linkability between those sessions.
Summary
What happened
Insufficient randomness in crypto/tls before Go 1.17.11 and Go 1.18.0 through 1.18.2 allows attackers to correlate TLS connections. The serverHandshakeStateTLS13.sendSessionTickets routine writes ticket_age_add as zero instead of generating a random 32-bit value for each session ticket. The attack requires visibility into an original TLS 1.3 handshake and its resumed connection, and the consequence is linkability between those sessions.
The record
- CVE
- CVE-2022-30629
- Published
- Aug 9, 2022
- Updated
- Mar 6, 2026
- Vendor
- Go standard library
- Product
- crypto/tls
- Classifications
- CWE-330, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2022CVE publishedPublication date reported by the CVE source.
- Mar 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.17.11
- Affected versionversion=1.18.0-0 <1.18.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo