Google Go on Windows os.DirFS/http.Dir pathname traversal

Summaryinfo

A vulnerability was found in Google Go on Windows. It has been rated as critical. The affected element is the function os.DirFS/http.Dir. This manipulation causes pathname traversal. The identification of this vulnerability is CVE-2022-41720. There is no exploit available.

Detailsinfo

A vulnerability was found in Google Go on Windows (Programming Language Software) (version unknown). It has been declared as critical. Affected by this vulnerability is the function os.DirFS/http.Dir. The manipulation with an unknown input leads to a pathname traversal vulnerability. The CWE definition for the vulnerability is CWE-21. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was shared 12/07/2022. The advisory is shared at go.dev. This vulnerability is known as CVE-2022-41720 since 09/28/2022. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 04/24/2025). MITRE ATT&CK project uses the attack technique T1006 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Programming Language Software

Vendor

• Google

Name

• Go

License

• open-source

Website

• Vendor: https://www.google.com/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion