All reports
High

Unsafe behavior in setuid/setgid binaries in runtime

Affected versions

Affected versions
<1.19.10 || >=1.20.0-0 <1.20.5
Fixed version
1.19.10 · 1.20.5
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2023-29403

Probability of exploitation in the next 30 days: 0.43%

FIRST EPSS · 2026-11-21

Description

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.

Links

Credits

  • Vincent Dehors from Synacktiv