Not rated
CVE-2023-45287 Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time
Description
Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| crypto/tls 1.20 | earliest → < 1.20.0 | 1.20.0 |
References
- go.dev go.dev
- go.dev go.dev
- groups.google.com groups.google.com
- people.redhat.com people.redhat.com
- pkg.go.dev pkg.go.dev
- security.netapp.com security.netapp.com
Timeline
- Published
- Last modified
Other CVEs of crypto/tls
The 13 CVEs of crypto/tls →
CVE-2026-97031
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted…
7.5
High
CVE-2026-56862
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has…
7.5
High
CVE-2026-42505
Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of…
5.3
Medium
CVE-2026-32283
If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection…
7.5
High