Vulnerability in Golang Go
CVE-2023-45287
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.013, 69.9th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Golang Go
- Go Standard Library Crypto/tls — versions 0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 6 other repositories (11notes/docker-paperless-ngx, 8-cm/kube-dump, drewtwitchell/scancompare, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- go.dev/issue/20654 (Issue Tracking)
- go.dev/cl/326012/26 (Issue Tracking)
- groups.google.com/g/golang-announce/c/QMK8IQALDvA (Mailing List, Release Notes)
- people.redhat.com/~hkario/marvin/ (Third Party Advisory)
- pkg.go.dev/vuln/GO-2023-2375 (Vendor Advisory)
- security.netapp.com/advisory/ntap-20240112-0005/