First published: Tue Dec 05 2023(Updated: )
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.
Credit: security@golang.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/golang | <1.20 | 1.20 |
Go Programming Language | <1.20.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-45287 has been classified as a moderate severity vulnerability due to potential timing attack risks.
To fix CVE-2023-45287, upgrade to Go version 1.20 or later.
CVE-2023-45287 affects IBM Concert Software versions up to 1.0.1 and Go versions earlier than 1.20.
The potential impact of CVE-2023-45287 involves the possibility of exposing sensitive information through timing attacks.
CVE-2023-45287 is not categorized as a critical vulnerability but still poses significant security risks.