[23.0] update to go1.20.13

[thaJeztah]

update to go1.20.13

go1.20.13 (released 2024-01-09) includes fixes to the runtime and the crypto/tls
package. See the Go 1.20.13 milestone on our issue tracker for details:

• https://github.com/golang/go/issues?q=milestone%3AGo1.20.13+label%3ACherryPickApproved
• full diff: golang/go@go1.20.12...go1.20.13

update to go1.20.12

go1.20.12 (released 2023-12-05) includes security fixes to the go command,
and the net/http and path/filepath packages, as well as bug fixes to the
compiler and the go command. See the Go 1.20.12 milestone on our issue
tracker for details.

• https://github.com/golang/go/issues?q=milestone%3AGo1.20.12+label%3ACherryPickApproved
• full diff: golang/go@go1.20.11...go1.20.12

from the security mailing:

[security] Go 1.21.5 and Go 1.20.12 are released

Hello gophers,

We have just released Go versions 1.21.5 and 1.20.12, minor point releases.

These minor releases include 3 security fixes following the security policy:

• net/http: limit chunked data overhead

  A malicious HTTP sender can use chunk extensions to cause a receiver
  reading from a request or response body to read many more bytes from
  the network than are in the body.

  A malicious HTTP client can further exploit this to cause a server to
  automatically read a large amount of data (up to about 1GiB) when a
  handler fails to read the entire body of a request.

  Chunk extensions are a little-used HTTP feature which permit including
  additional metadata in a request or response body sent using the chunked
  encoding. The net/http chunked encoding reader discards this metadata.
  A sender can exploit this by inserting a large metadata segment with
  each byte transferred. The chunk reader now produces an error if the
  ratio of real body to encoded bytes grows too small.

  Thanks to Bartek Nowotarski for reporting this issue.

  This is CVE-2023-39326 and Go issue https://go.dev/issue/64433.

• cmd/go: go get may unexpectedly fallback to insecure git

  Using go get to fetch a module with the ".git" suffix may unexpectedly
  fallback to the insecure "git://" protocol if the module is unavailable
  via the secure "https://" and "git+ssh://" protocols, even if GOINSECURE
  is not set for said module. This only affects users who are not using
  the module proxy and are fetching modules directly (i.e. GOPROXY=off).

  Thanks to David Leadbeater for reporting this issue.

  This is CVE-2023-45285 and Go issue https://go.dev/issue/63845.

• path/filepath: retain trailing \ when cleaning paths like \?\c:\

  Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the
  volume name in Windows paths starting with \?, resulting in
  filepath.Clean(\?\c:) returning \?\c: rather than \?\c:\ (among
  other effects). The previous behavior has been restored.

  This is an update to CVE-2023-45283 and Go issue https://go.dev/issue/64028.

update to go1.20.11

go1.20.11 (released 2023-11-07) includes security fixes to the path/filepath
package, as well as bug fixes to the linker and the net/http package. See the
Go 1.20.11 milestone on our issue tracker for details:

• https://github.com/golang/go/issues?q=milestone%3AGo1.20.11+label%3ACherryPickApproved
• full diff: golang/go@go1.20.10...go1.20.11

from the security mailing:

[security] Go 1.21.4 and Go 1.20.11 are released

Hello gophers,

We have just released Go versions 1.21.4 and 1.20.11, minor point releases.

These minor releases include 2 security fixes following the security policy:

• path/filepath: recognize \??\ as a Root Local Device path prefix.

  On Windows, a path beginning with \??\ is a Root Local Device path equivalent
  to a path beginning with \\?\. Paths with a \??\ prefix may be used to
  access arbitrary locations on the system. For example, the path \??\c:\x
  is equivalent to the more common path c:\x.

  The filepath package did not recognize paths with a \??\ prefix as special.

  Clean could convert a rooted path such as \a\..\??\b into
  the root local device path \??\b. It will now convert this
  path into .\??\b.

  IsAbs did not report paths beginning with \??\ as absolute.
  It now does so.

  VolumeName now reports the \??\ prefix as a volume name.

  Join(`, ??, b)could convert a seemingly innocent sequence of path elements into the root local device path??\b. It will now convert this to .??\b`.

  This is CVE-2023-45283 and https://go.dev/issue/63713.

• path/filepath: recognize device names with trailing spaces and superscripts

  The IsLocal function did not correctly detect reserved names in some cases:

  • reserved names followed by spaces, such as "COM1 ".
  • "COM" or "LPT" followed by a superscript 1, 2, or 3.

  IsLocal now correctly reports these names as non-local.

  This is CVE-2023-45284 and https://go.dev/issue/63713.

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

[vvoland]

Weird:

=== Failed
=== FAIL: github.com/docker/docker/integration-cli TestDockerCLIRunSuite/TestRunContainerWithRmFlagCannotStartContainer (12.18s)
    docker_cli_run_test.go:2773: timeout hit after 10s: waiting for container 'sparkles' to be removed

That failure doesn't seem to go away after multiple restarts 🤔

[thaJeztah]

Yeah, it's a flaky test;

• Flaky test: TestRunContainerWithRmFlagCannotStartContainer (on windows) #43679
• and older ones: racy tests TestRunContainerWithRmFlagExitCodeNotEqualToZero TestRunContainerWithRmFlagCannotStartContainer #11966

[thaJeztah]

Oh! You even had a draft PR for that one to investigate 😂 #43933

[vvoland]

Yeah I know it used to be flaky (it was fixed in a PR that couldn't be backported), but didn't expect it to be flaky 3 times in a row 😅

[thaJeztah]

Make that 4 times in a row now 😞

I think I've seen that before though, and it may be related to prior state when re-running. I can try if it goes green if I do a full re-run

[thaJeztah]

Rebased and updated to 1.20.13

[thaJeztah]

Rebased, as the flaky test should probably be fixed now 🤞

• [23.0 backport] Lock container when deleting its root directory #47110

[thaJeztah]

@corhere PTAL; all green now 👍