Kong Mesh: kuma-dp connects to the control plane without verifying the TLS certificate when no CA is configured
Kong Inc. Kong Mesh
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kumahq/kuma/v2 Go |
|
|
Kong Inc. Kong Mesh
| 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 |
When kuma-dp is started against an HTTPS control plane and the operator did not pass a CA certificate, the data plane connects with TLS peer verification disabled, and the dataplane authentication token is sent over that unverified connection.
An on-path actor can intercept the dataplane authentication token and impersonate the control plane to the data plane, injecting a forged bootstrap configuration and taking over the proxy.
From the CVE record · Kong
When kuma-dp connects to an HTTPS control plane without an operator-provided CA certificate, it disables TLS peer verification and sends its authentication token over the unverified connection. An on-path attacker can intercept the token, impersonate the control plane, and inject a forged bootstrap configuration to take over the proxy.
Operators of Kong Mesh using affected github.com/kumahq/kuma/v2 versions before the applicable fixes, or github.com/kumahq/kuma versions through 1.8.1, should check their deployments.