On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors. If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.
[
{
"vendor": "Go standard library",
"product": "runtime",
"collectionURL": "https://pkg.go.dev",
"packageName": "runtime",
"versions": [
{
"version": "0",
"lessThan": "1.19.10",
"status": "affected",
"versionType": "semver"
},
{
"version": "1.20.0-0",
"lessThan": "1.20.5",
"status": "affected",
"versionType": "semver"
}
],
"defaultStatus": "unaffected"
}
]
go.dev/cl/501223
go.dev/issue/60272
groups.google.com/g/golang-announce/c/q5135a9d924/m/j0ZoAJOHAwAJ
lists.fedoraproject.org/archives/list/[email protected]/message/NZ2O6YCO2IZMZJELQGZYR2WAUNEDLYV6/
lists.fedoraproject.org/archives/list/[email protected]/message/XBS3IIK6ADV24C5ULQU55QLT2UE762ZX/
pkg.go.dev/vuln/GO-2023-1840
security.gentoo.org/glsa/202311-09