Information Disclosure in github.com/kyverno/kyverno (CVE-2023-47630)
Summary
Vulnerability in github.com/kyverno/kyverno (CVE-2023-47630). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.11.0 or later.
Original description
The description as published by the source.
Kyverno is a policy engine designed for Kubernetes. An issue was found in Kyverno that allowed an attacker to control the digest of images used by Kyverno users. The issue would require the attacker to compromise the registry that the Kyverno users fetch their images from. The attacker could then return an vulnerable image to the the user and leverage that to further escalate their position. As such, the attacker would need to know which images the Kyverno user consumes and know of one of multiple exploitable vulnerabilities in previous digests of the images. Alternatively, if the attacker has compromised the registry, they could craft a malicious image with a different digest with intentionally placed vulnerabilities and deliver the image to the user. Users pulling their images by digests and from trusted registries are not impacted by this vulnerability. There is no evidence of this being exploited in the wild. The issue has been patched in 1.10.5. All users are advised to upgrade. There are no known workarounds for this vulnerability.
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-2023-47630 has been found in github.com/kyverno/kyverno.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/kyverno/kyverno to 1.11.0 or later.
If unsure, ask your IT team or search "github.com/kyverno/kyverno CVE-2023-47630" on the vendor's site.
CVE-2023-47630 (github.com/kyverno/kyverno) — CWE-200
Attack vector: remote (network-reachable)
Patched: 1.11.0 — 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.
Information disclosure (CWE-200) exists in github.com/kyverno/kyverno.
Check the vendor advisory for the affected versions of github.com/kyverno/kyverno.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1.11.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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 patch patch
Upgrade github.com/kyverno/kyverno to 1.11.0ステージング環境で 1.11.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-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
- web github.com