🛡️ AZL-79088 — golang
Description
CVE-2023-45287 affecting package golang 1.25.7-1
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.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.
Affected software
AZL-79088 is recorded against 1 package.
- golang
Timeline and source
Published on 5 December 2023 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| golang | — | — |
References
Similar Threats
- Unknown ALSA-2024:2562
- Unknown ALSA-2024:1963
- Unknown ALSA-2024:1962
- Unknown ALSA-2024:1462
- Unknown ALSA-2024:1472
More AZL 7 advisories
Browse all of AZL 7 in the advisory index.
Free Vulnerability Check
Is your site affected by AZL-79088?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-79088 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.