Authentication Bypass in github.com/kyverno/kyverno (CVE-2022-47633)
Summary
Authentication bypass in github.com/kyverno/kyverno (CVE-2022-47633). Successful exploitation can lead to full system takeover. Exploitable via verifyImages. Mitigation: upgrade to 1.8.5 or later.
Original description
The description as published by the source.
An image signature validation bypass vulnerability in Kyverno 1.8.3 and 1.8.4 allows a malicious image registry (or a man-in-the-middle attacker) to inject unsigned arbitrary container images into a protected Kubernetes cluster. This is fixed in 1.8.5. This has been fixed in 1.8.5 and mitigations are available for impacted releases.
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-47633 has been found in github.com/kyverno/kyverno.
Attackers can target a specific entry point like verifyImages over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/kyverno/kyverno to 1.8.5 or later.
If unsure, ask your IT team or search "github.com/kyverno/kyverno CVE-2022-47633" on the vendor's site.
CVE-2022-47633 (github.com/kyverno/kyverno) — CWE-287
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: verifyImages
Patched: 1.8.5 — apply immediately
Workaround: Configure a Kyverno policy to restrict registries to a set of secure trusted image registries (sample).
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.
Authentication bypass (CWE-287) exists in github.com/kyverno/kyverno. Attackers reach the vulnerable code path via verifyImages without authentication.
Check the vendor advisory for the affected versions of github.com/kyverno/kyverno. Attack surface: verifyImages.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1.8.5.
Workaround: Configure a Kyverno policy to restrict registries to a set of secure trusted image registries (sample).
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/kyverno/kyverno' . 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/kyverno/kyverno' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/kyverno/kyvernoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Configure a Kyverno policy to restrict registries to a set of secure trusted image registries ([sample](https://kyverno.io/policies/best-practices/restrict_image_registries/restrict_image_registries/)).パッチが適用されるまでの応急処置として、Configure a Kyverno policy to restrict registries to a set of secure trusted image registries (sample). を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/kyverno/kyverno to 1.8.5ステージング環境で 1.8.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- patch github.com
- web github.com
- web github.com
- web kyverno.io
- web kyverno.io
- web pkg.go.dev
- web web.archive.org
- web kyverno.io