Loading vulnerability…
CVE-2022-0811, also known as cr8escape, is a code-injection flaw in CRI-O's handling of pod sysctl settings. A user authorized to deploy a pod can supply a crafted sysctl value that causes CRI-O to set arbitrary kernel parameters on the node rather than enforcing the intended restrictions. An attacker can set kernel.core_pattern and use the resulting kernel helper execution behavior to escape the container and execute attacker-controlled code with root privileges on the Kubernetes node hosting the pod.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A CRI-O container-escape vulnerability allowing arbitrary sysctl settings that can lead to root-level arbitrary code execution on the host.
Security vulnerability addressed in the Red Hat Advanced Cluster Management for Kubernetes 2.4.3 erratum; no technical detail is provided.
A CRI-O/pinns vulnerability that allows arbitrary kernel parameter injection via pod sysctl settings, enabling code execution through abuse of kernel.core_pattern.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.