| Name | CVE-2023-45283 |
| 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 | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| golang-1.11 (PTS) | buster | 1.11.6-1+deb10u4 | vulnerable |
| buster (security) | 1.11.6-1+deb10u7 | vulnerable | |
| golang-1.15 (PTS) | bullseye | 1.15.15-1~deb11u4 | vulnerable |
| golang-1.19 (PTS) | bookworm | 1.19.8-2 | vulnerable |
| golang-1.21 (PTS) | sid, trixie | 1.21.9-1 | fixed |
| golang-1.7 (PTS) | stretch (security), stretch (lts), stretch | 1.7.4-2+deb9u5 | vulnerable |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| golang-1.11 | source | (unstable) | (unfixed) | unimportant | ||
| golang-1.15 | source | (unstable) | (unfixed) | unimportant | ||
| golang-1.19 | source | (unstable) | (unfixed) | unimportant | ||
| golang-1.20 | unknown | (unstable) | 1.20.12-1 | unimportant | ||
| golang-1.21 | source | (unstable) | 1.21.5-1 | unimportant | ||
| golang-1.7 | source | (unstable) | (unfixed) | unimportant |
https://groups.google.com/g/golang-announce/c/4tU8LZfBFkY
https://github.com/golang/go/issues/63713
https://github.com/golang/go/commit/9e933c189ca3a84f12995b3c799364a06abc4376 (go1.21.4)
https://github.com/golang/go/commit/46fb78168596f7ce8834f528bb0eb9555c08bcae (go1.20.11)
Requires a followup: https://www.openwall.com/lists/oss-security/2023/12/05/2
https://go.dev/issue/64028
https://github.com/golang/go/commit/8caf4bb3e78d0bc2d5598645b89ed8f0e9bd68f2 (go1.21.5)
https://github.com/golang/go/commit/1b59b017db1ac4a63ed08173c00d7f08d47530be (go1.20.12)
No security impact for Debian packages, only affects code running on Windows