Path traversal via Clean on Windows 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.2% (FIRST EPSS); higher than 82.7% 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 path/filepath 1.17.11, 1.18.3.
Low priority for now. Upgrade to Go standard library path/filepath 1.17.11, 1.18.3 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
Incorrect conversion of certain invalid paths to valid, absolute paths in Clean in path/filepath before Go 1.17.11 and Go 1.18.3 on Windows allows potential directory traversal attack.
- Published
- Aug 10, 2022
- Updated
- Jun 17, 2026
- EPSS
- 2.2% · 82th 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.2%
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.17.11
- golang go1.18.0 and later · before 1.18.3
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 path/filepath
- before 1.17.11affected · semver
- 1.18.0-0 and later · before 1.18.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | stdlib | from 1.18.0-0 · before 1.18.3 | 1.18.3 |
| Go | stdlib | before 1.17.11 | 1.17.11 |
| openSUSE:Tumbleweed | go1.17 | before 1.17.11-1.1 | 1.17.11-1.1 |
| openSUSE:Tumbleweed | go1.18 | before 1.18.3-1.1 | 1.18.3-1.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP3 | go1.17 | before 1.17.11-150000.1.37.1 | 1.17.11-150000.1.37.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP3 | go1.17 | before 1.17.11-150000.1.37.1 | 1.17.11-150000.1.37.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP3 | go1.18 | before 1.18.3-150000.1.20.1 | 1.18.3-150000.1.20.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP3 | go1.18 | before 1.18.3-150000.1.20.1 | 1.18.3-150000.1.20.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | go1.18-openssl | before 1.18.10.1-150000.1.9.1 | 1.18.10.1-150000.1.9.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP4 | go1.18-openssl | before 1.18.10.1-150000.1.9.1 | 1.18.10.1-150000.1.9.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-2022-1962Aug 10, 2022 · Stack exhaustion due to deeply nested types in go/parser22Monitor
- ← EarlierCVE-2022-28131Aug 10, 2022 · Stack exhaustion from deeply nested XML documents in encoding/xml31Monitor
- Later →CVE-2022-30580Aug 10, 2022 · Empty Cmd.Path can trigger unintended binary in os/exec on Windows31Monitor
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 path/filepath | 1.17.11 | Vendor (CNA) |
| Go standard library path/filepath | 1.18.3 | Vendor (CNA) |
| Go:stdlib | 1.17.11 | Package registry (OSV) |
| Go:stdlib | 1.18.3 | Package registry (OSV) |
| opensuse:go1.17 | 1.17.11-150000.1.37.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:go1.18 | 1.18.3-150000.1.20.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:go1.18-openssl | 1.18.10.1-150000.1.9.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| suse:go1.17 | 1.17.11-150000.1.37.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP3 | Package registry (OSV) |
| suse:go1.18 | 1.18.3-150000.1.20.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP3 | Package registry (OSV) |
| suse:go1.18-openssl | 1.18.10.1-150000.1.9.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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
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).
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.