Windows Environment Variables Vulnerability

Windows Environment Variables Vulnerability

According to the vulnerability that has been released on 27th of June; attackers may maliciosly set environment variables on Windows due to unsanitized NUL values.

In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. Therefore a malicious environment variable value can exploit this 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". (CVE-2022-41716)

Affected Systems

Configuration 1
cpe:2.3:a:golang:go:*:*:*:*:*:*:*:* Up to (excluding) 1.18.8
cpe:2.3:a:golang:go:*:*:*:*:*:*:*:* From (including) 1.19.0 Up to (excluding) 1.19.3
Running on/with
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*

IoC’s

-

Recommended Solution(s)

-

Mitigations

-

CVE / CWE

CVE-2022-41716

Related Website(s)

• https://nvd.nist.gov/vuln/detail/CVE-2022-41716
• https://go.dev/cl/446916
• https://go.dev/issue/56284
• https://groups.google.com/g/golang-announce/c/mbHY1UY3BaM/m/hSpmRzk-AgAJ
• https://pkg.go.dev/vuln/GO-2022-1095

* Vulnerabilities with a CVSS 3.1 score between 7.0 and 8.9 are evaluated to be “high” whereas vulnerabilities with a CVSS 3.1 score between 9.0 and 10.0 are evaluated to be “critical”.