Microsoft security update for CVE-2023-45283
🔗 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-45283. This page also shows what EchelonGraph holds for CVE-2023-45283, 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 products6
- azl3 golang 1.23.9-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.21.6-1 on CBL Mariner 2.0
- cbl2 msft-golang 1.20.11-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 article | Update | Fixed build |
|---|---|---|
| — | Security Update | — |
| — | Security Update | 1.21.6-1 |
| — | Security Update | 1.20.11-1 |
| — | Security Update | — |
🧭 EchelonGraph on CVE-2023-45283
- 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
The filepath package does not recognize paths with a \??\ prefix as special. On Windows, a path beginning with \??\ is a Root Local Device path equivalent to a path beginning with \\?\. Paths with a \??\ prefix may be used to access arbitrary locations on the system. For example, the path \??\c:\x is equivalent to the more common path c:\x. Before fix, Clean could convert a rooted path such as \a\..\??\b into the root local device path \??\b. Clean will now convert this to .\??\b. Similarly, Join(\, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path \??\b. Join will now convert this to \.\??\b. In addition, with fix, IsAbs now correctly reports paths beginning with \??\ as absolute, and VolumeName correctly reports the \??\ prefix as a volume name. UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with \?, resulting in filepath.Clean(\?\c:) returning \?\c: rather than \?\c:\ (among other effects). The previous behavior has been restored.
Published by Go Project, the CVE Numbering Authority that assigned CVE-2023-45283, 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).