Kuma: kumactl connects to control plane without verifying TLS certificate when no CA is configured
kumahq kuma
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kumahq/kuma/v2 Go |
|
|
kumahq kuma
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kumahq/kuma/v2 Go |
|
|
2.9.162.11.142.12.112.13.7| github.com/kumahq/kuma Go |
| No fix yet |
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.
From the CVE record · GitHub_M
A manually configured kumactl profile using an HTTPS control plane without --ca-cert-file disables TLS peer verification and sends API tokens over an unverified connection. An attacker on the network path can intercept user or administrator tokens and act against the control plane as that user; the default local HTTP profile is unaffected.
Engineers running affected versions of Go packages github.com/kumahq/kuma/v2 or github.com/kumahq/kuma should check manually configured kumactl HTTPS profiles.