CVE-2022-41716: Unsanitized NUL in environment variables on Windows in syscall and os/exec
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".
Other sources
Golang Go could allow a remote attacker to bypass security restrictions, caused by improper checking for invalid environment variable values in syscall.StartProcess and os/exec.Cmd. By using a specially-crafted environment variable value, an attacker could exploit this vulnerability to set a value for a different environment variable.
Affected Software
Event History
Frequently Asked Questions
What is the vulnerability ID for this issue?
The vulnerability ID is CVE-2022-41716.
What is the severity of CVE-2022-41716?
The severity of CVE-2022-41716 is high with a score of 7.5.
How can a remote attacker exploit CVE-2022-41716?
A remote attacker can exploit CVE-2022-41716 by maliciously setting environment variables on Windows.
Which versions of Golang Go are affected by CVE-2022-41716?
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.
Are there any patches or fixes available for CVE-2022-41716?
Refer to the references for patches or fixes available for CVE-2022-41716.