CVE-2023-45287HighMicrosoft CVSS 7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Microsoft security update for CVE-2023-45287

Published
September 3, 2025
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-45287. This page also shows what EchelonGraph holds for CVE-2023-45287, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products7

  • azl3 golang 1.20.0-1 on Azure Linux 3.0
  • azl3 golang 1.27.0-1 on Azure Linux 3.0
  • cbl2 golang 1.17.13-2 on CBL Mariner 2.0
  • cbl2 golang 1.18.8-7 on CBL Mariner 2.0
  • cbl2 golang 1.20.0-1 on CBL Mariner 2.0
  • cbl2 golang 1.21.6-1 on CBL Mariner 2.0
  • cbl2 msft-golang 1.20.0-1 on CBL Mariner 2.0

✅ Updates Microsoft lists: 4 updates

4 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—
—Security Update1.21.6-1
—Security Update1.20.0-1
—Security Update—

🧭 EchelonGraph on CVE-2023-45287

EchelonGraph score
7.5 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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.

Published by Go Project, the CVE Numbering Authority that assigned CVE-2023-45287, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)