CVE-2023-45283: Insecure parsing of Windows paths with a \??\ prefix in path/filepath
Go standard library · path/filepath
Vendor fix available · Affected: Go standard library path/filepath · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 88% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
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.
Affected products3
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Go standard library · path/filepathbefore 1.20.11; from 1.21.0-0 before 1.21.4
- Go standard library · internal/safefilepathbefore 1.20.11; from 1.21.0-0 before 1.21.4
- Go standard library · path/filepathfrom 1.20.11 before 1.20.12; from 1.21.4 before 1.21.5
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Go standard library
- Published
- November 2023
CoverageNo articles yet
No CyberSIXT article names CVE-2023-45283 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-41cwe.mitre.org
- go.dev/issue/63713go.dev
- go.dev/cl/540277go.dev
- groups.google.com/g/golang-announce/c/4tU8LZfBFkYgroups.google.com
- go.dev/issue/64028go.dev
- go.dev/cl/541175go.dev
- groups.google.com/g/golang-dev/c/6ypN5EjibjM/m/KmLVYH_uAgAJgroups.google.com
- pkg.go.dev/vuln/GO-2023-2185pkg.go.dev
- openwall.com/lists/oss-security/2023/12/05/2openwall.com
- security.netapp.com/advisory/ntap-20231214-0008security.netapp.com