fix(deps): update module github.com/docker/docker to v25 [security] (release-2.9.x) #15902
+53,864
−28,912
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
area/security
dependencies
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
deps-update/release-2.9.x-go-github.com-docker-docker-vulnerability
branch
2 times, most recently
from
bbdca6d to
20ffa2d
Compare
renovate
bot
changed the title
renovate
bot
deleted the
deps-update/release-2.9.x-go-github.com-docker-docker-vulnerability
branch
renovate
bot
changed the title
renovate
bot
force-pushed
the
deps-update/release-2.9.x-go-github.com-docker-docker-vulnerability
branch
from
1d77fdd to
20ffa2d
Compare
renovate
bot
force-pushed
the
deps-update/release-2.9.x-go-github.com-docker-docker-vulnerability
branch
2 times, most recently
from
990a3ae to
04166c9
Compare
renovate
bot
force-pushed
the
deps-update/release-2.9.x-go-github.com-docker-docker-vulnerability
branch
from
04166c9 to
525c514
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
deps-update/release-2.9.x-go-github.com-docker-docker-vulnerability
branch
from
10d0166 to
525c514
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v23.0.15+incompatible->v25.0.6+incompatibleClassic 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
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
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
HEALTHCHECKandONBUILD) 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:
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
HEALTCHECKcommand.Impact
23.0+ users are only affected if they explicitly opted out of Buildkit (
DOCKER_BUILDKIT=0environment variable) or are using the/buildAPI 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) andImageBuildfunction fromgithub.com/docker/docker/clientis also affected as it the uses classic builder by default.Patches
Patches are included in Moby releases:
Workarounds
--no-cacheor use Buildkit if possible (DOCKER_BUILDKIT=1, it's default on 23.0+ assuming that the buildx plugin is installed).Version = types.BuilderBuildKitorNoCache = trueinImageBuildOptionsforImageBuildcall.Severity
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:LReferences
This data is provided by OSV and the GitHub Advisory 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
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Release Notes
docker/docker (github.com/docker/docker)
v25.0.6+incompatibleCompare Source
v25.0.5+incompatibleCompare Source
v25.0.4+incompatibleCompare Source
v25.0.3+incompatibleCompare Source
v25.0.2+incompatibleCompare Source
v25.0.1+incompatibleCompare Source
v25.0.0+incompatibleCompare Source
v24.0.9+incompatibleCompare Source
v24.0.8+incompatibleCompare Source
v24.0.7+incompatibleCompare Source
v24.0.6+incompatibleCompare Source
v24.0.5+incompatibleCompare Source
v24.0.4+incompatibleCompare Source
v24.0.3+incompatibleCompare Source
v24.0.2+incompatibleCompare Source
v24.0.1+incompatibleCompare Source
v24.0.0+incompatibleCompare Source
v23.0.16+incompatibleCompare Source
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.