Bug 1217842 (CVE-2023-45287) - VUL-0: CVE-2023-45287: go,go1.19,go1.20,go1.21: RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective
Summary: VUL-0: CVE-2023-45287: go,go1.19,go1.20,go1.21: RSA blinding was applied to p...
Status: RESOLVED FIXED
Alias: CVE-2023-45287
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/387155/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-06 08:45 UTC by SMASH SMASH
Modified: 2023-12-06 10:50 UTC (History)
1 user (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2023-12-06 08:45:09 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-45287
Comment 1 Alexander Bergmann 2023-12-06 10:50:05 UTC
This issue was already fixed within previous releases.

Closing bug as fixed.