Description
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.
Published: 2022-03-16
Score: 8.8 High
EPSS: 23.8% Moderate
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-6x2m-w449-qwx7 Code Injection in CRI-O
History

No history.

Subscriptions

Kubernetes Cri-o
Redhat Openshift
cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

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

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

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