MediumGHSA-w2j5-3rcx-vx7xGO-2022-0363

Sysctls applied to containers with host IPC or host network namespaces can affect the host

Published 15 Mar 2022 · Updated 21 Aug 2024

Is your project on an affected github.com/cri-o/cri-o?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=1.23.0 <1.23.1
Fixed in
1.23.1
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.23.1
Affected
>=1.22.0 <1.22.2
Fixed in
1.22.2
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.22.2
Affected
>=1.21.0 <1.21.5
Fixed in
1.21.5
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.21.5
Affected
>=1.20.0 <1.20.6
Fixed in
1.20.6
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.20.6
Affected
>=1.18.0 <1.19.5
Fixed in
1.19.5
Update to the fixed version for your release line, for example:go get github.com/cri-o/cri-o@v1.19.5

Details

Impact

Before setting the sysctls for a pod, the pods namespaces must be unshared (created). However, in cases where the pod is using a host network or IPC namespace, a bug in CRI-O caused the namespace creating tool pinns to configure the sysctls of the host. This allows a malicious user to set sysctls on the host, assuming they have access to hostNetwork and hostIPC.

Any CRI-O cluster after CRI-O 1.18 that drops the infra container 1.22 and 1.23 clusters drop infra container by default, and are thus vulnerable by default.

Patches

CRI-O versions 1.24.0, 1.23.1, 1.22.2, 1.21.5, 1.20.6, 1.19.5 all have the patches.

Workarounds

Users can set manage_ns_lifecycle to false, which causes the sysctls to be configured by the OCI runtime, which typically filter these cases. This option is available in 1.20 and 1.19. Newer versions don't have this option. An admission webhook could also be created to deny pods that use host IPC or network namespaces and also attempt to configure sysctls related to that namespace.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in the CRI-O repo
  • To make a report, email your vulnerability to the private

[cncf-crio-security@lists.cncf.io](mailto:cncf-crio-security@lists.cncf.io) list with the security details and the details expected for all CRI-O bug reports.

Is GHSA-w2j5-3rcx-vx7x in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/cri-o/cri-o, and gives you the command that fixes it.

More advisories for github.com/cri-o/cri-o

  • LowCVE-2025-4437CRI-O has Potential High Memory Consumption from File Read in github.com/cri-o/cri-o · 29 Aug 2025
  • MediumCVE-2025-4437CRI-O has Potential High Memory Consumption from File Read · 20 Aug 2025
  • LowCVE-2025-0750CRI-O Path Traversal vulnerability in github.com/cri-o/cri-o · 29 Jan 2025
  • MediumCVE-2025-0750CRI-O Path Traversal vulnerability · 28 Jan 2025
  • LowCVE-2024-8676CRI-O: Maliciously structured checkpoint file can gain arbitrary node access in github.com/cri-o/cri-o · 4 Dec 2024
  • MediumCVE-2024-8676CRI-O: Maliciously structured checkpoint file can gain arbitrary node access · 26 Nov 2024
All 25 advisories for github.com/cri-o/cri-o

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.