CVE-2022-0811GHSA-6X2M-W449-QWX7GO-2022-0354
A flaw was found in CRI-O in the way it set kernel options for a pod.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- n/a CRI-O
Version range not reported
- github.com/cri-o/cri-oGo
From 1.19.0 · fixed in 1.19.6
- github.com/cri-o/cri-oGo
From 1.20.0 · fixed in 1.20.7
- github.com/cri-o/cri-oGo
From 1.21.0 · fixed in 1.21.6
- github.com/cri-o/cri-oGo
From 1.22.0 · fixed in 1.22.3
- github.com/cri-o/cri-oGo
From 1.23.0 · fixed in 1.23.2
- github.com/cri-o/cri-oGo
From 1.19.0 · fixed in 1.19.6; From 1.20.0 · fixed in 1.20.7; From 1.21.0 · fixed in 1.21.6; From 1.22.0 · fixed in 1.22.3; From 1.23.0 · fixed in 1.23.2