golang-1.19 — security advisory
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.
- Products
- golang-1.19
- Affected versions
- 1.19.10-1, 1.19.10-2, 1.19.11-1, 1.19.12-1, 1.19.12-2, 1.19.12-2~bpo11+1, 1.19.12-2~bpo12+1, 1.19.13-1, 1.19.13-1~bpo11+1, 1.19.13-1~bpo12+1, 1.19.8-2, 1.19.9-1
- Fixed versions
- Not specified
- CVEs
- CVE-2023-45283
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 16:25 UTC · Revision 1
Source evidence
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.
osv:DEBIAN-CVE-2023-45283
golang-1.19
Fixed versions: Not specified
Complete source record
{
"id": "cff5b156ef79ecf18703cc2837d058a3df16f04d7958717cfa3a1926091b1f61",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2023-45283",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2023-45283",
"summary": "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.",
"evidence": "osv:DEBIAN-CVE-2023-45283",
"products": [
{
"name": {
"value": "golang-1.19",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "1.19.10-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.10-2",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.11-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.12-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.12-2",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.12-2~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.12-2~bpo12+1",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.13-1",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.13-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.13-1~bpo12+1",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.8-2",
"evidence": "/affected/0/versions"
},
{
"value": "1.19.9-1",
"evidence": "/affected/0/versions"
}
]
}
],
"severity": "high",
"structured": {
"id": "DEBIAN-CVE-2023-45283",
"aliases": [
"DEBIAN-CVE-2023-45283"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "golang-1.19",
"purl": "pkg:deb/debian/golang-1.19?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"1.19.10-1",
"1.19.10-2",
"1.19.11-1",
"1.19.12-1",
"1.19.12-2",
"1.19.12-2~bpo11+1",
"1.19.12-2~bpo12+1",
"1.19.13-1",
"1.19.13-1~bpo11+1",
"1.19.13-1~bpo12+1",
"1.19.8-2",
"1.19.9-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-45283.json"
},
"ecosystem_specific": {
"urgency": "unimportant"
}
}
],
"modified": "2026-10-26T18:03:06.595700581Z",
"provider": "osv",
"upstream": [
"CVE-2023-45283"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2023-45283"
]
},
"related_cves": [
{
"value": "CVE-2023-45283",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 457660,
"published_at": "2023-11-09T17:15:08.757+00:00"
}