CVE-2023-45287: Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channel

Published Dec 5, 2023
·
Updated

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

8 affected componentsFixes available
Golang Go<1.20.0
redhat/golang<1.20
1.20
Microsoft cbl2 golang 1.18.8-7
Microsoft azl3 golang 1.20.0-1
Microsoft cbl2 msft-golang 1.20.0-1
Microsoft cbl2 golang 1.21.6-1
Microsoft cbl2 golang 1.20.0-1
Microsoft cbl2 golang 1.17.13-2

Event History

Dec 5, 2023
CVE Published
via MITRE·04:18 PM
Data Sourced
via MITRE·04:18 PM
DescriptionWeakness
Dec 6, 2023
Data Sourced
via Red Hat·01:50 PM
DescriptionSeverityAffected Software
Feb 4, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·04:28 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·04:28 AM
Affected Software
Updated
via Microsoft·04:28 AM
Affected Software
Updated
via Microsoft·04:28 AM
DescriptionSeverity

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

How do I fix CVE-2023-45287?

To fix CVE-2023-45287, upgrade to Go version 1.20 or later.

3

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.

4

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.

5

Is CVE-2023-45287 a critical vulnerability?

CVE-2023-45287 is not categorized as a critical vulnerability but still poses significant security risks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203