CVE-2022-0811

moderate-risk

Published 2022-03-16

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.

Do I need to act?

21.3% chance of exploitation in next 30 days

EPSS score — higher than 79% of all CVEs

Not on CISA KEV list

No confirmed active exploitation reported to CISA

Patch status unknown

Check vendor advisories for fix availability and mitigation guidance

CVSS 8.8/10 High

NETWORK / LOW complexity

Affected Products (1)

Cri-O

Affected Vendors

Kubernetes

References (4)

Issue Tracking https://bugzilla.redhat.com/show_bug.cgi?id=2059475

Third Party Advisory https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7

Issue Tracking https://bugzilla.redhat.com/show_bug.cgi?id=2059475

Third Party Advisory https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7

/ 100

moderate-risk

Severity 30/34 · Critical

Exploitability 14/34 · Moderate

Exposure 5/34 · Minimal