CVE-2023-45283: Insecure parsing of Windows paths with a \??\ prefix in path/filepath
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.7% (FIRST EPSS); higher than 86.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Go standard library internal/safefilepath 1.20.11, 1.21.4; Go standard library path/filepath 1.20.11, 1.20.12, 1.21.4.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Go standard library internal/safefilepath 1.20.11, 1.21.4; Go standard library path/filepath 1.20.11, 1.20.12, 1.21.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 9, 2023
- Updated
- Jun 17, 2026
- EPSS
- 2.7% · 86th percentile
- CWE
- CWE-22
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- golang gobefore 1.20.11
- golang go1.21.0-0 and later · before 1.21.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.
Go standard library internal/safefilepath
- before 1.20.11affected · semver
- 1.21.0-0 and later · before 1.21.4affected · semver
Go standard library path/filepath
- before 1.20.11affected · semver
- 1.21.0-0 and later · before 1.21.4affected · semver
- 1.20.11 and later · before 1.20.12affected · semver
- 1.21.4 and later · before 1.21.5affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | golang-1.19 | from 0 | — |
| Go | stdlib | from 1.20.11 · before 1.20.12 | 1.20.12 |
| Go | stdlib | from 1.21.0-0 · before 1.21.4 | 1.21.4 |
| Go | stdlib | from 1.21.4 · before 1.21.5 | 1.21.5 |
| Go | stdlib | before 1.20.11 | 1.20.11 |
| openSUSE:Leap 15.4 | go1.20 | before 1.20.11-150000.1.32.1 | 1.20.11-150000.1.32.1 |
| openSUSE:Leap 15.4 | go1.20-openssl | before 1.20.11.1-150000.1.14.1 | 1.20.11.1-150000.1.14.1 |
| openSUSE:Leap 15.4 | go1.21 | before 1.21.4-150000.1.15.1 | 1.21.4-150000.1.15.1 |
| openSUSE:Leap 15.4 | go1.21-openssl | before 1.21.4.1-150000.1.5.1 | 1.21.4.1-150000.1.5.1 |
| openSUSE:Tumbleweed | go1.20 | before 1.20.11-1.1 | 1.20.11-1.1 |
| openSUSE:Tumbleweed | go1.21 | before 1.21.4-1.1 | 1.21.4-1.1 |
| openSUSE:Tumbleweed | traefik | before 2.10.7-1.1 | 2.10.7-1.1 |
| openSUSE:Tumbleweed | traefik2 | before 2.11.5-1.1 | 2.11.5-1.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | go1.20 | before 1.20.11-150000.1.32.1 | 1.20.11-150000.1.32.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | go1.20-openssl | before 1.20.11.1-150000.1.14.1 | 1.20.11.1-150000.1.14.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | go1.21 | before 1.21.4-150000.1.15.1 | 1.21.4-150000.1.15.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | go1.21-openssl | before 1.21.4.1-150000.1.5.1 | 1.21.4.1-150000.1.5.1 |
Same product
golang: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only 54Plan
- CVE-2018-16873In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and52Plan
- CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH42Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-39323Oct 5, 2023 · Arbitrary code execution during build via line directives in cmd/go33Monitor
- ← EarlierCVE-2023-39325Oct 11, 2023 · HTTP/2 rapid reset can cause excessive work in net/http31Monitor
- Later →CVE-2023-45284Nov 9, 2023 · Incorrect detection of reserved device names on Windows in path/filepath21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go standard library internal/safefilepath | 1.20.11 | Vendor (CNA) |
| Go standard library internal/safefilepath | 1.21.4 | Vendor (CNA) |
| Go standard library path/filepath | 1.20.11 | Vendor (CNA) |
| Go standard library path/filepath | 1.20.12 | Vendor (CNA) |
| Go standard library path/filepath | 1.21.4 | Vendor (CNA) |
| Go standard library path/filepath | 1.21.5 | Vendor (CNA) |
| Go:stdlib | 1.20.11 | Package registry (OSV) |
| Go:stdlib | 1.20.12 | Package registry (OSV) |
| Go:stdlib | 1.21.4 | Package registry (OSV) |
| Go:stdlib | 1.21.5 | Package registry (OSV) |
| opensuse:go1.20 | 1.20.11-150000.1.32.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:go1.20-openssl | 1.20.11.1-150000.1.14.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:go1.21 | 1.21.4-150000.1.15.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:go1.21-openssl | 1.21.4.1-150000.1.5.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:traefik | 2.10.7-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:traefik2 | 2.11.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:go1.20 | 1.20.11-150000.1.32.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
| suse:go1.20-openssl | 1.20.11.1-150000.1.14.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
| suse:go1.21 | 1.21.4-150000.1.15.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
| suse:go1.21-openssl | 1.21.4.1-150000.1.5.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2022-41722254 days apartPath traversal on Windows in path/filepath31Monitor
- CVE-2022-32190422 days apartFailure to strip relative path components in net/url31Monitor
- CVE-2022-29804456 days apartPath traversal via Clean on Windows in path/filepath31Monitor
- CVE-2022-41720337 days apartRestricted file access on Windows in os and net/http30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0646 · Nov 20, 2023(SUSE Güvenlik Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.