CVE-2022-0811: Code Injection
First published: Tue Mar 01 2022(Updated: )
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/cri-o | <0:1.23.1-12.rhaos4.10.git1607c6e.el7 | 0:1.23.1-12.rhaos4.10.git1607c6e.el7 |
| redhat/cri-o | <0:1.19.5-3.rhaos4.6.git91f8458.el8 | 0:1.19.5-3.rhaos4.6.git91f8458.el8 |
| redhat/cri-o | <0:1.20.6-11.rhaos4.7.git76ea3d0.el8 | 0:1.20.6-11.rhaos4.7.git76ea3d0.el8 |
| redhat/cri-o | <0:1.21.5-3.rhaos4.8.gitaf64931.el8 | 0:1.21.5-3.rhaos4.8.gitaf64931.el8 |
| redhat/cri-o | <0:1.22.2-3.rhaos4.9.gitb030be8.el8 | 0:1.22.2-3.rhaos4.9.gitb030be8.el8 |
| Kubernetes CRI-O | >=1.19.0<1.19.6 | |
| Kubernetes CRI-O | >=1.20.0<1.20.7 | |
| Kubernetes CRI-O | >=1.21.0<1.21.6 | |
| Kubernetes CRI-O | >=1.22.0<1.22.3 | |
| Kubernetes CRI-O | >=1.23.0<1.23.2 |
Remedy
Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://bugzilla.redhat.com/show_bug.cgi?id=2059475
- https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2064293
- https://access.redhat.com/errata/RHSA-2022:0810
- https://access.redhat.com/security/cve/cve-2022-0811
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2066126
- https://access.redhat.com/errata/RHSA-2022:0860
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2066468
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2066469
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2066470
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2066471
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2066472
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2066473
- https://access.redhat.com/errata/RHSA-2022:0870
- https://access.redhat.com/errata/RHSA-2022:0871
- https://access.redhat.com/errata/RHSA-2022:0866
- https://www.cve.org/CVERecord?id=CVE-2022-0811 https://nvd.nist.gov/vuln/detail/CVE-2022-0811 https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7
Parent vulnerabilities
(Appears in the following advisories)
Frequently Asked Questions
What is CVE-2022-0811?
CVE-2022-0811 is a vulnerability in CRI-O that allows a container escape and arbitrary code execution as root on a Kubernetes cluster.
What is the severity of CVE-2022-0811?
CVE-2022-0811 has a severity rating of 8.8 (Critical).
Which software is affected by CVE-2022-0811?
The affected software includes CRI-O versions up to 1.24.0, 1.23.2, 1.22.3, 1.21.6, and 1.20.7.
How can I fix CVE-2022-0811?
To fix CVE-2022-0811, update your CRI-O installation to version 1.24.0, 1.23.2, 1.22.3, 1.21.6, or 1.20.7.
Where can I find more information about CVE-2022-0811?
You can find more information about CVE-2022-0811 in the Red Hat Bugzilla and Red Hat Security Advisories.
- collector/redhat-cve
- collector/nvd-index
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- agent/remedy
- agent/author
- agent/references
- agent/severity
- agent/weakness
- agent/description
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2022-0811
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/tags
- agent/trending
- package-manager/redhat
- vendor/kubernetes
- canonical/kubernetes cri-o
- version/kubernetes cri-o/1.19.0
- version/kubernetes cri-o/1.20.0
- version/kubernetes cri-o/1.21.0
- version/kubernetes cri-o/1.22.0
- version/kubernetes cri-o/1.23.0