CVE-2023-45283
published 2023-11-09CVE-2023-45283: 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…
PriorityP347high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
EPSS
2.76%
84.4th percentile
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
22 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | golang-1.15 | — | — |
| debian | golang-1.19 | — | — |
| go_standard_library | internal_safefilepath | < 1.20.11 | 1.20.11 |
| go_standard_library | internal_safefilepath | >= 1.21.0-0 < 1.21.4 | 1.21.4 |
| go_standard_library | path_filepath | < 1.20.11 | 1.20.11 |
| go_standard_library | path_filepath | >= 1.20.11 < 1.20.12 | 1.20.12 |
| go_standard_library | path_filepath | >= 1.21.0-0 < 1.21.4 | 1.21.4 |
| go_standard_library | path_filepath | >= 1.21.4 < 1.21.5 | 1.21.5 |
| golang | go | < 1.20.11 | 1.20.11 |
| golang | go | >= 1.21.0-0 < 1.21.4 | 1.21.4 |
| msrc | azl3_gcc_13.2.0-7_on_azure_linux_3.0 | — | — |
| msrc | azl3_golang_1.23.9-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_golang_1.24.3-1_on_azure_linux_3.0 | — | — |
| msrc | azl3_python-tensorboard_2.16.2-6_on_azure_linux_3.0 | — | — |
| msrc | azl3_tensorflow_2.16.1-9_on_azure_linux_3.0 | — | — |
| msrc | cbl2_golang_1.17.13-2_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_golang_1.18.8-7_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_golang_1.21.6-1_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_msft-golang_1.20.11-1_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_python-tensorboard_2.11.0-3_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_tensorflow_2.11.1-2_on_cbl_mariner_2.0 | — | — |
| paloalto | pan-os | — | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
osv7.5HIGH
vendor_debian7.5LOW
vendor_msrc7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Palo Alto
PAN-SA-2024-0001 Informational Bulletin: Impact of OSS CVEs in PAN-OS
vendor_paloalto·2024-02-14·CVSS 9.8
CVE-2017-18342 [CRITICAL] PAN-SA-2024-0001 Informational Bulletin: Impact of OSS CVEs in PAN-OS
PAN-SA-2024-0001 Informational Bulletin: Impact of OSS CVEs in PAN-OS
The Palo Alto Networks Product Security Assurance team has evaluated the following open source software (OSS) CVEs as they relate to PAN-OS software. While PAN-OS software may include the
CVEs: CVE-2017-18342, CVE-2017-8923, CVE-2017-9120, CVE-2019-1551, CVE-2019-16865, CVE-2019-16905, CVE-2019-19523, CVE-2019-19528, CVE-2019-19911, CVE-2020-0404, CVE-2020-0431, CVE-2020-0466, CVE-2020-10379, CVE-2020-11538, CVE-2020-11608, CVE-2020-12114, CVE-2020-12321, CVE-2020-12362, CVE-2020-12363, CVE-2020-12364, CVE-2020-13757, CVE-2020-14314, CVE-2020-14351, CVE-2020-15778, CVE-2020-1967, CVE-2020-24394, CVE-2020-24504, CVE-2020-25211, CVE-2020-25212, CVE-2020-25284, CVE-2020-25285, CVE-2020-25717, CVE-2020-26541, CVE-2020-2715
Microsoft
Insecure parsing of Windows paths with a \??\ prefix in path/filepath
vendor_msrc·2023-11-14·CVSS 7.5
CVE-2023-45283 [HIGH] CWE-22 Insecure parsing of Windows paths with a \??\ prefix in path/filepath
Insecure parsing of Windows paths with a \??\ prefix in path/filepath
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
Go: Go
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https
Debian
CVE-2023-45283: golang-1.15 - The filepath package does not recognize paths with a \??\ prefix as special. On ...
vendor_debian·2023·CVSS 7.5
CVE-2023-45283 [HIGH] CVE-2023-45283: golang-1.15 - The filepath package does not recognize paths with a \??\ prefix as special. On ...
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 volum
OSV
CVE-2023-45283: The filepath package does not recognize paths with a \??\ prefix as special
osv·2023-11-09·CVSS 7.5
CVE-2023-45283 [HIGH] CVE-2023-45283: The filepath package does not recognize paths with a \??\ prefix as special
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 volum
GHSA
GHSA-vvjp-q62m-2vph: The filepath package does not recognize paths with a \??\ prefix as special
ghsa_unreviewed·2023-11-09
CVE-2023-45283 [HIGH] CWE-22 GHSA-vvjp-q62m-2vph: The filepath package does not recognize paths with a \??\ prefix as special
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 volum
OSV
Insecure parsing of Windows paths with a \??\ prefix in path/filepath
osv·2023-11-08
CVE-2023-45283 Insecure parsing of Windows paths with a \??\ prefix in path/filepath
Insecure parsing of Windows paths with a \??\ prefix in path/filepath
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 \?
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
http://www.openwall.com/lists/oss-security/2023/12/05/2https://go.dev/cl/540277https://go.dev/cl/541175https://go.dev/issue/63713https://go.dev/issue/64028https://groups.google.com/g/golang-announce/c/4tU8LZfBFkYhttps://groups.google.com/g/golang-dev/c/6ypN5EjibjM/m/KmLVYH_uAgAJhttps://pkg.go.dev/vuln/GO-2023-2185https://security.netapp.com/advisory/ntap-20231214-0008/http://www.openwall.com/lists/oss-security/2023/12/05/2https://go.dev/cl/540277https://go.dev/cl/541175https://go.dev/issue/63713https://go.dev/issue/64028https://groups.google.com/g/golang-announce/c/4tU8LZfBFkYhttps://groups.google.com/g/golang-dev/c/6ypN5EjibjM/m/KmLVYH_uAgAJhttps://pkg.go.dev/vuln/GO-2023-2185https://security.netapp.com/advisory/ntap-20231214-0008/
2023-11-09
Published