On Unix platforms, the Go runtime does not behave...
High severity
Unreviewed
Published
Jun 8, 2023
to the GitHub Advisory Database
•
Updated Dec 4, 2023
Description
Published by the National Vulnerability Database
Jun 8, 2023
Published to the GitHub Advisory Database
Jun 8, 2023
Last updated
Dec 4, 2023
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.
References