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
Configurations
History
06 Jan 2025, 20:15
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
20 Dec 2024, 13:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
Information
Published : 2023-06-08 21:15
Updated : 2025-01-06 20:15
NVD link : CVE-2023-29403
Mitre link : CVE-2023-29403
CVE.ORG link : CVE-2023-29403
JSON object : View
Products Affected
golang
- go
fedoraproject
- fedora
CWE
CWE-668
Exposure of Resource to Wrong Sphere