starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00

docker from 20.10.19+incompatible to 20.10.20+incompatible #1926

New issue

Closed

opened 2026-03-01 21:53:16 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 21:53:16 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/nektos/act/pull/1403
Author: @dependabot[bot]
Created: 10/24/2022
Status: ✅ Merged
Merged: 10/24/2022
Merged by: @mergify[bot]

Base: master ← Head: dependabot/go_modules/github.com/docker/docker-20.10.20incompatible

📝 Commits (2)

b3ecd32 build(deps): bump github.com/docker/docker
807e4a5 Merge branch 'master' into dependabot/go_modules/github.com/docker/docker-20.10.20incompatible

📊 Changes

2 files changed (+3 additions, -3 deletions)

View changed files

📝 go.mod (+1 -1)
📝 go.sum (+2 -2)

📄 Description

Bumps github.com/docker/docker from 20.10.19+incompatible to 20.10.20+incompatible.

Release notes

Sourced from github.com/docker/docker's releases.

v20.10.20

This release of Docker Engine contains partial mitigations for a Git vulnerability (CVE-2022-39253), and has updated handling of image:tag@digest image references.

The Git vulnerability allows a maliciously crafted Git repository, when used as a build context, to copy arbitrary filesystem paths into resulting containers/images; this can occur in both the daemon, and in API clients, depending on the versions and tools in use.

The mitigations available in this release and in other consumers of the daemon API are partial and only protect users who build a Git URL context (e.g. git+protocol://). As the vulnerability could still be exploited by manually run Git commands that interact with and check out submodules, users should immediately upgrade to a patched version of Git to protect against this vulernability. Further details are available from the GitHub blog ("Git security vulnerabilities announced").

Client

Added a mitigation for CVE-2022-39253, when using the classic Builder with a Git URL as the build context.

Daemon

Updated handling of image:tag@digest references. When pulling an image using the image:tag@digest ("pull by digest"), image resolution happens through the content-addressable digest and the image and tag are not used. While this is expected, this could lead to confusing behavior, and could potentially be exploited through social engineering to run an image that is already present in the local image store. Docker now checks if the digest matches the repository name used to pull the image, and otherwise will produce an error.

Builder

Updated handling of image:tag@digest references. Refer to the "Daemon" section above for details.

Added a mitigation to the classic Builder and updated BuildKit to v0.8.3-31-gc0149372, for CVE-2022-39253.

Commits

03df974 Merge pull request #6 from moby/ghsa-ambiguous-pull-by-digest
3adff51 Merge pull request #9 from moby/update_buildkit
d7c33ad Merge pull request #8 from moby/20.10_fix_git_file_leak
2f3bf18 [20.10] vendor moby/buildkit v0.8.3-31-gc0149372
4b9902b Validate digest in repo for pull by digest
c0d1188 builder: make git config isolation opt-in
9f5f3ab builder: isolate git from local system
10db4c2 builder: explicitly set CWD for all git commands
8816c3c builder: modernize TestCheckoutGit
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/nektos/act/pull/1403 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 10/24/2022 **Status:** ✅ Merged **Merged:** 10/24/2022 **Merged by:** [@mergify[bot]](https://github.com/apps/mergify) **Base:** `master` ← **Head:** `dependabot/go_modules/github.com/docker/docker-20.10.20incompatible` --- ### 📝 Commits (2) - [`b3ecd32`](https://github.com/nektos/act/commit/b3ecd32155c2d199275e96488896752eccbd35bc) build(deps): bump github.com/docker/docker - [`807e4a5`](https://github.com/nektos/act/commit/807e4a52dcd96d8c93dd7894479a7a4b34138efe) Merge branch 'master' into dependabot/go_modules/github.com/docker/docker-20.10.20incompatible ### 📊 Changes **2 files changed** (+3 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `go.mod` (+1 -1) 📝 `go.sum` (+2 -2) </details> ### 📄 Description Bumps [github.com/docker/docker](https://github.com/docker/docker) from 20.10.19+incompatible to 20.10.20+incompatible. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/docker/docker/releases">github.com/docker/docker's releases</a>.</em></p> <blockquote> <h2>v20.10.20</h2> <p>This release of Docker Engine contains partial mitigations for a Git vulnerability (<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253">CVE-2022-39253</a>), and has updated handling of <code>image:tag@digest</code> image references.</p> <p>The Git vulnerability allows a maliciously crafted Git repository, when used as a build context, to copy arbitrary filesystem paths into resulting containers/images; this can occur in both the daemon, and in API clients, depending on the versions and tools in use.</p> <p>The mitigations available in this release and in other consumers of the daemon API are partial and only protect users who build a Git URL context (e.g. <code>git+protocol://</code>). As the vulnerability could still be exploited by manually run Git commands that interact with and check out submodules, users should immediately upgrade to a patched version of Git to protect against this vulernability. Further details are available from the GitHub blog (<a href="https://github.blog/2022-10-18-git-security-vulnerabilities-announced/">"Git security vulnerabilities announced"</a>).</p> <h3>Client</h3> <ul> <li>Added a mitigation for <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253">CVE-2022-39253</a>, when using the classic Builder with a Git URL as the build context.</li> </ul> <h3>Daemon</h3> <ul> <li>Updated handling of <code>image:tag@digest</code> references. When pulling an image using the <code>image:tag@digest</code> ("pull by digest"), image resolution happens through the content-addressable digest and the <code>image</code> and <code>tag</code> are not used. While this is expected, this could lead to confusing behavior, and could potentially be exploited through social engineering to run an image that is already present in the local image store. Docker now checks if the digest matches the repository name used to pull the image, and otherwise will produce an error.</li> </ul> <h3>Builder</h3> <ul> <li>Updated handling of <code>image:tag@digest</code> references. Refer to the "Daemon" section above for details.</li> <li>Added a mitigation to the classic Builder and updated BuildKit to <a href="https://github.com/moby/buildkit/commit/c014937225cba29cfb1d5161fd134316c0e9bdaa">v0.8.3-31-gc0149372</a>, for <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-39253">CVE-2022-39253</a>.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/moby/moby/commit/03df974ae9e6c219862907efdd76ec2e77ec930b"><code>03df974</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/docker/docker/issues/6">#6</a> from moby/ghsa-ambiguous-pull-by-digest</li> <li><a href="https://github.com/moby/moby/commit/3adff51f8537b334fef5421f9e30d7162aec039f"><code>3adff51</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/docker/docker/issues/9">#9</a> from moby/update_buildkit</li> <li><a href="https://github.com/moby/moby/commit/d7c33ad827aea4ec35451ef06b6cb34952dc93db"><code>d7c33ad</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/docker/docker/issues/8">#8</a> from moby/20.10_fix_git_file_leak</li> <li><a href="https://github.com/moby/moby/commit/2f3bf180143ebdccb9ebd8b8d7c7faf7c1783889"><code>2f3bf18</code></a> [20.10] vendor moby/buildkit v0.8.3-31-gc0149372</li> <li><a href="https://github.com/moby/moby/commit/4b9902bad44373b43f2ba55d6b587dbe8505b86f"><code>4b9902b</code></a> Validate digest in repo for pull by digest</li> <li><a href="https://github.com/moby/moby/commit/c0d1188c146e793a8a98f3a4105f73c66e662b0a"><code>c0d1188</code></a> builder: make git config isolation opt-in</li> <li><a href="https://github.com/moby/moby/commit/9f5f3abcee28e70ffe8dc5c72c8b034c9cab5ebb"><code>9f5f3ab</code></a> builder: isolate git from local system</li> <li><a href="https://github.com/moby/moby/commit/10db4c2db7a7588913bd358670344e2ad3efbdb5"><code>10db4c2</code></a> builder: explicitly set CWD for all git commands</li> <li><a href="https://github.com/moby/moby/commit/8816c3c2aa9973d708e138905cd4199b883408ad"><code>8816c3c</code></a> builder: modernize TestCheckoutGit</li> <li>See full diff in <a href="https://github.com/docker/docker/compare/v20.10.19...v20.10.20">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=github.com/docker/docker&package-manager=go_modules&previous-version=20.10.19+incompatible&new-version=20.10.20+incompatible)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-03-01 21:53:16 +03:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1926

No description provided.

Rows
Columns