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 PoCs from references.
- https://github.com/8-cm/kube-dump
- https://github.com/ARPSyndicate/cvemon
- https://github.com/JakubWierzchowski/manier
- https://github.com/agadecki/malware-cryptominer-container
- https://github.com/drewtwitchell/scancompare
- https://github.com/henriquebesing/container-security
- https://github.com/kb5fls/container-security
- https://github.com/runwhen-contrib/helm-charts
- https://github.com/ruzickap/malware-cryptominer-container