Kong Mesh: default control plane config leaks the admin token cross-origin via a CORS wildcard and localhost admin
Kong Inc. Kong Mesh
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kumahq/kuma Go |
|
|
Kong Inc. Kong Mesh
| Product | Affected | Fixed in |
|---|---|---|
| github.com/kumahq/kuma Go |
|
|
2.11.132.12.102.13.5| github.com/kumahq/kuma/v2 Go |
|
|
The default kuma-cp configuration in Kong Mesh reveals the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. Due to a CORS misconfiguration a cross-origin fetch() from a malicious page returns the admin JWT and signing material.
From the CVE record · Kong
The default kuma-cp configuration has a CORS misconfiguration that exposes the admin bootstrap token and signing keys. A malicious webpage visited by an operator can retrieve the admin JWT and signing material if the control plane is reachable from the operator’s browser.
Operators of Kong Mesh using affected versions of the Go packages github.com/kumahq/kuma or github.com/kumahq/kuma/v2 should check their deployments.