Vulnerability Intelligence Report
Unsanitized NUL in environment variables on Windows in syscall and os/exec
CVE-2022-41716
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".
No Active Exploit Signals
CVSS Base Score
6.3
MEDIUM
Exploitability:2.9
Impact Score:3.4
EPSS Probability:0.78%
Executive Threat Verdict
Evaluating...
Evaluating Threat Landscape...
Assessing known weaponization, exploitation telemetry, and federal advisories.
Attack Surface
—
Authentication
—
Weaponization
—
SSVC Action
—
Weaknesses (CWE)
CWE-158 ↗CWE-158: Improper Neutralization of Null Byte or NUL Character
Affected Products & Versions
| Vendor | Product | Affected Versions |
|---|---|---|
| Go standard library | syscall | 0 < 1.18.8 (affected), 1.19.0-0 < 1.19.3 (affected) |
| Go standard library | os/exec | 0 < 1.18.8 (affected), 1.19.0-0 < 1.19.3 (affected) |
References & Technical Advisories
No reference links found.
Threat Intelligence Signals
EPSS Score
0.778%
GitHub Advisory
Identity & Timeline
| Status | PUBLISHED |
| Assigning Authority | Go Project · Vendor · USA |
| Reserved | 2022-09-28T17:00:06 |
| Published | 2022-11-02T15:28:19 |
| Last Updated | 2024-10-30T13:59:43 |
Community Chatter & Buzz