Authorization Bypass Through User-Controlled Key Affecting kots package, versions <1.124.3-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

Exploit Maturity
Not Defined
EPSS
0.04% (12th percentile)

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 Authorization Bypass Through User-Controlled Key vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-KOTS-8719763
  • published12 Feb 2025
  • disclosed11 Feb 2025

Introduced: 11 Feb 2025

NewCVE-2025-24976  (opens in a new tab)
CWE-639  (opens in a new tab)

How to fix?

Upgrade Chainguard kots to version 1.124.3-r1 or higher.

NVD Description

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

Distribution is a toolkit to pack, ship, store, and deliver container content. Systems running registry versions 3.0.0-beta.1 through 3.0.0-rc.2 with token authentication enabled may be vulnerable to an issue in which token authentication allows an attacker to inject an untrusted signing key in a JSON web token (JWT). The issue lies in how the JSON web key (JWK) verification is performed. When a JWT contains a JWK header without a certificate chain, the code only checks if the KeyID (kid) matches one of the trusted keys, but doesn't verify that the actual key material matches. A fix for the issue is available at commit 5ea9aa028db65ca5665f6af2c20ecf9dc34e5fcd and expected to be a part of version 3.0.0-rc.3. There is no way to work around this issue without patching if the system requires token authentication.

CVSS Scores

version 3.1