| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/akuity/kargo | ≥ 1.7.0, < 1.7.8≥ 1.8.0-rc.1, < 1.8.11≥ 1.9.0-rc.1, < 1.9.3 | 1.7.81.8.111.9.3 |
| kargo | ≥ 1.7.0, < 1.7.8≥ 1.8.0, < 1.8.11≥ 1.9.0, < 1.9.3 | 1.7.81.8.111.9.3 |
The batch resource creation endpoints of both Kargo's legacy gRPC API and newer REST API accept multi-document YAML payloads. When either endpoint creates a Project resource, creation of subsequent resources from that same payload belonging in that Project's underlying Kubernetes namespace, by design, proceeds using the API server's own permissions. The creator of a new Project automatically becomes its administrator, but those permissions are granted asynchronously by the management controller. The design choice to create the affected resources using the API server's own permissions averts a race and is contextually appropriate.
Specially crafted payloads can manifest a bug present in the logic of both endpoints to inject arbitrary resources (of specific types only) into the underlying namespace of an existing Project using the API server's own permissions when that behavior was not intended. Critically, an attacker may exploit this as a vector for elevating their own permissions, which can then be leveraged to achieve remote code execution or secret exfiltration. Exfiltrated artifact repository credentials can be leveraged, in turn, to execute further attacks.
In some configurations of the Kargo control plane's underlying Kubernetes cluster, elevated permissions may additionally be leveraged to achieve remote code execution or secret exfiltration using kubectl. This can reduce the complexity of the attack, however, worst case scenarios remain entirely achievable even without this.
The following sections provide the rationale for the values selected for each of CVSS v4's base metrics.
The affected endpoints are served by the Kargo API server over HTTP/HTTPS. No local or physical access is required.
Exploitation requires only a specially crafted YAML payload sent to an affected API endpoint.
No specific environmental conditions are required beyond those that are typical for any Kargo instance.
The attack relies only on the ability to authenticate to the Kargo API server along with basic permissions that are typically granted to all Kargo users.
The attack is fully automated via API calls. No other user needs to take any action.
Elevated permissions enable secret exfiltration from any Kargo Project.
Elevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the integrity of the vulnerable system, including Kargo Projects, Kargo control plane components, and the Kargo control plane's underlying Kubernetes cluster.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site freeNote: Because it is an integral component of Kargo's control plane, the underlying Kubernetes cluster has been counted as a component of the vulnerable system instead of a subsequent system.
Elevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the availability of the vulnerable system, including Kargo control plane components and the Kargo control plane's underlying Kubernetes cluster.
Secrets exfiltrated from Project namespaces typically contain credentials for external systems. These may enable exfiltration of further confidential information from those systems.
Elevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the integrity of subsequent systems.
Elevated permissions enable tampering, up to and including remote code execution, as well as secret exfiltration from any Kargo Project. Project secrets often include credentials having write permissions to GitOps repositories. Such secrets may enable pushing configurations that impact the availability of subsequent systems.
Exploitation requires authentication to the Kargo API server. Anonymous access is not sufficient.
The most severe consequences of this vulnerability depend on a privilege escalation path (via RoleBinding injection) that was not identified by the original reporter, suggesting it is not immediately obvious from the bug alone.
There is no evidence of exploitation in the wild.