The Go Programming Language
Security Fix(es):
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.(CVE-2023-29403)
{
"severity": "High"
}{
"x86_64": [
"golang-1.17.3-19.oe2203.x86_64.rpm",
"golang-1.17.3-19.oe2203sp1.x86_64.rpm",
"golang-1.17.3-19.oe2203sp2.x86_64.rpm"
],
"src": [
"golang-1.17.3-19.oe2203.src.rpm",
"golang-1.17.3-19.oe2203sp1.src.rpm",
"golang-1.17.3-19.oe2203sp2.src.rpm"
],
"aarch64": [
"golang-1.17.3-19.oe2203.aarch64.rpm",
"golang-1.17.3-19.oe2203sp1.aarch64.rpm",
"golang-1.17.3-19.oe2203sp2.aarch64.rpm"
],
"noarch": [
"golang-devel-1.17.3-19.oe2203.noarch.rpm",
"golang-help-1.17.3-19.oe2203.noarch.rpm",
"golang-help-1.17.3-19.oe2203sp1.noarch.rpm",
"golang-devel-1.17.3-19.oe2203sp1.noarch.rpm",
"golang-help-1.17.3-19.oe2203sp2.noarch.rpm",
"golang-devel-1.17.3-19.oe2203sp2.noarch.rpm"
]
}