Skip to content
Noroxi
CVE-2022-41722· NVD / CVE Program· CNA Go

Path traversal 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: 1.6% (FIRST EPSS); higher than 76.5% 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.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Go standard library path/filepath 1.19.6, 1.20.1.

Low priority for now. Upgrade to Go standard library path/filepath 1.19.6, 1.20.1 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

A path traversal vulnerability exists in filepath.Clean on Windows. On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack. After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Feb 28, 2023
Updated
Jun 17, 2026
EPSS
1.6% · 76th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.6%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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.

Follow CVE-2022-41722

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
golanggo
microsoftwindows

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • golang gobefore 1.19.6
  • golang go1.20.0

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.19.6affected · semver
    • 1.20.0-0 and later · before 1.20.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12golang-1.19before 1.19.6-21.19.6-2
Gostdlibfrom 1.20.0-0 · before 1.20.11.20.1
Gostdlibbefore 1.19.61.19.6
openSUSE:Tumbleweedgo1.19before 1.19.6-1.11.19.6-1.1
openSUSE:Tumbleweedgo1.20before 1.20.1-1.11.20.1-1.1
Red Hat:openshift_ironic:4.13::el9openstack-ironicbefore 1:21.3.1-0.20230510075528.b3c902e.el91:21.3.1-0.20230510075528.b3c902e.el9
Red Hat:openshift_ironic:4.13::el9openstack-ironic-apibefore 1:21.3.1-0.20230510075528.b3c902e.el91:21.3.1-0.20230510075528.b3c902e.el9
Red Hat:openshift_ironic:4.13::el9openstack-ironic-commonbefore 1:21.3.1-0.20230510075528.b3c902e.el91:21.3.1-0.20230510075528.b3c902e.el9
Red Hat:openshift_ironic:4.13::el9openstack-ironic-conductorbefore 1:21.3.1-0.20230510075528.b3c902e.el91:21.3.1-0.20230510075528.b3c902e.el9
Red Hat:openshift_ironic:4.13::el9openstack-ironic-dnsmasq-tftp-serverbefore 1:21.3.1-0.20230510075528.b3c902e.el91:21.3.1-0.20230510075528.b3c902e.el9
Red Hat:openshift_ironic:4.13::el9python-werkzeugbefore 0:2.0.3-4.el90:2.0.3-4.el9
Red Hat:openshift_ironic:4.13::el9python3-ironic-testsbefore 1:21.3.1-0.20230510075528.b3c902e.el91:21.3.1-0.20230510075528.b3c902e.el9
Red Hat:openshift_ironic:4.13::el9python3-werkzeugbefore 0:2.0.3-4.el90:2.0.3-4.el9
Red Hat:openshift:4.13::el8cri-obefore 0:1.26.3-7.rhaos4.13.gitec064c9.el80:1.26.3-7.rhaos4.13.gitec064c9.el8
Red Hat:openshift:4.13::el8cri-o-debuginfobefore 0:1.26.3-7.rhaos4.13.gitec064c9.el80:1.26.3-7.rhaos4.13.gitec064c9.el8
Red Hat:openshift:4.13::el8cri-o-debugsourcebefore 0:1.26.3-7.rhaos4.13.gitec064c9.el80:1.26.3-7.rhaos4.13.gitec064c9.el8
Red Hat:openshift:4.13::el8haproxybefore 0:2.2.24-3.rhaos4.13.el80:2.2.24-3.rhaos4.13.el8
Red Hat:openshift:4.13::el8haproxy-debugsourcebefore 0:2.2.24-3.rhaos4.13.el80:2.2.24-3.rhaos4.13.el8
Red Hat:openshift:4.13::el8haproxy22before 0:2.2.24-3.rhaos4.13.el80:2.2.24-3.rhaos4.13.el8
Red Hat:openshift:4.13::el8haproxy22-debuginfobefore 0:2.2.24-3.rhaos4.13.el80:2.2.24-3.rhaos4.13.el8
Red Hat:openshift:4.13::el8openshiftbefore 0:4.13.0-202305301919.p0.g0001a21.assembly.stream.el80:4.13.0-202305301919.p0.g0001a21.assembly.stream.el8
Red Hat:openshift:4.13::el8openshiftbefore 0:4.13.0-202304211155.p0.gb404935.assembly.stream.el80:4.13.0-202304211155.p0.gb404935.assembly.stream.el8
Red Hat:openshift:4.13::el8openshift-clientsbefore 0:4.13.0-202305291355.p0.g1024efc.assembly.stream.el80:4.13.0-202305291355.p0.g1024efc.assembly.stream.el8
Red Hat:openshift:4.13::el8openshift-clientsbefore 0:4.13.0-202303241616.p0.g92b1a3d.assembly.stream.el80:4.13.0-202303241616.p0.g92b1a3d.assembly.stream.el8

+96

Other 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 and
    52Plan
  • 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 GOARCH
    42Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-41720Dec 7, 2022 · Restricted file access on Windows in os and net/http
    30Monitor
  • ← EarlierCVE-2022-41717Dec 8, 2022 · Excessive memory growth in net/http and golang.org/x/net/http2
    23Monitor
  • Later →CVE-2022-41723Feb 28, 2023 · Denial of service via crafted HTTP/2 stream in net/http and golang.org/x/net
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go standard library path/filepath1.19.6Vendor (CNA)
Go standard library path/filepath1.20.1Vendor (CNA)
debian:golang-1.191.19.6-2 · Debian:12Package registry (OSV)
Go:stdlib1.19.6Package registry (OSV)
Go:stdlib1.20.1Package registry (OSV)
opensuse:go1.191.19.7-150000.1.23.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:go1.201.20.2-150000.1.5.1 · openSUSE:Leap 15.4Package registry (OSV)
red hat:buildah1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:buildah-debuginfo1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:buildah-debugsource1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:buildah-tests1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:buildah-tests-debuginfo1:1.29.1-1.rhaos4.13.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:cri-o0:1.26.3-3.rhaos4.13.git641290e.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:cri-o-debuginfo0:1.26.3-3.rhaos4.13.git641290e.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:cri-o-debugsource0:1.26.3-3.rhaos4.13.git641290e.el9 · Red Hat:openshift:4.13::el9Package registry (OSV)
red hat:openshift0:4.13.0-202304211155.p0.gb404935.assembly.stream.el8 · Red Hat:openshift:4.13::el8Package registry (OSV)
red hat:openshift-clients0:4.13.0-202303241616.p0.g92b1a3d.assembly.stream.el8 · Red Hat:openshift:4.13::el8Package registry (OSV)
red hat:openshift-clients-redistributable0:4.13.0-202303241616.p0.g92b1a3d.assembly.stream.el8 · Red Hat:openshift:4.13::el8Package registry (OSV)
red hat:openshift-hyperkube0:4.13.0-202304211155.p0.gb404935.assembly.stream.el8 · Red Hat:openshift:4.13::el8Package registry (OSV)
suse:go1.191.19.7-150000.1.23.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4Package registry (OSV)
suse:go1.201.20.2-150000.1.5.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP4Package 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.

EPSS, last 120 days

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.

Finders, 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

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records