A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deployed.

Project Subscriptions

Vendors Products
Kubernetes Subscribe
Openshift Subscribe
Advisories
Source ID Title
Github GHSA Github GHSA GHSA-6x2m-w449-qwx7 Code Injection in CRI-O
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2024-08-02T23:40:04.258Z

Reserved: 2022-03-01T00:00:00

Link: CVE-2022-0811

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2022-03-16T15:15:16.123

Modified: 2024-11-21T06:39:26.720

Link: CVE-2022-0811

cve-icon Redhat

Severity : Important

Publid Date: 2022-03-15T14:00:00Z

Links: CVE-2022-0811 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses