CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HKnown as cr8escape
High (8.8) in kubernetes cri-o. EPSS 19% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/cri-o/cri-o 1.19.6, 1.20.7, 1.21.6.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hgithub.com/cri-o/cri-o (Go): fixed in 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2Explain CVE-2022-0811 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-0811?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-0811?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-0811 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| kubernetes:cri-o | from 1.19.0 before 1.19.6 |
| kubernetes:cri-o | from 1.20.0 before 1.20.7 |
| kubernetes:cri-o | from 1.21.0 before 1.21.6 |
| kubernetes:cri-o | from 1.22.0 before 1.22.3 |
| kubernetes:cri-o | from 1.23.0 before 1.23.2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-6x2m-w449-qwx7 | Go | github.com/cri-o/cri-o | >=1.19.0 <1.19.6 | 1.19.6 |
| GHSA-6x2m-w449-qwx7 | Go | github.com/cri-o/cri-o | >=1.20.0 <1.20.7 | 1.20.7 |
| GHSA-6x2m-w449-qwx7 | Go | github.com/cri-o/cri-o | >=1.21.0 <1.21.6 | 1.21.6 |
| GHSA-6x2m-w449-qwx7 | Go | github.com/cri-o/cri-o | >=1.22.0 <1.22.3 | 1.22.3 |
| GHSA-6x2m-w449-qwx7 | Go | github.com/cri-o/cri-o | >=1.23.0 <1.23.2 | 1.23.2 |
| GO-2022-0354 | Go | github.com/cri-o/cri-o | >=1.19.0 <1.19.6 >=1.20.0 <1.20.7 >=1.21.0 <1.21.6 >=1.22.0 <1.22.3 >=1.23.0 <1.23.2 | 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Red Hat | openshift:4.6::el7 | cri-o, cri-o-debuginfo | 0:1.19.5-3.rhaos4.6.git91f8458.el7 | RHSA-2022:0866 |
| Red Hat | openshift:4.6::el8 | cri-o, cri-o-debuginfo, cri-o-debugsource | 0:1.19.5-3.rhaos4.6.git91f8458.el8 | RHSA-2022:0866 |
| Red Hat | openshift:4.7::el7 | cri-o, cri-o-debuginfo | 0:1.20.6-11.rhaos4.7.git76ea3d0.el7 | RHSA-2022:0870 |
| Red Hat | openshift:4.7::el8 | cri-o, cri-o-debuginfo, cri-o-debugsource | 0:1.20.6-11.rhaos4.7.git76ea3d0.el8 | RHSA-2022:0870 |
| Red Hat | openshift:4.8::el7 | cri-o, cri-o-debuginfo | 0:1.21.5-3.rhaos4.8.gitaf64931.el7 | RHSA-2022:0871 |
| Red Hat | openshift:4.8::el8 | cri-o, cri-o-debuginfo, cri-o-debugsource | 0:1.21.5-3.rhaos4.8.gitaf64931.el8 | RHSA-2022:0871 |
| Red Hat | openshift:4.8::el8 | jenkins-2-plugins | 0:4.8.1646993358-1.el8 | RHSA-2022:0871 |
| Red Hat | openshift:4.9::el7 | cri-o, cri-o-debuginfo | 0:1.22.2-3.rhaos4.9.gitb030be8.el7 | RHSA-2022:0860 |
| Red Hat | openshift:4.9::el8 | cri-o, cri-o-debuginfo, cri-o-debugsource | 0:1.22.2-3.rhaos4.9.gitb030be8.el8 | RHSA-2022:0860 |
| Red Hat | openshift:4.10::el7 | cri-o, cri-o-debuginfo | 0:1.23.1-12.rhaos4.10.git1607c6e.el7 | RHSA-2022:0810 |
| Red Hat | openshift:4.10::el8 | cri-o, cri-o-debuginfo, cri-o-debugsource | 0:1.23.1-12.rhaos4.10.git1607c6e.el8 | RHSA-2022:0810 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | cri-o | 1.23.2-r0 | ALPINE-CVE-2022-0811 |
| Azure Linux | 2 | cri-o | 1.22.3-1 | AZL-37070 |
From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat · Alpine.
Red Hat rates this Important.
OpenShift Container Platform (OCP) starting from version 4.6 is affected by this vulnerability, older versions of OCP are not affected.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.10 | cri-o-0:1.23.1-12.rhaos4.10.git1607c6e.el7 | Fixed 2022-03-15 | RHSA-2022:0810 |
| Red Hat OpenShift Container Platform 4.6 | cri-o-0:1.19.5-3.rhaos4.6.git91f8458.el7 | Fixed 2022-03-23 | RHSA-2022:0866 |
| Red Hat OpenShift Container Platform 4.7 | cri-o-0:1.20.6-11.rhaos4.7.git76ea3d0.el7 | Fixed 2022-03-22 | RHSA-2022:0870 |
| Red Hat OpenShift Container Platform 4.8 | cri-o-0:1.21.5-3.rhaos4.8.gitaf64931.el7 | Fixed 2022-03-22 | RHSA-2022:0871 |
| Red Hat OpenShift Container Platform 4.9 | cri-o-0:1.22.2-3.rhaos4.9.gitb030be8.el7 | Fixed 2022-03-21 | RHSA-2022:0860 |
| Red Hat OpenShift Container Platform 3.11 | cri-o | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-0811.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.