CVE-2023-29403: Unsafe behavior in setuid/setgid binaries in runtime
Golang Go could allow a local authenticated attacker to gain elevated privileges on the system, caused by a flaw when a binary is run with the setuid/setgid bits. By sending a specially crafted request, an authenticated attacker could exploit this vulnerability to gain elevated privileges. to read or write contents of the registers.
Other sources
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.
— Launchpad
Unsafe behavior in setuid/setgid binaries in runtime
— Microsoft
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is CVE-2023-29403?
CVE-2023-29403 is a vulnerability in the Go programming language on Unix platforms, where the Go runtime does not behave differently when a binary is run with the setuid/setgid bits, which can be dangerous in certain cases.
What is the severity of CVE-2023-29403?
The severity of CVE-2023-29403 is high with a severity value of 7.8.
Which software versions are affected by CVE-2023-29403?
The affected software versions are Go up to version 1.19.10, Go versions 1.20.0 to 1.20.5, and Fedora version 38.
How can CVE-2023-29403 be exploited?
CVE-2023-29403 can be exploited by executing a setuid/setgid binary with standard I/O, allowing for dangerous actions like dumping memory state or assuming the status of standard I/O file descriptors.
Are there any references available for CVE-2023-29403?
Yes, you can find references for CVE-2023-29403 at the following links: [link1](https://go.dev/cl/501223), [link2](https://go.dev/issue/60272), [link3](https://groups.google.com/g/golang-announce/c/q5135a9d924/m/j0ZoAJOHAwAJ)