dependabot[bot] opened a new pull request, #764: URL: https://github.com/apache/dubbo-kubernetes/pull/764
Bumps [github.com/opencontainers/runc](https://github.com/opencontainers/runc) from 1.1.7 to 1.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/opencontainers/runc/releases";>github.com/opencontainers/runc's releases</a>.</em></p> <blockquote> <h2>runc v1.2.0 -- "できるときにできることをやるんだ。それが今だ。"</h2> <p>This is the long-awaited release of runc 1.2.0! The primary changes from rc3 are general improvements and fixes for minor regressions related to the new /proc/self/exe cloning logic in runc 1.2, follow-on patches related to CVE-2024-45310, as well as some other minor changes.</p> <ul> <li>In order to alleviate the remaining concerns around the memory usage and (arguably somewhat unimportant, but measurable) performance overhead of memfds for cloning <code>/proc/self/exe</code>, we have added a new protection using <code>overlayfs</code> that is used if you have enough privileges and the running kernel supports it. It has effectively no performance nor memory overhead (compared to no cloning at all). (<a href="https://redirect.github.com/opencontainers/runc/issues/4448";>#4448</a>)</li> <li>The original fix for <a href="https://github.com/opencontainers/runc/security/advisories/GHSA-jfvp-7x6p-h2pv";>CVE-2024-45310</a> was intentionally very limited in scope to make it easier to review, however it also did not handle all possible <code>os.MkdirAll</code> cases and thus could lead to regressions. We have switched to the more complete implementation in the newer versions of <code>github.com/cyphar/filepath-securejoin</code>. (<a href="https://redirect.github.com/opencontainers/runc/issues/4393";>#4393</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4400";>#4400</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4421";>#4421</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4430";>#4430</a>)</li> <li>In certain situations (a system with lots of mounts or racing mounts) we could accidentally end up leaking mounts from the container into the host. This has been fixed. (<a href="https://redirect.github.com/opencontainers/runc/issues/4417";>#4417</a>)</li> <li>The fallback logic for <code>O_TMPFILE</code> clones of <code>/proc/self/exe</code> had a minor bug that would cause us to miss non-<code>noexec</code> directories and thus fail to start containers on some systems. (<a href="https://redirect.github.com/opencontainers/runc/issues/4444";>#4444</a>)</li> <li>Sometimes the cloned <code>/proc/self/exe</code> file descriptor could be placed in a way that it would get clobbered by the Go runtime. We had a fix for this already but it turns out it could still break in rare circumstances, but it has now been fixed. (<a href="https://redirect.github.com/opencontainers/runc/issues/4294";>#4294</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4452";>#4452</a>)</li> <li>It is not possible for <code>runc kill</code> to work properly in some specific configurations (such as rootless containers with no cgroups and a shared pid namespace). We now output a warning for such configurations. (<a href="https://redirect.github.com/opencontainers/runc/issues/4398";>#4398</a>)</li> <li>memfd-bind: update the documentation and make path handling with the systemd unit more idiomatic. (<a href="https://redirect.github.com/opencontainers/runc/issues/4428";>#4428</a>)</li> <li>We now use v0.16 of Cilium's eBPF library, including fixes that quite a few downstreams asked for. (<a href="https://redirect.github.com/opencontainers/runc/issues/4397";>#4397</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4396";>#4396</a>)</li> <li>Some internal <code>runc init</code> synchronisation that was no longer necessary (due to the <code>/proc/self/exe</code> cloning move to Go) was removed. (<a href="https://redirect.github.com/opencontainers/runc/issues/4441";>#4441</a>)</li> </ul> <h3>Static Linking Notices</h3> <p>The <code>runc</code> binary distributed with this release are <em>statically linked</em> with the following <a href="https://www.gnu.org/licenses/old-licenses/lgpl-2.1.en.html";>GNU LGPL-2.1</a> licensed libraries, with <code>runc</code> acting as a "work that uses the Library":</p> <ul> <li><a href="https://github.com/seccomp/libseccomp";>libseccomp</a></li> </ul> <p>The versions of these libraries were not modified from their upstream versions, but in order to comply with the LGPL-2.1 (§6(a)), we have attached the</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/opencontainers/runc/blob/main/CHANGELOG.md";>github.com/opencontainers/runc's changelog</a>.</em></p> <blockquote> <h2>[1.2.0] - 2024-10-22</h2> <blockquote> <p>できるときにできることをやるんだ。それが今だ。</p> </blockquote> <h3>Added</h3> <ul> <li>In order to alleviate the remaining concerns around the memory usage and (arguably somewhat unimportant, but measurable) performance overhead of memfds for cloning <code>/proc/self/exe</code>, we have added a new protection using <code>overlayfs</code> that is used if you have enough privileges and the running kernel supports it. It has effectively no performance nor memory overhead (compared to no cloning at all). (<a href="https://redirect.github.com/opencontainers/runc/issues/4448";>#4448</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>The original fix for <a href="https://github.com/opencontainers/runc/security/advisories/GHSA-jfvp-7x6p-h2pv";>CVE-2024-45310</a> was intentionally very limited in scope to make it easier to review, however it also did not handle all possible <code>os.MkdirAll</code> cases and thus could lead to regressions. We have switched to the more complete implementation in the newer versions of <code>github.com/cyphar/filepath-securejoin</code>. (<a href="https://redirect.github.com/opencontainers/runc/issues/4393";>#4393</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4400";>#4400</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4421";>#4421</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4430";>#4430</a>)</li> <li>In certain situations (a system with lots of mounts or racing mounts) we could accidentally end up leaking mounts from the container into the host. This has been fixed. (<a href="https://redirect.github.com/opencontainers/runc/issues/4417";>#4417</a>)</li> <li>The fallback logic for <code>O_TMPFILE</code> clones of <code>/proc/self/exe</code> had a minor bug that would cause us to miss non-<code>noexec</code> directories and thus fail to start containers on some systems. (<a href="https://redirect.github.com/opencontainers/runc/issues/4444";>#4444</a>)</li> <li>Sometimes the cloned <code>/proc/self/exe</code> file descriptor could be placed in a way that it would get clobbered by the Go runtime. We had a fix for this already but it turns out it could still break in rare circumstances, but it has now been fixed. (<a href="https://redirect.github.com/opencontainers/runc/issues/4294";>#4294</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4452";>#4452</a>)</li> </ul> <h3>Changed</h3> <ul> <li>It is not possible for <code>runc kill</code> to work properly in some specific configurations (such as rootless containers with no cgroups and a shared pid namespace). We now output a warning for such configurations. (<a href="https://redirect.github.com/opencontainers/runc/issues/4398";>#4398</a>)</li> <li>memfd-bind: update the documentation and make path handling with the systemd unit more idiomatic. (<a href="https://redirect.github.com/opencontainers/runc/issues/4428";>#4428</a>)</li> <li>We now use v0.16 of Cilium's eBPF library, including fixes that quite a few downstreams asked for. (<a href="https://redirect.github.com/opencontainers/runc/issues/4397";>#4397</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4396";>#4396</a>)</li> <li>Some internal <code>runc init</code> synchronisation that was no longer necessary (due to the <code>/proc/self/exe</code> cloning move to Go) was removed. (<a href="https://redirect.github.com/opencontainers/runc/issues/4441";>#4441</a>)</li> </ul> <h2>[1.2.0-rc.3] - 2024-09-02</h2> <blockquote> <p>The supreme happiness of life is the conviction that we are loved.</p> </blockquote> <h3>Security</h3> <ul> <li>Fix <a href="https://github.com/opencontainers/runc/security/advisories/GHSA-jfvp-7x6p-h2pv";>CVE-2024-45310</a>, a low-severity attack that allowed maliciously configured containers to create empty files and directories on</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/opencontainers/runc/commit/0b9fa21be2bcba45f6d9d748b4bcf70cfbffbc19";><code>0b9fa21</code></a> VERSION: release v1.2.0</li> <li><a href="https://github.com/opencontainers/runc/commit/5190d6124bd65d92468abad364660e5a2978f149";><code>5190d61</code></a> Merge pull request <a href="https://redirect.github.com/opencontainers/runc/issues/4452";>#4452</a> from lifubang/fix-fd-reuse-race</li> <li><a href="https://github.com/opencontainers/runc/commit/ca45a2c52db89dd3dbf04fb10964aa7a7e3e4959";><code>ca45a2c</code></a> merge <a href="https://redirect.github.com/opencontainers/runc/issues/4446";>#4446</a> into opencontainers/runc:main</li> <li><a href="https://github.com/opencontainers/runc/commit/568231cc4ef4b0c20ff50185c006d48827903fe4";><code>568231c</code></a> Revert "increase memory.max in cgroups.bats"</li> <li><a href="https://github.com/opencontainers/runc/commit/e66992669172d1b5a10e553dc40a7c1853097d85";><code>e669926</code></a> fix an error caused by fd reuse race when starting runc init</li> <li><a href="https://github.com/opencontainers/runc/commit/ca8ca3ce07403327ecc998cf031b3ec9d22d8c63";><code>ca8ca3c</code></a> Merge pull request <a href="https://redirect.github.com/opencontainers/runc/issues/4448";>#4448</a> from cyphar/cloned-binary-overlayfs</li> <li><a href="https://github.com/opencontainers/runc/commit/08faf151069ed3a54f5d2b2770c09ee644c9d703";><code>08faf15</code></a> Merge pull request <a href="https://redirect.github.com/opencontainers/runc/issues/4429";>#4429</a> from kolyshkin/cap-load</li> <li><a href="https://github.com/opencontainers/runc/commit/515f09f7b1dbd442298132592c7e9689b855dbdf";><code>515f09f</code></a> dmz: use overlayfs to write-protect /proc/self/exe if possible</li> <li><a href="https://github.com/opencontainers/runc/commit/8cfbccb6d99a1bcfad5b16fb3f0bbca97cb5be4c";><code>8cfbccb</code></a> tests: integration: add helper to check if we're in a userns</li> <li><a href="https://github.com/opencontainers/runc/commit/8bebdbafd8e5199d7734747a91ba7e8dd369aca8";><code>8bebdba</code></a> Merge pull request <a href="https://redirect.github.com/opencontainers/runc/issues/4456";>#4456</a> from kolyshkin/misc-ci-cleanups</li> <li>Additional commits viewable in <a href="https://github.com/opencontainers/runc/compare/v1.1.7...v1.2.0";>compare view</a></li> </ul> </details> <br /> [](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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/dubbo-kubernetes/network/alerts). </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org For additional commands, e-mail: notifications-h...@dubbo.apache.org
