kuma-dp 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, Universal mode kuma-dp connections to an HTTPS control plane disable TLS peer verification when --ca-cert-file is not supplied and KUMA_CONTROL_PLANE_CA_CERT is unset. The dataplane authentication token is sent over the unverified connection, allowing an on-path attacker to intercept the token, impersonate the control plane, inject a forged bootstrap configuration, and take over the proxy. Standard Kubernetes installations created by kumactl install control-plane or the official Helm chart are unaffected because the mutating admission webhook injects KUMA_CONTROL_PLANE_CA_CERT into each sidecar. 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
In Universal mode, kuma-dp disables TLS peer verification for HTTPS control-plane connections when neither --ca-cert-file nor KUMA_CONTROL_PLANE_CA_CERT is set. An on-path attacker can intercept the dataplane authentication token, impersonate the control plane, inject a forged bootstrap configuration, and take over the proxy. Standard Kubernetes installations created by kumactl install control-plane or the official Helm chart are unaffected because they inject the CA certificate setting.
Operators of affected github.com/kumahq/kuma/v2 releases before the applicable fixed version (2.7.26, 2.9.16, 2.11.14, 2.12.11, or 2.13.7), and users of github.com/kumahq/kuma through 1.8.1, should check their deployments.