Summary
This update for go1.19 fixes the following issues:
Update to go1.19.10 (bsc#1200441):
- CVE-2023-29402: cmd/go: Fixed cgo code injection (bsc#1212073).
- CVE-2023-29403: runtime: Fixed unexpected behavior of setuid/setgid binaries (bsc#1212074).
- CVE-2023-29404: cmd/go: Fixed improper sanitization of LDFLAGS (bsc#1212075).
- CVE-2023-29405: cmd/go: Fixed improper sanitization of LDFLAGS (bsc#1212076).
Fixed packages 5
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.4 | go1.19 | 1.19.10-150000.1.34.1 |
| openSUSE · Leap 15.5 | go1.19 | 1.19.10-150000.1.34.1 |
| SUSE · SLES 15 SP4 Linux Enterprise Module for Development Tools 15 SP4 | go1.19 | 1.19.10-150000.1.34.1 |
| SUSE · SLES 15 SP5 Linux Enterprise Module for Development Tools 15 SP5 | go1.19 | 1.19.10-150000.1.34.1 |
| SUSE · SLE Real Time 15 SP3 Linux Enterprise Real Time 15 SP3 | go1.19 | 1.19.10-150000.1.34.1 |
Vulnerabilities 4
-
Critical 9.8
Code injection via go command with cgo in cmd/go
The go command may generate unexpected code at build time when using cgo. This may result in unexpected behavior when running a go program which uses cgo. This may occur when running an untrusted module which contains directories with newline characters in th…
-
Critical 9.8
Improper handling of non-optional LDFLAGS in go command with cgo in cmd/go
The go command may execute arbitrary code at build time when using cgo. This may occur when running "go get" on a malicious module, or when running any other command which builds untrusted code. This is can by triggered by linker flags, specified via a "#cgo …
-
Critical 9.8
Improper sanitization of LDFLAGS with embedded spaces in go command with cgo in cmd/go
The go command may execute arbitrary code at build time when using cgo. This may occur when running "go get" on a malicious module, or when running any other command which builds untrusted code. This is can by triggered by linker flags, specified via a "#cgo …
-
High 7.8
Unsafe behavior in setuid/setgid binaries in runtime
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/set…
References
-
report
https://bugzilla.suse.com/1200441
-
report
https://bugzilla.suse.com/1212073
-
report
https://bugzilla.suse.com/1212074
-
report
https://bugzilla.suse.com/1212075
-
report
https://bugzilla.suse.com/1212076
-
web
https://www.suse.com/security/cve/CVE-2023-29402
-
web
https://www.suse.com/security/cve/CVE-2023-29403
-
web
https://www.suse.com/security/cve/CVE-2023-29404
-
web
https://www.suse.com/security/cve/CVE-2023-29405