NVD / CVE Program· CNA Go

CVE-2022-41720: Restricted file access on Windows in os and net/http

Noroxi assessment

Priority: Monitor (action score 30/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.2% (FIRST EPSS); higher than 69.8% 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 net/http 1.18.9, 1.19.4; Go standard library os 1.18.9, 1.19.4.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Go standard library net/http 1.18.9, 1.19.4; Go standard library os 1.18.9, 1.19.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

On Windows, restricted files can be accessed via os.DirFS and http.Dir. The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access. In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system. With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Dec 7, 2022
Updated: Jun 17, 2026
EPSS: 1.2% · 69th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.2%

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.

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.

Vendor	Product	CPE
golang	go	cpe:2.3:a:golang:go
microsoft	windows	cpe:2.3:o:microsoft:windows

Affected versions

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

golang gobefore 1.18.9
golang go1.19.0 and later · before 1.19.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 net/http
- before 1.18.9affected · semver
- 1.19.0-0 and later · before 1.19.4affected · semver
Go standard library os
- before 1.18.9affected · semver
- 1.19.0-0 and later · before 1.19.4affected · 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	before 1.19.4-1	1.19.4-1
Go	stdlib	from 1.19.0-0 · before 1.19.4	1.19.4
Go	stdlib	before 1.18.9	1.18.9
openSUSE:Leap 15.3	go1.18	before 1.18.9-150000.1.40.1	1.18.9-150000.1.40.1
openSUSE:Leap 15.3	go1.19	before 1.19.4-150000.1.18.1	1.19.4-150000.1.18.1
openSUSE:Tumbleweed	go1.18	before 1.18.9-1.1	1.18.9-1.1
openSUSE:Tumbleweed	go1.19	before 1.19.4-1.1	1.19.4-1.1
SUSE:Linux Enterprise Module for Containers 15 SP4	container-suseconnect	before 2.4.0-150000.4.24.1	2.4.0-150000.4.24.1
SUSE:Linux Enterprise Module for Development Tools 15 SP3	go1.18	before 1.18.9-150000.1.40.1	1.18.9-150000.1.40.1
SUSE:Linux Enterprise Module for Development Tools 15 SP3	go1.19	before 1.19.4-150000.1.18.1	1.19.4-150000.1.18.1

Same product

golang: all records

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-41715Oct 14, 2022 · Memory exhaustion when compiling regular expressions in regexp/syntax
31Monitor
← EarlierCVE-2022-41716Nov 2, 2022 · Unsanitized NUL in environment variables on Windows in syscall and os/exec
30Monitor
Later →CVE-2022-41717Dec 8, 2022 · Excessive memory growth in net/http and golang.org/x/net/http2
23Monitor

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 net/http	1.18.9	Vendor (CNA)
Go standard library net/http	1.19.4	Vendor (CNA)
Go standard library os	1.18.9	Vendor (CNA)
Go standard library os	1.19.4	Vendor (CNA)
debian:golang-1.19	1.19.4-1 · Debian:12	Package registry (OSV)
Go:stdlib	1.18.9	Package registry (OSV)
Go:stdlib	1.19.4	Package registry (OSV)
opensuse:go1.18	1.18.9-150000.1.40.1 · openSUSE:Leap 15.3	Package registry (OSV)
opensuse:go1.19	1.19.4-150000.1.18.1 · openSUSE:Leap 15.3	Package registry (OSV)
suse:container-suseconnect	2.4.0-150000.4.24.1 · SUSE:Linux Enterprise Module for Containers 15 SP4	Package registry (OSV)
suse:go1.18	1.18.9-150000.1.40.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP3	Package registry (OSV)
suse:go1.19	1.19.4-150000.1.18.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP3	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.

No history yet (it accumulates with the daily EPSS job).

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 researchers

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

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

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-23-0169 · Mar 23, 2023(SUSE Güvenlik Güncellemesi)

All national notices →

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 class

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

Vulnerable

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

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.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)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

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

References

go.dev/cl/455716

Show all references (3 more)

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

All records