chore(deps): update module github.com/docker/docker to v25 [security] - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/docker/docker	v24.0.7+incompatible -> v25.0.6+incompatible

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

CVE-2024-24557

The classic builder cache system is prone to cache poisoning if the image is built FROM scratch.
Also, changes to some instructions (most important being HEALTHCHECK and ONBUILD) would not cause a cache miss.

An attacker with the knowledge of the Dockerfile someone is using could poison their cache by making them pull a specially crafted image that would be considered as a valid cache candidate for some build steps.

For example, an attacker could create an image that is considered as a valid cache candidate for:

FROM scratch
MAINTAINER Pawel

when in fact the malicious image used as a cache would be an image built from a different Dockerfile.

In the second case, the attacker could for example substitute a different HEALTCHECK command.

Impact

23.0+ users are only affected if they explicitly opted out of Buildkit (DOCKER_BUILDKIT=0 environment variable) or are using the /build API endpoint (which uses the classic builder by default).

All users on versions older than 23.0 could be impacted. An example could be a CI with a shared cache, or just a regular Docker user pulling a malicious image due to misspelling/typosquatting.

Image build API endpoint (/build) and ImageBuild function from github.com/docker/docker/client is also affected as it the uses classic builder by default.

Patches

Patches are included in Moby releases:

• v25.0.2
• v24.0.9
• v23.0.10

Workarounds

• Use --no-cache or use Buildkit if possible (DOCKER_BUILDKIT=1, it's default on 23.0+ assuming that the buildx plugin is installed).
• Use Version = types.BuilderBuildKit or NoCache = true in ImageBuildOptions for ImageBuild call.

CVE-2024-41110

A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low. This advisory outlines the issue, identifies the affected versions, and provides remediation steps for impacted users.

Impact

Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.

A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted.

Docker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable.

Vulnerability details

• AuthZ bypass and privilege escalation: An attacker could exploit a bypass using an API request with Content-Length set to 0, causing the Docker daemon to forward the request without the body to the AuthZ plugin, which might approve the request incorrectly.
• Initial fix: The issue was fixed in Docker Engine v18.09.1 January 2019..
• Regression: The fix was not included in Docker Engine v19.03 or newer versions. This was identified in April 2024 and patches were released for the affected versions on July 23, 2024. The issue was assigned CVE-2024-41110.

Patches

• docker-ce v27.1.1 containes patches to fix the vulnerability.
• Patches have also been merged into the master, 19.0, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches.

Remediation steps

• If you are running an affected version, update to the most recent patched version.
• Mitigation if unable to update immediately:
  • Avoid using AuthZ plugins.
  • Restrict access to the Docker API to trusted parties, following the principle of least privilege.

References

• moby/moby@fc274cd
• moby/moby@a79fabb
• https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin/

---

Classic builder cache poisoning

CVE-2024-24557 / GHSA-xw73-rw38-6vjc / GO-2024-2512

More information

Details

The classic builder cache system is prone to cache poisoning if the image is built FROM scratch.
Also, changes to some instructions (most important being HEALTHCHECK and ONBUILD) would not cause a cache miss.

An attacker with the knowledge of the Dockerfile someone is using could poison their cache by making them pull a specially crafted image that would be considered as a valid cache candidate for some build steps.

For example, an attacker could create an image that is considered as a valid cache candidate for:

FROM scratch
MAINTAINER Pawel

when in fact the malicious image used as a cache would be an image built from a different Dockerfile.

In the second case, the attacker could for example substitute a different HEALTCHECK command.

Impact

23.0+ users are only affected if they explicitly opted out of Buildkit (DOCKER_BUILDKIT=0 environment variable) or are using the /build API endpoint (which uses the classic builder by default).

All users on versions older than 23.0 could be impacted. An example could be a CI with a shared cache, or just a regular Docker user pulling a malicious image due to misspelling/typosquatting.

Image build API endpoint (/build) and ImageBuild function from github.com/docker/docker/client is also affected as it the uses classic builder by default.

Patches

Patches are included in Moby releases:

• v25.0.2
• v24.0.9
• v23.0.10

Workarounds

• Use --no-cache or use Buildkit if possible (DOCKER_BUILDKIT=1, it's default on 23.0+ assuming that the buildx plugin is installed).
• Use Version = types.BuilderBuildKit or NoCache = true in ImageBuildOptions for ImageBuild call.

Severity

• CVSS Score: 6.9 / 10 (Medium)
• Vector String: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L

References

• https://github.com/moby/moby/security/advisories/GHSA-xw73-rw38-6vjc
• https://nvd.nist.gov/vuln/detail/CVE-2024-24557
• https://github.com/moby/moby/commit/3e230cfdcc989dc524882f6579f9e0dac77400ae
• https://github.com/moby/moby/commit/fca702de7f71362c8d103073c7e4a1d0a467fadd
• https://github.com/moby/moby/commit/fce6e0ca9bc000888de3daa157af14fa41fcd0ff
• https://github.com/moby/moby

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Classic builder cache poisoning in github.com/docker/docker

CVE-2024-24557 / GHSA-xw73-rw38-6vjc / GO-2024-2512

More information

Details

Classic builder cache poisoning in github.com/docker/docker

Severity

Unknown

References

• https://github.com/moby/moby/security/advisories/GHSA-xw73-rw38-6vjc
• https://github.com/moby/moby/commit/3e230cfdcc989dc524882f6579f9e0dac77400ae
• https://github.com/moby/moby/commit/fca702de7f71362c8d103073c7e4a1d0a467fadd
• https://github.com/moby/moby/commit/fce6e0ca9bc000888de3daa157af14fa41fcd0ff

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).

---

Moby authz zero length regression in github.com/moby/moby

CVE-2024-41110 / GHSA-v23v-6jw2-98fq / GO-2024-3005

More information

Details

Moby authz zero length regression in github.com/moby/moby

Severity

Unknown

References

• https://nvd.nist.gov/vuln/detail/CVE-2024-41110
• https://github.com/moby/moby/commit/411e817ddf710ff8e08fa193da80cb78af708191
• https://github.com/moby/moby/commit/42f40b1d6dd7562342f832b9cd2adf9e668eeb76
• https://github.com/moby/moby/commit/65cc597cea28cdc25bea3b8a86384b4251872919
• https://github.com/moby/moby/commit/852759a7df454cbf88db4e954c919becd48faa9b
• https://github.com/moby/moby/commit/a31260625655cff9ae226b51757915e275e304b0
• https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1
• https://github.com/moby/moby/commit/ae160b4edddb72ef4bd71f66b975a1a1cc434f00
• https://github.com/moby/moby/commit/ae2b3666c517c96cbc2adf1af5591a6b00d4ec0f
• https://github.com/moby/moby/commit/cc13f952511154a2866bddbb7dddebfe9e83b801
• https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb
• https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq
• https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).

---

Authz zero length regression

CVE-2024-41110 / GHSA-v23v-6jw2-98fq / GO-2024-3005

More information

Details

A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low. This advisory outlines the issue, identifies the affected versions, and provides remediation steps for impacted users.

Impact

Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.

A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted.

Docker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable.

Vulnerability details

• AuthZ bypass and privilege escalation: An attacker could exploit a bypass using an API request with Content-Length set to 0, causing the Docker daemon to forward the request without the body to the AuthZ plugin, which might approve the request incorrectly.
• Initial fix: The issue was fixed in Docker Engine v18.09.1 January 2019..
• Regression: The fix was not included in Docker Engine v19.03 or newer versions. This was identified in April 2024 and patches were released for the affected versions on July 23, 2024. The issue was assigned CVE-2024-41110.

Patches

• docker-ce v27.1.1 containes patches to fix the vulnerability.
• Patches have also been merged into the master, 19.0, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches.

Remediation steps

• If you are running an affected version, update to the most recent patched version.
• Mitigation if unable to update immediately:
  • Avoid using AuthZ plugins.
  • Restrict access to the Docker API to trusted parties, following the principle of least privilege.

References

• moby/moby@fc274cd
• moby/moby@a79fabb
• https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin/

Severity

• CVSS Score: 9.9 / 10 (Critical)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

References

• https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq
• https://nvd.nist.gov/vuln/detail/CVE-2024-41110
• https://github.com/moby/moby/commit/411e817ddf710ff8e08fa193da80cb78af708191
• https://github.com/moby/moby/commit/42f40b1d6dd7562342f832b9cd2adf9e668eeb76
• https://github.com/moby/moby/commit/65cc597cea28cdc25bea3b8a86384b4251872919
• https://github.com/moby/moby/commit/852759a7df454cbf88db4e954c919becd48faa9b
• https://github.com/moby/moby/commit/a31260625655cff9ae226b51757915e275e304b0
• https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1
• https://github.com/moby/moby/commit/ae160b4edddb72ef4bd71f66b975a1a1cc434f00
• https://github.com/moby/moby/commit/ae2b3666c517c96cbc2adf1af5591a6b00d4ec0f
• https://github.com/moby/moby/commit/cc13f952511154a2866bddbb7dddebfe9e83b801
• https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb
• https://github.com/moby/moby
• https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

docker/docker (github.com/docker/docker)

v25.0.6+incompatible

Compare Source

v25.0.5+incompatible

Compare Source

v25.0.4+incompatible

Compare Source

v25.0.3+incompatible

Compare Source

v25.0.2+incompatible

Compare Source

v25.0.1+incompatible

Compare Source

v25.0.0+incompatible

Compare Source

v24.0.9+incompatible

Compare Source

v24.0.8+incompatible

Compare Source

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.20 -> 1.22.5

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum

Command failed: go mod tidy
go: downloading gotest.tools/v3 v3.5.0
go: downloading go.uber.org/goleak v1.2.1
go: downloading github.com/onsi/ginkgo/v2 v2.13.0
go: downloading github.com/onsi/gomega v1.29.0
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.10.0
go: downloading go.opentelemetry.io/otel/sdk v1.10.0
go: downloading golang.org/x/exp v0.0.0-20231006140011-7918f672742d
go: downloading gopkg.in/check.v1 v1.0.0-20201130134442-10cb98267c6c
go: downloading github.com/moby/term v0.5.0
go: downloading github.com/morikuni/aec v1.0.0
go: downloading gomodules.xyz/jsonpatch/v2 v2.4.0
go: downloading github.com/imdario/mergo v0.3.16
go: downloading github.com/kr/pretty v0.3.1
go: downloading github.com/fsnotify/fsnotify v1.6.0
go: downloading github.com/prometheus/client_golang v1.17.0
go: downloading github.com/kr/text v0.2.0
go: downloading github.com/rogpeppe/go-internal v1.10.0
go: downloading github.com/go-task/slim-sprig v0.0.0-20230315185526-52ccab3ef572
go: downloading github.com/Azure/go-ansiterm v0.0.0-20230124172434-306776ec8161
go: downloading github.com/prometheus/client_model v0.5.0
go: downloading github.com/prometheus/common v0.45.0
go: downloading github.com/beorn7/perks v1.0.1
go: downloading github.com/cespare/xxhash/v2 v2.2.0
go: downloading github.com/prometheus/procfs v0.11.1
go: downloading github.com/google/pprof v0.0.0-20230926050212-f7f687d19a98
go: downloading github.com/matttproud/golang_protobuf_extensions/v2 v2.0.0
go: downloading github.com/matttproud/golang_protobuf_extensions v1.0.4
go: finding module for package go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp
go: finding module for package github.com/containerd/log
go: downloading go.opentelemetry.io/otel v1.28.0
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.28.0
go: downloading github.com/containerd/log v0.1.0
go: finding module for package go.opentelemetry.io/otel/semconv/v1.21.0
go: downloading go.opentelemetry.io/otel/exporters/otlp v0.20.1
go: downloading go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.28.0
go: downloading go.opentelemetry.io v0.1.0
go: found github.com/containerd/log in github.com/containerd/log v0.1.0
go: found go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp in go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.28.0
go: found go.opentelemetry.io/otel/semconv/v1.21.0 in go.opentelemetry.io/otel v1.28.0
go: downloading github.com/go-logr/logr v1.4.2
go: downloading golang.org/x/sync v0.7.0
go: downloading github.com/stretchr/testify v1.9.0
go: downloading golang.org/x/sys v0.21.0
go: downloading go.opentelemetry.io/otel/trace v1.28.0
go: downloading golang.org/x/net v0.26.0
go: downloading go.opentelemetry.io/otel/metric v1.28.0
go: downloading go.opentelemetry.io/otel/sdk v1.28.0
go: downloading golang.org/x/term v0.21.0
go: downloading google.golang.org/protobuf v1.34.2
go: downloading golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d
go: downloading github.com/sirupsen/logrus v1.9.3
go: downloading go.opentelemetry.io/proto/otlp v1.3.1
go: downloading github.com/google/uuid v1.6.0
go: downloading golang.org/x/text v0.16.0
go: downloading google.golang.org/grpc v1.64.0
go: downloading github.com/grpc-ecosystem/grpc-gateway/v2 v2.20.0
go: downloading github.com/cenkalti/backoff/v4 v4.3.0
go: downloading github.com/grpc-ecosystem/grpc-gateway v1.16.0
go: downloading google.golang.org/genproto/googleapis/api v0.0.0-20240701130421-f6361c86f094
go: downloading google.golang.org/genproto/googleapis/rpc v0.0.0-20240701130421-f6361c86f094
go: downloading google.golang.org/genproto v0.0.0-20230526161137-0005af68ea54
go: downloading golang.org/x/mod v0.17.0
go: finding module for package go.opentelemetry.io/otel/metric/instrument/syncfloat64
go: finding module for package go.opentelemetry.io/otel/metric/global
go: finding module for package go.opentelemetry.io/otel/metric/instrument/syncint64
go: github.com/doodlescheduling/yakmv imports
	github.com/docker/docker/client imports
	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp imports
	go.opentelemetry.io/otel/metric/global: module go.opentelemetry.io/otel/metric@latest found (v1.28.0), but does not contain package go.opentelemetry.io/otel/metric/global
go: github.com/doodlescheduling/yakmv imports
	github.com/docker/docker/client imports
	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp imports
	go.opentelemetry.io/otel/metric/instrument/syncfloat64: module go.opentelemetry.io/otel/metric@latest found (v1.28.0), but does not contain package go.opentelemetry.io/otel/metric/instrument/syncfloat64
go: github.com/doodlescheduling/yakmv imports
	github.com/docker/docker/client imports
	go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp imports
	go.opentelemetry.io/otel/metric/instrument/syncint64: module go.opentelemetry.io/otel/metric@latest found (v1.28.0), but does not contain package go.opentelemetry.io/otel/metric/instrument/syncint64