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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-6x2m-w449-qwx7 | Code Injection in CRI-O |
References
History
No history.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2024-08-02T23:40:04.258Z
Reserved: 2022-03-01T00:00:00.000Z
Link: CVE-2022-0811
No data.
Status : Modified
Published: 2022-03-16T15:15:16.123
Modified: 2024-11-21T06:39:26.720
Link: CVE-2022-0811
OpenCVE Enrichment
No data.
Weaknesses
Github GHSA