CRI-O - v1.23.4

Security

CRI-O v1.23.4

The release notes have been generated for the commit range
v1.23.3...a6a1e6e on Fri, 21 Oct 2022 11:17:29 EDT.

Downloads

Download one of our static release bundles via our Google Cloud Bucket:

Changelog since v1.23.3

Changes by Kind

Feature

  • CRI-O now logs the stage of container or pod creation under system load. This allows users to find why their creation requests are stalling. (#6303, @haircommander)

Bug or Regression

  • Fix CVE-2022-27652 by dropping and refusing to add any inheritable capabilities (#5770, @haircommander)
  • Fix a bug where ExecSync requests (exec probes) could use an arbitrary amount of memory and disk. Output from ExecSync requests is now limited to 16MB (the amount that exec output was limited to in the dockershim). Disk limiting requires conmon 2.1.2 to work. See https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j and CVE-2022-1708 for more information. (#5937, @haircommander)
  • Fix a bug where child processes of containers in the host's PID namespace appear to leak after the child exits (#5977, @haircommander)
  • Fix a panic caused by using the improper Result structure version when setting up CNI plugins (#6320, @juanfresia)
  • Revert fix for CVE-2022-27652 by re-adding inheritable capabilities. While there is a workaround, we believe this causes regression mid cycle with is contrary to CRI-O's backporting policy. The risk of the CVE is low, and so there is little risk in reverting here. (#6168, @haircommander)
  • Update cni_default_network to not be commented by default in the output of crio config (#5566, @haircommander)

Uncategorized

Dependencies

Added

  • github.com/networkplumbing/go-nft: v0.2.0
  • github.com/onsi/ginkgo/v2: v2.1.4

Changed

Removed

Nothing has changed.


Details

date
Oct. 21, 2022, 2:15 p.m.
name
v1.23.4
type
Patch
👇
Register or login to:
  • 🔍View and search all CRI-O releases.
  • 🛠️Create and share lists to track your tools.
  • 🚨Setup notifications for major, security, feature or patch updates.
  • 🚀Much more coming soon!
Continue with GitHub
Continue with Google
or