Kong Mesh: kumactl 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 an operator adds an HTTPS control plane profile to kumactl without providing a CA certificate, kumactl disables TLS verification and sends API tokens over the unverified connection.
An attacker on the network path between the operator and the control plane can intercept user or admin API tokens and then act against the control plane as that user.
From the CVE record · Kong
When an operator adds an HTTPS control plane profile to kumactl without a CA certificate, kumactl disables TLS verification and sends API tokens over the unverified connection. An attacker on the network path can intercept user or admin tokens and act against the control plane as that user.
Operators using Kong Mesh should check github.com/kumahq/kuma/v2 versions below 2.7.26, 2.8.0–2.9.15, 2.10.0–2.11.13, 2.12.0–2.12.10, or 2.13.0–2.13.6, and github.com/kumahq/kuma versions through 1.8.1.