dbcve.org
KyvernoApplication

CVE-2023-47630

HIGH · 7.1 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 1.10.5 or later.
See remediation →
75/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Kyverno, a Kubernetes policy engine, has a vulnerability where an attacker who compromises a container registry can manipulate the image digest returned to Kyverno users, potentially delivering vulnerable or malicious images instead of the intended ones. The attacker needs to know which images users consume and have registry access. Users pulling images by digest from trusted registries are not affected.

MitigationUpgrade Kyverno to version 1.10.5. Additionally, pull images by digest rather than by tag and use trusted registries to prevent image manipulation attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
KyvernoApplication
Affected:< 1.10.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Kyverno version
    Run 'kubectl get deployment -n kyverno -o jsonpath='{.items[*].spec.template.spec.containers[*].image}'' to find the Kyverno image, then check the image tag against the version pattern (e.g., v1.10.4, v1.10.3)
    Affected if The installed Kyverno version is lower than 1.10.5 (e.g., v1.10.4, v1.10.3, v1.10.0)
  2. Locate image references in Kyverno policies
    Review Kyverno ClusterPolicy or Policy resources in the cluster using 'kubectl get ClusterPolicy,Policy -A -o yaml' and inspect any image fields (e.g., image, imagePullPolicy, registry)
    Affected if Policies reference container images using tags (like :latest, :v1.0.0) rather than digests (like @sha256:...)
  3. Check Kyverno image verification rules
    Examine any ClusterPolicy or Policy resources containing imageVerify, imageProfiles, or similar image validation rules using 'kubectl get ClusterPolicy,Policy -A -o jsonpath='{.items[*].spec.rules[*]}''
    Affected if No image digest verification rules are configured (vulnerability requires tag-based image references)
  4. Assess image pull behavior in workloads
    Run 'kubectl get pods -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"\t"}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\n"}{end}'' to see how images are referenced across cluster workloads
    Affected if Workloads pull images by tag (e.g., nginx:latest) rather than by immutable digest

A user is affected if their Kyverno version is below 1.10.5 AND they or their policies reference container images using tags instead of digests from potentially untrusted registries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.10.5 or later
Fixed in 1.10.5
Interim mitigation

Upgrade Kyverno to version 1.10.5. Additionally, pull images by digest rather than by tag and use trusted registries to prevent image manipulation attacks.

Recommended fix High confidence

Kyverno 1.10.5

  1. Upgrade Kyverno to version 1.10.5 or later
  2. Verify the upgrade was successful by checking the Kyverno version
  3. Ensure image pull policies are reviewed to use trusted registries
Caveat Review release notes for 1.10.x for any breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kyverno Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47630 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47630 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data