Back to bug 2216965
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Pedro Sampaio | 2023-06-26 17:41:27 UTC | CC | amctagga, aoconnor, asm, bniver, bodavis, dbenoit, emachado, flucifre, gmeno, mbenjamin, mhackett, mnewsome, sipoyare, sostapov, tstellar, vereddy | |
| Pedro Sampaio | 2023-06-26 17:41:43 UTC | Depends On | 2217561, 2217560 | |
| Pedro Sampaio | 2023-06-26 17:54:31 UTC | Fixed In Version | go 1.20.5, go 1.19.10 | |
| Pedro Sampaio | 2023-06-26 18:00:51 UTC | Blocks | 2217573 | |
| Pedro Sampaio | 2023-06-26 18:07:52 UTC | Depends On | 2217597, 2217599, 2217591, 2217588, 2217595, 2217593, 2217590, 2217594, 2217598, 2217600, 2217592, 2217596, 2217601 | |
| errata-xmlrpc | 2023-06-29 05:30:51 UTC | Link ID | Red Hat Product Errata RHSA-2023:3920 | |
| errata-xmlrpc | 2023-06-29 09:07:25 UTC | Link ID | Red Hat Product Errata RHSA-2023:3922 | |
| errata-xmlrpc | 2023-06-29 09:45:21 UTC | Link ID | Red Hat Product Errata RHSA-2023:3923 | |
| errata-xmlrpc | 2023-06-29 13:45:52 UTC | Link ID | Red Hat Product Errata RHBA-2023:3940 | |
| errata-xmlrpc | 2023-06-29 14:13:28 UTC | Link ID | Red Hat Product Errata RHBA-2023:3941 | |
| Product Security DevOps Team | 2023-06-29 14:16:40 UTC | Resolution | --- | ERRATA |
| Status | NEW | CLOSED | ||
| Last Closed | 2023-06-29 14:16:40 UTC | |||
| Anten Skrabec | 2023-06-29 19:17:52 UTC | Doc Text | 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. | |
| Paige Jung | 2023-06-29 19:30:04 UTC | Doc Text | 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. | 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. |
| errata-xmlrpc | 2023-06-30 02:50:33 UTC | Link ID | Red Hat Product Errata RHBA-2023:3956 |
Back to bug 2216965