CVE-2022-0811 Code Injection in CRI-O
Attackers with pod deployment rights can escape containers and execute arbitrary code as root on cluster nodes via CRI-O kernel option flaws.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-0811?
CVE-2022-0811 is a high-severity code injection vulnerability in CRI-O, published on 16 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-94
Which versions are affected by CVE-2022-0811?
11 open source packages ship an affected version, including github.com/cri-o/cri-o. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/cri-o/cri-o Go | From 1.19.0 | 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2 |
github.com/cri-o/cri-o Go | From 1.19.0 | 1.19.6 |
github.com/cri-o/cri-o Go | From 1.19.0 | 1.19.6 |
github.com/cri-o/cri-o Go | From 1.20.0 | 1.20.7 |
github.com/cri-o/cri-o Go | From 1.20.0 | 1.20.7 |
github.com/cri-o/cri-o Go | From 1.21.0 | 1.21.6 |
5 more packages
github.com/cri-o/cri-o Go | From 1.21.0 | 1.21.6 |
github.com/cri-o/cri-o Go | From 1.22.0 | 1.22.3 |
github.com/cri-o/cri-o Go | From 1.22.0 | 1.22.3 |
github.com/cri-o/cri-o Go | From 1.23.0 | 1.23.2 |
github.com/cri-o/cri-o Go | From 1.23.0 | 1.23.2 |
Linux distribution packages (10)
cri-o Red Hat:openshift:4.10::el7 | All versions | 0:1.23.1-12.rhaos4.10.git1607c6e.el7 |
cri-o-debuginfo Red Hat:openshift:4.10::el7 | All versions | 0:1.23.1-12.rhaos4.10.git1607c6e.el7 |
cri-o Red Hat:openshift:4.10::el8 | All versions | 0:1.23.1-12.rhaos4.10.git1607c6e.el8 |
cri-o-debuginfo Red Hat:openshift:4.10::el8 | All versions | 0:1.23.1-12.rhaos4.10.git1607c6e.el8 |
cri-o-debugsource Red Hat:openshift:4.10::el8 | All versions | 0:1.23.1-12.rhaos4.10.git1607c6e.el8 |
cri-o Red Hat:openshift:4.9::el7 | All versions | 0:1.22.2-3.rhaos4.9.gitb030be8.el7 |
cri-o-debuginfo Red Hat:openshift:4.9::el7 | All versions | 0:1.22.2-3.rhaos4.9.gitb030be8.el7 |
cri-o Red Hat:openshift:4.9::el8 | All versions | 0:1.22.2-3.rhaos4.9.gitb030be8.el8 |
cri-o-debuginfo Red Hat:openshift:4.9::el8 | All versions | 0:1.22.2-3.rhaos4.9.gitb030be8.el8 |
cri-o-debugsource Red Hat:openshift:4.9::el8 | All versions | 0:1.22.2-3.rhaos4.9.gitb030be8.el8 |
Products include Kubernetes Cri-O.
How do I fix CVE-2022-0811?
Upgrade github.com/cri-o/cri-o to a fixed version for your release line: 1.19.6, 1.20.7, 1.21.6 or 1.22.3.
Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.
Is CVE-2022-0811 being exploited?
There is no known exploitation of CVE-2022-0811 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in CRI-O
- CVE-2018-1000400 Privilege escalation in n/a
- CVE-2024-5154 Cri-o: malicious container can create symlink on host
- CVE-2022-2995 CRI-O incorrect handling of supplementary groups may lead to sensitive information disclosure
- CVE-2022-3466 Cri-o: security regression of cve-2022-27652
- CVE-2022-0532 Incorrect Permission Assignment for Critical Resource in CRI-O
Sources
Also known as AZL-37070, GHSA-6x2m-w449-qwx7, GO-2022-0354, RHSA-2022:0810, RHSA-2022:0860.