Kuma: Default kuma-cp leaks admin token cross-origin via CORS wildcard + LocalhostIsAdmin
kumahq kuma
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kumahq/kuma Go |
|
|
kumahq kuma
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kumahq/kuma Go |
|
|
2.11.132.12.102.13.5| github.com/kumahq/kuma/v2 Go |
|
|
Kuma is a modern Envoy-based service mesh that can run on every cloud across both Kubernetes and VMs. Prior to 2.7.25, 2.9.15, 2.11.13, 2.12.10, and 2.13.5, the default kuma-cp config leaks the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. CorsAllowedDomains: [".*"] reflects any Origin, and LocalhostIsAdmin: true promotes requests from 127.0.0.1 to mesh-system:admin. A cross-origin fetch() from a malicious page returns the admin JWT and signing material. This vulnerability is fixed in 2.7.25, 2.9.15, 2.11.13, 2.12.10, and 2.13.5.
From the CVE record · GitHub_M
The default kuma-cp configuration allows a malicious webpage to read the admin bootstrap token and signing keys. This can happen when an operator visits the page while the control plane is reachable from their browser; permissive cross-origin access and localhost admin privileges enable the request.
Operators running affected Kuma versions and users of the affected Go packages github.com/kumahq/kuma or github.com/kumahq/kuma/v2 should check their installations.