Vulnerability in github.com/cri-o/cri-o (CVE-2022-27652)
Summary
Vulnerability in github.com/cri-o/cri-o (CVE-2022-27652). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.24.0 or later.
Original description
The description as published by the source.
A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions. A vulnerability was found in Moby (Docker Engine) where containers started incorrectly with non-empty inheritable Linux process capabilities. This flaw allows an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs.
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-27652 has been found in github.com/cri-o/cri-o.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/cri-o/cri-o to 1.24.0 or later.
If unsure, ask your IT team or search "github.com/cri-o/cri-o CVE-2022-27652" on the vendor's site.
CVE-2022-27652 (github.com/cri-o/cri-o) — CWE-276
Attack vector: local
Patched: 1.24.0 — apply immediately
Workaround: The entrypoint of a container can be modified to use a utility like capsh(1) to drop inheritable capabilities prior to the primary process starting.
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.
A vulnerability (CWE-276) exists in github.com/cri-o/cri-o.
Check the vendor advisory for the affected versions of github.com/cri-o/cri-o.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.24.0.
Workaround: The entrypoint of a container can be modified to use a utility like capsh(1) to drop inheritable capabilities prior to the primary process starting.
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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
The entrypoint of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting.パッチが適用されるまでの応急処置として、The entrypoint of a container can be modified to use a utility like
capsh(1)to drop inheritable capabilities prior to the primary process starting. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade github.com/cri-o/cri-o to 1.24.0ステージング環境で 1.24.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- report bugzilla.redhat.com