CVE-2023-45283
The filepath package does not recognize paths with a \??\ prefix as sp ...
Overview
Description
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.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness: CWE-22
Affected packages · 2
Operating systems · 25 fixes
Photon OS 2 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 4.0 | go | 1.20.12-1.ph4 |
| 5.0 | go | 1.20.12-1.ph5 |
SUSE Linux Enterprise 2 releases · 4 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 15.4 | go1-20 +2 | 1.20.11-150000.1.32.1 | SUSE-SU-2023:4470-1 |
| 15.4 | go1-20-openssl +2 | 1.20.11.1-150000.1.14.1 | SUSE-SU-2023:4472-1 |
| 15.4 | go1-21 +2 | 1.21.4-150000.1.15.1 | SUSE-SU-2023:4471-1 |
| 15.4 | go1-21-openssl +2 | 1.21.4.1-150000.1.5.1 | SUSE-SU-2023:4469-1 |
| 15.5 | go1-20 +2 | 1.20.11-150000.1.32.1 | SUSE-SU-2023:4470-1 |
| 15.5 | go1-20-openssl +2 | 1.20.11.1-150000.1.14.1 | SUSE-SU-2023:4472-1 |
2 more rows
amazon linux 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 2023 | golang +6 | 1.20.12-1.amzn2023.0.1 |
chainguard 1 release · 3 packages
| Release | Package | Fixed in |
|---|---|---|
| aactl +279 | not affected | |
| go-1-20 | 1.20.12-r0 | |
| go-1-21 | 1.21.5-r0 |
debian 2 releases · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| 11 | golang-1-15 | affected |
| 12 | golang-1-19 | affected |
echo 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| golang-1-19 | affected |
openSUSE 1 release · 4 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | go1-20 +3 | 1.20.11-1.1 | openSUSE-SU-2024:13406-1 |
| Tumbleweed | go1-21 +3 | 1.21.4-1.1 | openSUSE-SU-2024:13407-1 |
| Tumbleweed | traefik | 2.10.7-1.1 | openSUSE-SU-2024:13506-1 |
| Tumbleweed | traefik2 | 2.11.5-1.1 | openSUSE-SU-2024:14076-1 |
root.io debian 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 12 | rootio-golang-1-19 | affected |
wolfi 1 release · 3 packages
| Release | Package | Fixed in |
|---|---|---|
| aactl +262 | not affected | |
| go-1-20 | 1.20.12-r0 | |
| go-1-21 | 1.21.5-r0 |
References
- www.openwall.com http://www.openwall.com/lists/oss-security/2023/12/05/2
- go.dev https://go.dev/cl/540277
- go.dev https://go.dev/cl/541175
- go.dev https://go.dev/issue/63713
- go.dev https://go.dev/issue/64028
- groups.google.com https://groups.google.com/g/golang-announce/c/4tU8LZfBFkY
- groups.google.com https://groups.google.com/g/golang-dev/c/6ypN5EjibjM/m/KmLVYH_uAgAJ
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2023-45283
- pkg.go.dev https://pkg.go.dev/vuln/GO-2023-2185
- security.netapp.com https://security.netapp.com/advisory/ntap-20231214-0008/
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.