Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2022-0811

Code Injection in github.com/cri-o/cri-o (CVE-2022-0811)

Summary

Code injection in github.com/cri-o/cri-o (CVE-2022-0811). Successful exploitation can lead to full system takeover. Exploitable via kernel.core_pattern. Mitigation: upgrade to 1.23.2 or later.

Original description

The description as published by the source.

Impact

A flaw introduced in CRI-O version 1.19 which an attacker can use to bypass the safeguards and set arbitrary kernel parameters on the host. As a result, anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime can abuse the kernel.core_pattern kernel parameter to achieve container escape and arbitrary code execution as root on any node in the cluster.

Patches

The patches will be present in 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2, 1.24.0

Workarounds

  • Users can set manage_ns_lifecycle to false, which causes the sysctls to be configured by the OCI runtime, which typically filter these cases. This option is available in 1.20 and 1.19. Newer versions don't have this option.
  • An admission webhook could be created to deny pods that specify a + in the sysctl value of a pod.
  • A PodSecurityPolicy [deprecated] could be created, specifying all sysctls as forbidden like so:
apiVersion: policy/v1beta1
kind: PodSecurityPolicy
metadata:
  name: sysctl-psp
spec:
  forbiddenSysctls:
    - "*"

However, this option will not work if any sysctls are required by any pods in the cluster.

Credits

Credit for finding this vulnerability goes to John Walker and Manoj Ahuje of Crowdstrike. The CRI-O community deeply thanks them for the report.

For more information

If you have any questions or comments about this advisory:

  • Open an issue in [t…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-0811 has been found in github.com/cri-o/cri-o.
Attackers can target a specific entry point like kernel.core_pattern over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/cri-o/cri-o to 1.23.2 or later.
If unsure, ask your IT team or search "github.com/cri-o/cri-o CVE-2022-0811" on the vendor's site.

CVE-2022-0811 (github.com/cri-o/cri-o) — CWE-94
Attack vector: remote (network-reachable) / no user interaction
Attack surface: kernel.core_pattern
Patched: 1.23.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Arbitrary code execution (CWE-94) exists in github.com/cri-o/cri-o. Attackers reach the vulnerable code path via kernel.core_pattern.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/cri-o/cri-o. Attack surface: kernel.core_pattern.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.23.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/cri-o/cri-o' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/cri-o/cri-o' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/cri-o/cri-o を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/cri-o/cri-o to 1.23.2

    ステージング環境で 1.23.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/cri-o/cri-o
[{"type":"SEMVER","events":[{"introduced":"1.23.0"},{"fixed":"1.23.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details