CyberRota Analysis
AI-GeneratedKubernetes deployments using Kuma versions prior to 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7 are vulnerable when a kumactl profile is manually configured for an HTTPS control plane without the --ca-cert-file option, leading to disabled TLS peer verification. This flaw allows an attacker on the network to intercept API tokens, potentially compromising the control plane by impersonating legitimate users. Organizations utilizing Kuma in their Kubernetes environments should prioritize upgrading to the patched versions to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD 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.