CVE-2022-0811Public exploitNetwork attack vector

Host-root code execution via unsanitized sysctl values

Published Mar 16, 2022 · Updated Aug 2, 2024

Code injection in CRI-O allows remote authenticated users who can deploy a pod to execute arbitrary code as root on its cluster node. The getSysctlForPinns path joins sysctl entries with '+' without sanitizing values, so an injected delimiter makes pinns set kernel.core_pattern. Pod-deployment rights are required; after the host-wide core pattern points to an attacker-controlled executable, a core dump runs it as host root.

CVSS severity8.8
High
EPSS probability19.05%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Code injection in CRI-O allows remote authenticated users who can deploy a pod to execute arbitrary code as root on its cluster node. The getSysctlForPinns path joins sysctl entries with '+' without sanitizing values, so an injected delimiter makes pinns set kernel.core_pattern. Pod-deployment rights are required; after the host-wide core pattern points to an attacker-controlled executable, a core dump runs it as host root.

The record

CVE
CVE-2022-0811
Published
Mar 16, 2022
Updated
Aug 2, 2024
Vendor
CRI-O
Product
CRI-O
Classifications
CWE-94, T1611
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 16, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=cri-o 1.24.0, cri-o 1.23.2, cri-o 1.22.3, cri-o 1.21.6, cri-o 1.20.7, cri-o 1.19.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

CRI-O · CRI-Oversion=cri-o 1.24.0, cri-o 1.23.2, cri-o 1.22.3, cri-o 1.21.6, cri-o 1.20.7, cri-o 1.19.6

Published CVSS scores

9.0NIST NVDAV:N/AC:L/Au:S/C:C/I:C/A:C
8.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-94Improper Control of Generation of Code ('Code Injection')
T1611Escape to Host

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo