Container Escape Vulnerability in CRI-O for Kubernetes Clusters
CVE-2022-0811

8.8HIGH

Key Information:

Vendor
Kubernetes
Status
Cri-o
Vendor
CVE Published:
16 March 2022

Badges

👾 Exploit Exists🟡 Public PoC🟣 EPSS 20%

Summary

A flaw in the CRI-O container runtime has been identified, which improperly sets kernel options for pods. This vulnerability allows an attacker with the ability to deploy a pod on a Kubernetes cluster using CRI-O to escape the container and execute arbitrary code as root on the host node where the compromised pod is running. This could potentially allow unauthorized access to the host environment and sensitive data, making it critical for organizations to assess their Kubernetes configurations and apply necessary updates.

Affected Version(s)

CRI-O cri-o 1.24.0, cri-o 1.23.2, cri-o 1.22.3, cri-o 1.21.6, cri-o 1.20.7, cri-o 1.19.6

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

webhook-cve-2022-0811
Created by spiarh

References

https://bugzilla.redhat.com/show_bug.cgi?id=2059475
x_refsource_MISC
https://github.com/cri-o/cri-o/security/advisories/GHSA-6...
x_refsource_MISC

EPSS Score

20% chance of being exploited in the next 30 days.

CVSS V3.1

Score:
8.8
Severity:
HIGH
Confidentiality:
High
Integrity:
High
Availability:
High
Attack Vector:
Network
Attack Complexity:
Low
Privileges Required:
Low
User Interaction:
None
Scope:
Unchanged

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

.