Kuma: kumactl connects to control plane without verifying TLS certificate when no CA is configured
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| kumahq | kuma | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Kumahq | Kuma |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-v95x-xhq5-4929 | kumactl connects to control plane without verifying TLS certificate when no CA is configured |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.275% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Kumahq
Kumahq kuma |
|
| Vendors & Products |
Kumahq
Kumahq kuma |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Kuma is a modern Envoy-based service mesh that can run on every cloud across both Kubernetes and VMs. Prior to 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7, a kumactl profile manually configured for an HTTPS control plane without --ca-cert-file disables TLS peer verification and sends API tokens over the unverified connection. An attacker on the network path can intercept user or administrator API tokens and act against the control plane as the compromised user. The default local profile is unaffected because it uses plain HTTP. This issue is fixed in versions 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7. | |
| Title | Kuma: kumactl connects to control plane without verifying TLS certificate when no CA is configured | |
| Weaknesses | CWE-295 | |
| References |
|
|
| Metrics |
cvssV4_0
|