ALAS2023-2023-269

html/template: improper handling of empty HTML attributes.

Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input could result in output that would have unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags. (CVE-2023-29400)

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). (CVE-2023-29402)

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)

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-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. 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-29405)

aarch64:
    golang-1.20.5-1.amzn2023.0.2.aarch64
    golang-bin-1.20.5-1.amzn2023.0.2.aarch64
    golang-shared-1.20.5-1.amzn2023.0.2.aarch64

noarch:
    golang-docs-1.20.5-1.amzn2023.0.2.noarch
    golang-misc-1.20.5-1.amzn2023.0.2.noarch
    golang-src-1.20.5-1.amzn2023.0.2.noarch
    golang-tests-1.20.5-1.amzn2023.0.2.noarch

src:
    golang-1.20.5-1.amzn2023.0.2.src

x86_64:
    golang-1.20.5-1.amzn2023.0.2.x86_64
    golang-bin-1.20.5-1.amzn2023.0.2.x86_64
    golang-shared-1.20.5-1.amzn2023.0.2.x86_64