Description

Kargo manages and automates the promotion of software artifacts. From v1.9.0 to v1.9.2, Kargo's authorization model includes a promote verb -- a non-standard Kubernetes "dolphin verb" -- that gates the ability to advance Freight through a promotion pipeline. This verb exists to separate the ability to manage promotion-related resources from the ability to trigger promotions, enabling fine-grained access control over what is often a sensitive operation. The promote verb is correctly enforced in Kargo's legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (patch on freights/status or create on promotions). This permits users who hold those standard permissions -- but who were deliberately not granted promote -- to bypass the intended authorization boundary. The affected endpoints are /v1beta1/projects/{project}/freight/{freight}/approve, /v1beta1/projects/{project}/stages/{stage}/promotions, and /v1beta1/projects/{project}/stages/{stage}/promotions/downstream. This vulnerability is fixed in v1.9.3.

Weaknesses 1

Affected Products 1

References 2

• github.com https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49
  Patch
• github.com https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4
  Vendor Advisory

Remediation

• github.com https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49
  Patch