- Notifications
You must be signed in to change notification settings - Fork1.1k
Commitab93943
authored
chore: bump github.com/opencontainers/runc from 1.2.3 to 1.2.8 (#20674)
Bumps[github.com/opencontainers/runc](https://github.com/opencontainers/runc)from 1.2.3 to 1.2.8.<details><summary>Release notes</summary><p><em>Sourced from <ahref="https://github.com/opencontainers/runc/releases">github.com/opencontainers/runc'sreleases</a>.</em></p><blockquote><h2>runc v1.2.8 -- "鳥籠の中に囚われた屈辱を"</h2><blockquote><p>[!NOTE]Some vendors were given a pre-release version of this release.This public release includes two extra patches to fix regressionsdiscovered very late during the embargo period and were thus notincluded in the pre-release versions. Please update to this version.</p></blockquote><p>This release contains fixes for three high-severity securityvulnerabilities in runc (<ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-9493-h29p-rfm2">CVE-2025-31133</a>,<ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-qw9x-cqr3-wc7r">CVE-2025-52565</a>,and<ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-cgrx-mc8f-2prm">CVE-2025-52881</a>).All three vulnerabilities ultimately allow (throughdifferent methods) for full container breakouts by bypassing runc'srestrictions for writing to arbitrary <code>/proc</code> files.</p><h3>Security</h3><ul><li><p><ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-9493-h29p-rfm2">CVE-2025-31133</a>exploits an issue with how masked paths are implemented inrunc. When masking files, runc will bind-mount the container's<code>/dev/null</code>inode on top of the file. However, if an attacker can replace<code>/dev/null</code>with a symlink to some other procfs file, runc will instead bind-mountthesymlink target read-write. This issue affected all known runcversions.</p></li><li><p><ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-qw9x-cqr3-wc7r">CVE-2025-52565</a>is very similar in concept and application to<ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-9493-h29p-rfm2">CVE-2025-31133</a>,except that it exploits a flaw in <code>/dev/console</code>bind-mounts. When creating the <code>/dev/console</code> bind-mount (to<code>/dev/pts/$n</code>),if an attacker replaces <code>/dev/pts/$n</code> with a symlink thenrunc willbind-mount the symlink target over <code>/dev/console</code>. This issueaffected allversions of runc >= 1.0.0-rc3.</p></li><li><p><ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-cgrx-mc8f-2prm">CVE-2025-52881</a>is a more sophisticated variant of <ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-fh74-hm69-rqjw">CVE-2019-19921</a>,which was a flaw that allowed an attacker to trick runc into writing theLSMprocess labels for a container process into a dummy tmpfs file and thusnotapply the correct LSM labels to the container process. The mitigation weapplied for <ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-fh74-hm69-rqjw">CVE-2019-19921</a>was fairly limited and effectively only causedrunc to verify that when we write LSM labels that those labels areactualprocfs files. This issue affects all known runc versions.</p></li></ul><h3>Static Linking Notices</h3><p>The <code>runc</code> binary distributed with this release are<em>statically linked</em> withthe following <ahref="https://www.gnu.org/licenses/old-licenses/lgpl-2.1.en.html">GNULGPL-2.1</a> licensed libraries, with <code>runc</code> actingas a "work that uses the Library":</p><ul><li><a href="https://github.com/seccomp/libseccomp">libseccomp</a></li></ul><!-- raw HTML omitted --></blockquote><p>... (truncated)</p></details><details><summary>Changelog</summary><p><em>Sourced from <ahref="https://github.com/opencontainers/runc/blob/v1.2.8/CHANGELOG.md">github.com/opencontainers/runc'schangelog</a>.</em></p><blockquote><h2>[1.2.8] - 2025-11-05</h2><blockquote><p>鳥籠の中に囚われた屈辱を</p></blockquote><h3>Security</h3><p>This release includes fixes for the following high-severity securityissues:</p><ul><li><p><ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-9493-h29p-rfm2">CVE-2025-31133</a>exploits an issue with how masked paths are implemented inrunc. When masking files, runc will bind-mount the container's<code>/dev/null</code>inode on top of the file. However, if an attacker can replace<code>/dev/null</code>with a symlink to some other procfs file, runc will instead bind-mountthesymlink target read-write. This issue affected all known runcversions.</p></li><li><p><ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-qw9x-cqr3-wc7r">CVE-2025-52565</a>is very similar in concept and application to<ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-9493-h29p-rfm2">CVE-2025-31133</a>,except that it exploits a flaw in <code>/dev/console</code>bind-mounts. When creating the <code>/dev/console</code> bind-mount (to<code>/dev/pts/$n</code>),if an attacker replaces <code>/dev/pts/$n</code> with a symlink thenrunc willbind-mount the symlink target over <code>/dev/console</code>. This issueaffected allversions of runc >= 1.0.0-rc3.</p></li><li><p><ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-cgrx-mc8f-2prm">CVE-2025-52881</a>is a more sophisticated variant of <ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-fh74-hm69-rqjw">CVE-2019-19921</a>,which was a flaw that allowed an attacker to trick runc into writing theLSMprocess labels for a container process into a dummy tmpfs file and thusnotapply the correct LSM labels to the container process. The mitigation weapplied for <ahref="https://github.com/opencontainers/runc/security/advisories/GHSA-fh74-hm69-rqjw">CVE-2019-19921</a>was fairly limited and effectively only causedrunc to verify that when we write LSM labels that those labels areactualprocfs files. This issue affects all known runc versions.</p></li></ul><h2>[1.2.7] - 2025-09-05</h2><blockquote><p>さんをつけろよデコ助野郎！</p></blockquote><h3>Fixed</h3><ul><li>Removed preemptive "full access to cgroups" warning whencalling <code>runc pause</code> or <code>runc unpause</code> as anunprivileged user without<code>--systemd-cgroups</code>. Now the warning is only emitted if anactual permissionerror was encountered. (<ahref="https://redirect.github.com/opencontainers/runc/issues/4709">#4709</a>,<ahref="https://redirect.github.com/opencontainers/runc/issues/4720">#4720</a>)</li><li>Add time namespace to container config after checkpoint/restore.CRIU sinceversion 3.14 uses a time namespace for checkpoint/restore, however itwasnot joining the time namespace in runc. (<ahref="https://redirect.github.com/opencontainers/runc/issues/4696">#4696</a>,<ahref="https://redirect.github.com/opencontainers/runc/issues/4714">#4714</a>)</li><li>Container processes will no longer inherit the CPU affinity of runcbydefault. Instead, the default CPU affinity of container processes willbethe largest set of CPUs permitted by the container's cpuset cgroup andanyother system restrictions (such as isolated CPUs). (<ahref="https://redirect.github.com/opencontainers/runc/issues/4041">#4041</a>,<ahref="https://redirect.github.com/opencontainers/runc/issues/4815">#4815</a>,<ahref="https://redirect.github.com/opencontainers/runc/issues/4858">#4858</a>)</li></ul><!-- raw HTML omitted --></blockquote><p>... (truncated)</p></details><details><summary>Commits</summary><ul><li><ahref="https://github.com/opencontainers/runc/commit/eeb7e6024f9ee43876301b1d23c353384fa6dcdd"><code>eeb7e60</code></a>VERSION: release v1.2.8</li><li><ahref="https://github.com/opencontainers/runc/commit/cdee962c391af84a922252c283bd065e5cabb34b"><code>cdee962</code></a>merge private security patches into ghsa-release-1.2.8</li><li><ahref="https://github.com/opencontainers/runc/commit/b4cb2f5436a1110a1de4eec7335a791d2b30a868"><code>b4cb2f5</code></a>rootfs: re-allow dangling symlinks in mount targets</li><li><ahref="https://github.com/opencontainers/runc/commit/ee56b8571cc81d41f85b069671bb6d33fd235cf1"><code>ee56b85</code></a>openat2: improve resilience on busy systems</li><li><ahref="https://github.com/opencontainers/runc/commit/2462b68fa2d6618480e6a4f615661ee6e762d13a"><code>2462b68</code></a>Merge pull request <ahref="https://redirect.github.com/opencontainers/runc/issues/4943">#4943</a>from lifubang/backport-1.2-4934-4937</li><li><ahref="https://github.com/opencontainers/runc/commit/99e41a58f7a51cf1b6caa5bed58ffbe615193523"><code>99e41a5</code></a>ci: only run lint-extra job on PRs to main</li><li><ahref="https://github.com/opencontainers/runc/commit/f2a1c986629e82cffb3b7c01eee68405894f4783"><code>f2a1c98</code></a>CI: remove deprecated lima-vm/lima-actions/ssh</li><li><ahref="https://github.com/opencontainers/runc/commit/8f901856f96126285585e7343d7bc600013798fc"><code>8f90185</code></a>selinux: use safe procfs API for labels</li><li><ahref="https://github.com/opencontainers/runc/commit/948d6e9dbece33da25886f18c97a128c347e95ff"><code>948d6e9</code></a>rootfs: switch to fd-based handling of mountpoint targets</li><li><ahref="https://github.com/opencontainers/runc/commit/7aa42ade85d575294cf778b21edbd53c0171a3d4"><code>7aa42ad</code></a>libct: align param type for mountCgroupV1/V2 functions</li><li>Additional commits viewable in <ahref="https://github.com/opencontainers/runc/compare/v1.2.3...v1.2.8">compareview</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'talter 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 editsthat 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 afteryour CI passes on it- `@dependabot cancel merge` will cancel a previously requested mergeand block automerging- `@dependabot reopen` will reopen this PR if it is closed- `@dependabot close` will close this PR and stop Dependabot recreatingit. You can achieve the same result by closing it manually- `@dependabot show <dependency name> ignore conditions` will show allof the ignore conditions of the specified dependency- `@dependabot ignore this major version` will close this PR and stopDependabot creating any more for this major version (unless you reopenthe PR or upgrade to it yourself)- `@dependabot ignore this minor version` will close this PR and stopDependabot creating any more for this minor version (unless you reopenthe PR or upgrade to it yourself)- `@dependabot ignore this dependency` will close this PR and stopDependabot creating any more for this dependency (unless you reopen thePR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the[Security Alerts page](https://github.com/coder/coder/network/alerts).</details>Signed-off-by: dependabot[bot] <support@github.com>Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parent34f6e72 commitab93943
2 files changed
+5
-5
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
381 | 381 | | |
382 | 382 | | |
383 | 383 | | |
384 | | - | |
| 384 | + | |
385 | 385 | | |
386 | 386 | | |
387 | 387 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
985 | 985 | | |
986 | 986 | | |
987 | 987 | | |
988 | | - | |
989 | | - | |
| 988 | + | |
| 989 | + | |
990 | 990 | | |
991 | 991 | | |
992 | 992 | | |
| |||
1662 | 1662 | | |
1663 | 1663 | | |
1664 | 1664 | | |
1665 | | - | |
1666 | | - | |
| 1665 | + | |
| 1666 | + | |
1667 | 1667 | | |
1668 | 1668 | | |
1669 | 1669 | | |
| |||
0 commit comments
Comments
(0)