First published: Wed Nov 02 2022(Updated: )
Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows. In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".
Credit: security@golang.org security@golang.org
Affected Software | Affected Version | How to fix |
---|---|---|
IBM Cloud Pak for Business Automation | <=V22.0.2 - V22.0.2-IF001 | |
IBM Cloud Pak for Business Automation | <=V21.0.3 - V21.0.3-IF017 | |
IBM Cloud Pak for Business Automation | <=V22.0.1 - V22.0.1-IF006 and later fixes V21.0.2 - V21.0.2-IF012 and later fixesV21.0.1 - V21.0.1-IF007 and later fixesV20.0.1 - V20.0.3 and later fixesV19.0.1 - V19.0.3 and later fixesV18.0.0 - V18.0.2 and later fixes | |
All of | ||
Any of | ||
Golang | <1.18.8 | |
Golang | >=1.19.0<1.19.3 | |
Microsoft Windows Operating System | ||
Golang | <1.18.8 | |
Golang | >=1.19.0<1.19.3 | |
Microsoft Windows Operating System |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2022-41716.
The severity of CVE-2022-41716 is high with a score of 7.5.
A remote attacker can exploit CVE-2022-41716 by maliciously setting environment variables on Windows.
Versions up to 1.18.8 and versions between 1.19.0 and 1.19.3 of Golang Go are affected by CVE-2022-41716.
Refer to the references for patches or fixes available for CVE-2022-41716.