CVE-2022-41716

Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows. In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows. In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

The Go Programming Language.

Security Fix(es):

Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows. In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".(CVE-2022-41716)

Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows. In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows. In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

Fixed unsanitized NUL in environment variables in syscalls, os/exec (go#56327) (bsc#1204941). (CVE-2022-41716)

runtime: lock count" fatal error when cgo is enabled (go#56308)

These are all security issues fixed in the go1.18-1.18.8-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the go1.19-1.19.3-1.1 package on the GA media of openSUSE Tumbleweed.

This update for go1.19 fixes the following issues:

Update to go 1.19.3 (released 2022-11-01) (bsc#1200441):

Security fixes:

• CVE-2022-41716: Fixed unsanitized NUL in environment variables in syscalls, os/exec (go#56327) (bsc#1204941).

Bugfixes:

• runtime: lock count' fatal error when cgo is enabled (go#56308).
• cmd/compile: libFuzzer instrumentation fakePC overflow on 386 arch (go#56168).
• internal/fuzz: array literal initialization causes ICE 'unhandled stmt ASOP' while fuzzing (go#56106).

This update for go1.18 fixes the following issues:

Update to go 1.18.8 (released 2022-11-01) (bsc#1193742):

Security fixes:

• CVE-2022-41716: Fixed unsanitized NUL in environment variables in syscalls, os/exec (go#56327) (bsc#1204941).

Bugfixes:

• runtime: lock count' fatal error when cgo is enabled (go#56308).

This update for go1.18-openssl fixes the following issues:

• Add subpackage go1.x-libstd compiled shared object libstd.so (jsc#PED-1962)

  • Main go1.x package included libstd.so in previous versions
  • Split libstd.so into subpackage that can be installed standalone
  • Continues the slimming down of main go1.x package by 40 Mb
  • Experimental and not recommended for general use, Go currently has no ABI
  • Upstream Go has not committed to support buildmode=shared long-term
  • Do not use in packaging, build static single binaries (the default)
  • Upstream Go go1.x binary releases do not include libstd.so
  • go1.x Suggests go1.x-libstd so not installed by default Recommends
  • go1.x-libstd does not Require: go1.x so can install standalone
  • Provides go-libstd unversioned package name
  • Fix build step -buildmode=shared std to omit -linkshared

• Packaging improvements:

  • go1.x Suggests go1.x-doc so not installed by default Recommends
  • Use Group: Development/Languages/Go instead of Other

• Improvements to go1.x packaging spec:

  • On Tumbleweed bootstrap with current default gcc13 and gccgo118
  • On SLE-12 aarch64 ppc64le ppc64 remove overrides to bootstrap using go1.x package (%bcond_without gccgo). This is no longer needed on current SLE-12:Update and removing will consolidate the build configurations used.
  • Change source URLs to go.dev as per Go upstream
  • On x86_64 export GOAMD64=v1 as per the current baseline. At this time forgo GOAMD64=v3 option for x86_64_v3 support.
  • On x86_64 %define go_amd64=v1 as current instruction baseline

• Update to version 1.18.10.1 cut from the go1.18-openssl-fips branch at the revision tagged go1.18.10-1-openssl-fips.

  • Merge branch dev.boringcrypto.go1.18 into go1.18-openssl-fips
  • Merge go1.18.10 into dev.boringcrypto.go1.18

• go1.18.10 (released 2023-01-10) includes fixes to cgo, the compiler, the linker, and the crypto/x509, net/http, and syscall packages. Refs bsc#1193742 go1.18 release tracking

  • go#57705 misc/cgo: backport needed for dlltool fix
  • go#57426 crypto/x509: Verify on macOS does not return typed errors
  • go#57344 cmd/compile: the loong64 intrinsic for CompareAndSwapUint32 function needs to sign extend its 'old' argument.
  • go#57338 syscall, internal/poll: accept4-to-accept fallback removal broke Go code on Synology DSM 6.2 ARM devices
  • go#57213 os: TestLstat failure on Linux Aarch64
  • go#57211 reflect: sort.SliceStable sorts incorrectly on arm64 with less function created with reflect.MakeFunc and slice of sufficient length
  • go#57057 cmd/go: remove test dependency on gopkg.in service
  • go#57054 cmd/go: TestScript/version_buildvcs_git_gpg (if enabled) fails on linux longtest builders
  • go#57044 cgo: malformed DWARF TagVariable entry
  • go#57028 cmd/cgo: Wrong types in compiler errors with clang 14
  • go#56833 cmd/link/internal/ppc64: too-far trampoline is reused
  • go#56711 net: reenable TestLookupDotsWithRemoteSource and TestLookupGoogleSRV with a different target
  • go#56323 net/http: bad handling of HEAD requests with a body