Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| akuity | kargo | affected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Akuity | Kargo | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-w5wv-wvrp-v5m5 | Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.393% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:akuity:kargo:*:*:*:*:*:kubernetes:*:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Akuity
Akuity kargo |
|
| Vendors & Products |
Akuity
Akuity kargo |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Kargo manages and automates the promotion of software artifacts. Prior to versions 1.8.7, 1.7.7, and 1.6.3, a bug was found with authentication checks on the `GetConfig()` API endpoint. This allowed unauthenticated users to access this endpoint by specifying an `Authorization` header with any non-empty `Bearer` token value, regardless of validity. This vulnerability did allow for exfiltration of configuration data such as endpoints for connected Argo CD clusters. This data could allow an attacker to enumerate cluster URLs and namespaces for use in subsequent attacks. Additionally, the same bug affected the `RefreshResource` endpoint. This endpoint does not lead to any information disclosure, but could be used by an unauthenticated attacker to perform a denial-of-service style attack against the Kargo API. `RefreshResource` sets an annotation on specific Kubernetes resources to trigger reconciliations. If run on a constant loop, this could also slow down legitimate requests to the Kubernetes API server. This problem has been patched in Kargo versiosn 1.8.7, 1.7.7, and 1.6.3. There are no workarounds for this issue. | |
| Title | Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access | |
| Weaknesses | CWE-863 | |
| References |
|
|
| Metrics |
cvssV4_0
|