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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Go standard library | crypto/tls | < 1.20.0 |
References
- https://go.dev/cl/326012/26Issue Tracking
- https://go.dev/issue/20654Issue Tracking
- https://groups.google.com/g/golang-announce/c/QMK8IQALDvAMailing List, Release Notes
- https://people.redhat.com/~hkario/marvin/Third Party Advisory
- https://pkg.go.dev/vuln/GO-2023-2375Vendor Advisory
- https://security.netapp.com/advisory/ntap-20240112-0005/
- https://go.dev/cl/326012/26Issue Tracking
- https://go.dev/issue/20654Issue Tracking
- https://groups.google.com/g/golang-announce/c/QMK8IQALDvAMailing List, Release Notes
- https://people.redhat.com/~hkario/marvin/Third Party Advisory
- https://pkg.go.dev/vuln/GO-2023-2375Vendor Advisory
- https://security.netapp.com/advisory/ntap-20240112-0005/
Timeline
- Published
- Dec 5, 2023
- Last modified
- Jun 17, 2026
- NVD status
- Modified