CVE-2022-30580: Code Injection
First published: Wed Aug 10 2022(Updated: )
Code injection in Cmd.Start in os/exec before Go 1.17.11 and Go 1.18.3 allows execution of any binaries in the working directory named either "..com" or "..exe" by calling Cmd.Run, Cmd.Start, Cmd.Output, or Cmd.CombinedOutput when Cmd.Path is unset.
Credit: security@golang.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Golang Go | <1.17.11 | |
| Golang Go | >=1.18.0<1.18.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID of this code injection vulnerability?
The vulnerability ID is CVE-2022-30580.
What is the severity of CVE-2022-30580?
The severity of CVE-2022-30580 is high with a CVSS score of 7.8.
Which software versions are affected by CVE-2022-30580?
Versions of Go before 1.17.11 and versions between 1.18.0 and 1.18.3 are affected by CVE-2022-30580.
How can an attacker exploit this vulnerability?
An attacker can exploit this vulnerability by calling Cmd.Run, Cmd.Start, Cmd.Output, or Cmd.CombinedOutput when Cmd.Path is unset, allowing execution of any binaries in the working directory named "..com" or "..exe".
Are there any fix or workaround available for CVE-2022-30580?
Yes, upgrading to Go 1.17.11 or Go 1.18.3 or later versions is recommended to fix CVE-2022-30580.
- collector/nvd-index
- vendor/golang
- canonical/golang go
- version/golang go/1.18.0