feat(deps): bump github.com/opencontainers/runc from 1.1.6 to 1.1.13

[dependabot]

Bumps github.com/opencontainers/runc from 1.1.6 to 1.1.13.

Release notes

Sourced from github.com/opencontainers/runc's releases.

runc 1.1.12 -- "Now you're thinking with Portals™!"

This is the twelfth patch release in the 1.1.z release branch of runc. It fixes a high-severity container breakout vulnerability involving leaked file descriptors, and users are strongly encouraged to update as soon as possible.

• Fix CVE-2024-21626, a container breakout attack that took advantage of a file descriptor that was leaked internally within runc (but never leaked to the container process).

  In addition to fixing the leak, several strict hardening measures were added to ensure that future internal leaks could not be used to break out in this manner again.

  Based on our research, while no other container runtime had a similar leak, none had any of the hardening steps we've introduced (and some runtimes would not check for any file descriptors that a calling process may have leaked to them, allowing for container breakouts due to basic user error).

Static Linking Notices

The runc binary distributed with this release are statically linked with the following GNU LGPL-2.1 licensed libraries, with runc acting as a "work that uses the Library":

• libseccomp

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 complete source code for those libraries which (when combined with the attached runc source code) may be used to exercise your rights under the LGPL-2.1.

However we strongly suggest that you make use of your distribution's packages or download them from the authoritative upstream sources, especially since these libraries are related to the security of your containers.

Thanks to all of the contributors who made this release possible:

• Aleksa Sarai cyphar@cyphar.com
• hang.jiang hang.jiang@daocloud.io
• lfbzhm lifubang@acmcoder.com

Signed-off-by: Aleksa Sarai cyphar@cyphar.com

... (truncated)

Changelog

Sourced from github.com/opencontainers/runc's changelog.

[1.1.13] - 2024-06-13

There is no certainty in the world. This is the only certainty I have.

Important Notes

• If building with Go 1.22.x, make sure to use 1.22.4 or a later version. (see #4233 for more details)

Fixed

• Support go 1.22.4+. (#4313)
• runc list: fix race with runc delete. (#4231)
• Fix set nofile rlimit error. (#4277, #4299)
• libct/cg/fs: fix setting rt_period vs rt_runtime. (#4284)
• Fix a debug msg for user ns in nsexec. (#4315)
• script/*: fix gpg usage wrt keyboxd. (#4316)
• CI fixes and misc backports. (#4241)
• Fix codespell warnings. (#4300)

Changed

• Silence security false positives from golang/net. (#4244)
• libcontainer: allow containers to make apps think fips is enabled/disabled for testing. (#4257)
• allow overriding VERSION value in Makefile. (#4270)
• Vagrantfile.fedora: bump Fedora to 39. (#4261)
• ci/cirrus: rm centos stream 8. (#4305, #4308)

[1.1.12] - 2024-01-31

Now you're thinking with Portals™!

Security

• Fix CVE-2024-21626, a container breakout attack that took advantage of a file descriptor that was leaked internally within runc (but never leaked to the container process). In addition to fixing the leak, several strict hardening measures were added to ensure that future internal leaks could not be used to break out in this manner again. Based on our research, while no other container runtime had a similar leak, none had any of the hardening steps we've introduced (and some runtimes would not check for any file descriptors that a calling process may have leaked to them, allowing for container breakouts due to basic user error).

[1.1.11] - 2024-01-01

Happy New Year!

... (truncated)

Commits

• 58aa920 VERSION: release 1.1.13
• 2b3a247 Merge pull request #4316 from lifubang/backport-4189
• 3507ada Merge pull request #4315 from lifubang/backport-4311
• 0f7150a script/*: fix gpg usage wrt keyboxd
• 80186fe fix a debug msg for user ns in nsexec
• 8407d3c Merge pull request #4313 from kolyshkin/1.1-backport-4292
• 7219e0a Dockerfile: bump Debian to 12, Go to 1.21
• c9beabc ci: switch to go 1.22 as main version
• 4578c6c libct/nsenter: stop blacklisting go 1.22+
• c488d13 use go mod instead of go get in spec.bats
• Additional commits viewable 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 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)

[dependabot]

The following labels could not be found: dependencies.

[koordinator-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign zwzhang0107 after the PR has been reviewed.
You can assign the PR to them by writing /assign @zwzhang0107 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment