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.
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Wed, 16 Jul 2025 13:45:00 +0000

Type Values Removed Values Added
Metrics epss

{'score': 9e-05}

epss

{'score': 0.0001}


Mon, 06 Jan 2025 20:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 20 Dec 2024 13:30:00 +0000

Type Values Removed Values Added
References

cve-icon MITRE

Status: PUBLISHED

Assigner: Go

Published:

Updated: 2025-02-13T16:49:14.029Z

Reserved: 2023-04-05T19:36:35.042Z

Link: CVE-2023-29403

cve-icon Vulnrichment

Updated: 2024-12-20T13:06:40.480Z

cve-icon NVD

Status : Modified

Published: 2023-06-08T21:15:16.927

Modified: 2025-01-06T20:15:25.820

Link: CVE-2023-29403

cve-icon Redhat

Severity : Important

Publid Date: 2023-06-08T00:00:00Z

Links: CVE-2023-29403 - Bugzilla

cve-icon OpenCVE Enrichment

No data.