Vulnerability in github.com/kyverno/kyverno (CVE-2023-34091)
Summary
Vulnerability in github.com/kyverno/kyverno (CVE-2023-34091). Data can be tampered with by attackers. Exploitable via deletionTimestamp. Mitigation: upgrade to 1.10.0 or later.
Original description
The description as published by the source.
Impact
In versions of Kyverno prior to 1.10.0, resources which have the deletionTimestamp field defined can bypass validate, generate, or mutate-existing policies, even in cases where the validationFailureAction field is set to Enforce.
This situation occurs as resources pending deletion were being consciously exempted by Kyverno, as a way to reduce processing load as policies are typically not applied to objects which are being deleted.
However, this could potentially result in allowing a malicious user to leverage the Kubernetes finalizers feature by setting a finalizer which causes the Kubernetes API server to set the deletionTimestamp and then not completing the delete operation as a way to explicitly to bypass a Kyverno policy.
Note that this is not applicable to Kubernetes Pods but, as an example, a Kubernetes Service resource can be manipulated using an indefinite finalizer to bypass policies.
Patches
This is resolved in Kyverno 1.10.0.
Workarounds
There is no known workaround.
References
Are there any links users can visit to find out more?
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-34091 has been found in github.com/kyverno/kyverno.
Attackers can target a specific entry point like deletionTimestamp over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade github.com/kyverno/kyverno to 1.10.0 or later.
If unsure, ask your IT team or search "github.com/kyverno/kyverno CVE-2023-34091" on the vendor's site.
CVE-2023-34091 (github.com/kyverno/kyverno) — CWE-285
Attack vector: remote (network-reachable) / no user interaction
Attack surface: deletionTimestamp / validationFailureAction / Enforce
Patched: 1.10.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.
A vulnerability (CWE-285) exists in github.com/kyverno/kyverno. Attackers reach the vulnerable code path via deletionTimestamp.
Check the vendor advisory for the affected versions of github.com/kyverno/kyverno. Attack surface: deletionTimestamp / validationFailureAction / Enforce.
Severity: ?. Data can be tampered with by attackers.
Update to 1.10.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.10.0ステージング環境で 1.10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com