Improper Input Validation Affecting kyverno-notation-aws package, versions <1.1-r20


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Input Validation vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-KYVERNONOTATIONAWS-10881438
  • published23 Jul 2025
  • disclosed23 Jul 2025

Introduced: 23 Jul 2025

NewCVE-2025-47281  (opens in a new tab)
CWE-20  (opens in a new tab)
CWE-248  (opens in a new tab)

How to fix?

Upgrade Chainguard kyverno-notation-aws to version 1.1-r20 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kyverno-notation-aws package and not the kyverno-notation-aws package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Kyverno is a policy engine designed for cloud native platform engineering teams. In versions 1.14.1 and below, a Denial of Service (DoS) vulnerability exists due to improper handling of JMESPath variable substitutions. Attackers with permissions to create or update Kyverno policies can craft expressions using the {{@}} variable combined with a pipe and an invalid JMESPath function (e.g., {{@ | non_existent_function }}). This leads to a nil value being substituted into the policy structure. Subsequent processing by internal functions, specifically getValueAsStringMap, which expect string values, results in a panic due to a type assertion failure (interface {} is nil, not string). This crashes Kyverno worker threads in the admission controller and causes continuous crashes of the reports controller pod. This is fixed in version 1.14.2.