Google Go up to 1.17.10/1.18.2 on Windows path-filepath Clean pathname traversal

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k0.00

Summaryinfo

A vulnerability was found in Google Go up to 1.17.10/1.18.2 on Windows. It has been rated as critical. This impacts the function Clean of the component path-filepath. The manipulation leads to pathname traversal. This vulnerability is documented as CVE-2022-29804. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Google Go up to 1.17.10/1.18.2 on Windows (Programming Language Software). It has been rated as critical. This issue affects the function Clean of the component path-filepath. The manipulation with an unknown input leads to a pathname traversal vulnerability. Using CWE to declare the problem leads to CWE-21. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was released 08/11/2022. It is possible to read the advisory at go.dev. The identification of this vulnerability is CVE-2022-29804 since 04/26/2022. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

Upgrading to version 1.17.11 or 1.18.3 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-34125). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Pathname traversal
CWE: CWE-21 / CWE-22
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Go 1.17.11/1.18.3

Timelineinfo

04/26/2022 🔍
08/11/2022 +107 days 🔍
08/11/2022 +0 days 🔍
05/23/2026 +1381 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: go.dev
Status: Confirmed

CVE: CVE-2022-29804 (🔍)
GCVE (CVE): GCVE-0-2022-29804
GCVE (VulDB): GCVE-100-206171
EUVD: 🔍

Entryinfo

Created: 08/11/2022 11:27
Updated: 05/23/2026 03:16
Changes: 08/11/2022 11:27 (43), 05/23/2026 03:16 (15)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!