Closed haroonc closed 9 months ago
Although I can't speak for the moby/moby
project and Docker team that publishes the docker
binaries that we use from https://download.docker.com/linux/static
, I don't see how these vulnerabilities apply since they all only matter when building a go project and do not really apply to running go-built binaries.
CVE-2023-29404
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 LDFLAGS" directive. The arguments for a number of flags which are non-optional are incorrectly considered optional, allowing disallowed flags to be smuggled through the LDFLAGS sanitization. This affects usage of both the gc and gccgo compilers.
CVE-2023-29405
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 LDFLAGS" directive. Flags containing embedded spaces are mishandled, allowing disallowed flags to be smuggled through the LDFLAGS sanitization by including them in the argument of another flag. This only affects usage of the gccgo compiler.
CVE-2023-29402
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 their names. Modules which are retrieved using the go command, i.e. via "go get", are not affected (modules retrieved using GOPATH-mode, i.e. GO111MODULE=off, may be affected).
(Closing as 23.x is no longer supported here.)
It appears that the current build for 23.0.6 was done with go 1.19.9. There are a number of CVE fixes in 1.19.10 (e.g. CVE-2023-29404. CVE-2023-29405, CVE-2023-29402).
Are there any plans to publish and other version for 23.0.x to address these issues?