CVE-2023-45287: Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channel
Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channel
Other sources
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.
— MITRE
Golang Go could allow a remote attacker to obtain sensitive information, caused by a timing-side channel attack in the RSA based key exchange methods in crypto/tls. The removal of of PKCS#1 padding could allow a remote attacker to leak timing information, which in turn could be used to recover session key bits.
— IBM
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2023-45287?
CVE-2023-45287 has been classified as a moderate severity vulnerability due to potential timing attack risks.
How do I fix CVE-2023-45287?
To fix CVE-2023-45287, upgrade to Go version 1.20 or later.
Which software is affected by CVE-2023-45287?
CVE-2023-45287 affects IBM Concert Software versions up to 1.0.1 and Go versions earlier than 1.20.
What are the potential impacts of CVE-2023-45287?
The potential impact of CVE-2023-45287 involves the possibility of exposing sensitive information through timing attacks.
Is CVE-2023-45287 a critical vulnerability?
CVE-2023-45287 is not categorized as a critical vulnerability but still poses significant security risks.