Vulnerabilities · 2023 · Golang
CVE-2023-45287
Golang Go vulnerability
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
Go. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Golang Go runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- pkg.go.dev/vuln/GO-2023-2375 · Vendor Advisory
- people.redhat.com/~hkario/marvin/ · Third Party Advisory
- go.dev/cl/326012/26
- go.dev/issue/20654
- groups.google.com/g/golang-announce/c/QMK8IQALDvA
- security.netapp.com/advisory/ntap-20240112-0005/
- nvd.nist.gov/vuln/detail/CVE-2023-45287
- cve.org/CVERecord?id=CVE-2023-45287
More vulnerabilities in Golang products
CVE-2026-42506CVE-2026-42502CVE-2026-27136CVE-2026-25681CVE-2026-25680CVE-2025-68121CVE-2025-68119CVE-2025-61732All 172
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.