{"answers":{"affected":"11 open source packages ship an affected version, including github.com/cri-o/cri-o.","exploited":"There is no known exploitation of GHSA-w2j5-3rcx-vx7x in the wild and no public exploit code.","fix":"Upgrade github.com/cri-o/cri-o to a fixed version for your release line: 1.19.5, 1.20.6, 1.21.5 or 1.22.2.","what":"GHSA-w2j5-3rcx-vx7x is a vulnerability in github.com/cri-o/cri-o, published on 15 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-w2j5-3rcx-vx7x and fix it if it is affected.\n\nWhat it is: GHSA-w2j5-3rcx-vx7x is a vulnerability in github.com/cri-o/cri-o, published on 15 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-w2j5-3rcx-vx7x in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/cri-o/cri-o (Go): affected from 1.18.0; fixed in 1.19.5, 1.20.6, 1.21.5, 1.22.2, 1.23.1\n- github.com/cri-o/cri-o (Go): affected from 1.18.0; fixed in 1.19.5\n- github.com/cri-o/cri-o (Go): affected from 1.18.0; fixed in 1.19.5\n- github.com/cri-o/cri-o (Go): affected from 1.20.0; fixed in 1.20.6\n- github.com/cri-o/cri-o (Go): affected from 1.20.0; fixed in 1.20.6\n- github.com/cri-o/cri-o (Go): affected from 1.21.0; fixed in 1.21.5\n- github.com/cri-o/cri-o (Go): affected from 1.21.0; fixed in 1.21.5\n- github.com/cri-o/cri-o (Go): affected from 1.22.0; fixed in 1.22.2\n- github.com/cri-o/cri-o (Go): affected from 1.22.0; fixed in 1.22.2\n- github.com/cri-o/cri-o (Go): affected from 1.23.0; fixed in 1.23.1\n- github.com/cri-o/cri-o (Go): affected from 1.23.0; fixed in 1.23.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-w2j5-3rcx-vx7x/ (Markdown: https://insights.sbomify.com/GHSA-w2j5-3rcx-vx7x/index.md)","id":"GHSA-w2j5-3rcx-vx7x","markdown":"https://insights.sbomify.com/GHSA-w2j5-3rcx-vx7x/index.md","name":"GHSA-w2j5-3rcx-vx7x","record":{"aliases":["GO-2022-0363"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CRI-O container runtime","requires_auth":"low_privilege","summary":"A bug in CRI-O allows users with host network or IPC access to modify host sysctls, potentially escalating privileges or bypassing security controls.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nBefore 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](https://github.com/cri-o/cri-o/tree/main/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.\n\nAny CRI-O cluster after CRI-O 1.18 that drops the infra container\n1.22 and 1.23 clusters drop infra container by default, and are thus vulnerable by default.\n\n### Patches\nCRI-O versions 1.24.0, 1.23.1, 1.22.2, 1.21.5, 1.20.6, 1.19.5 all have the patches.\n\n### Workarounds\nUsers 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.\nAn 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.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [the CRI-O repo](http://github.com/cri-o/cri-o/issues)\n* To make a report, email your vulnerability to the private\n[cncf-crio-security@lists.cncf.io](mailto:cncf-crio-security@lists.cncf.io) list\nwith the security details and the details expected for [all CRI-O bug\nreports](https://github.com/cri-o/cri-o/blob/main/.github/ISSUE_TEMPLATE/bug-report.yml).","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Sysctls applied to containers with host IPC or host network namespaces can affect the host","id":"GHSA-w2j5-3rcx-vx7x","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":11,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["1.19.5","1.20.6","1.21.5","1.22.2","1.23.1"],"introduced":["1.18.0","1.20.0","1.21.0","1.22.0","1.23.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":"pkg:golang/github.com/cri-o/cri-o","source":"GO-2022-0363"},{"ecosystem":"Go","fixed":["1.19.5"],"introduced":["1.18.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":null,"source":"GHSA-w2j5-3rcx-vx7x"},{"ecosystem":"Go","fixed":["1.19.5"],"introduced":["1.18.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":"pkg:golang/github.com/cri-o/cri-o","source":"GHSA-w2j5-3rcx-vx7x"},{"ecosystem":"Go","fixed":["1.20.6"],"introduced":["1.20.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":null,"source":"GHSA-w2j5-3rcx-vx7x"},{"ecosystem":"Go","fixed":["1.20.6"],"introduced":["1.20.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":"pkg:golang/github.com/cri-o/cri-o","source":"GHSA-w2j5-3rcx-vx7x"},{"ecosystem":"Go","fixed":["1.21.5"],"introduced":["1.21.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":null,"source":"GHSA-w2j5-3rcx-vx7x"},{"ecosystem":"Go","fixed":["1.21.5"],"introduced":["1.21.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":"pkg:golang/github.com/cri-o/cri-o","source":"GHSA-w2j5-3rcx-vx7x"},{"ecosystem":"Go","fixed":["1.22.2"],"introduced":["1.22.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":null,"source":"GHSA-w2j5-3rcx-vx7x"},{"ecosystem":"Go","fixed":["1.22.2"],"introduced":["1.22.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":"pkg:golang/github.com/cri-o/cri-o","source":"GHSA-w2j5-3rcx-vx7x"},{"ecosystem":"Go","fixed":["1.23.1"],"introduced":["1.23.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":null,"source":"GHSA-w2j5-3rcx-vx7x"},{"ecosystem":"Go","fixed":["1.23.1"],"introduced":["1.23.0"],"last_affected":[],"package":"github.com/cri-o/cri-o","purl":"pkg:golang/github.com/cri-o/cri-o","source":"GHSA-w2j5-3rcx-vx7x"}],"products":null,"published":"2022-03-15","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A bug in CRI-O allows users with host network or IPC access to modify host sysctls, potentially escalating privileges or bypassing security controls.","url":"https://insights.sbomify.com/GHSA-w2j5-3rcx-vx7x/"}