Kong Mesh: default control plane config leaks the admin token cross-origin via a CORS wildcard and localhost admin
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.1epss 0.2%
exploitation probability
0.2%top 86% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Affected products
Kong Inc. · Kong MeshReferences
https://developer.konghq.com/mesh/changelog/https://github.com/kumahq/kuma/pull/16416https://github.com/kumahq/kuma/pull/16423https://github.com/kumahq/kuma/pull/16424https://github.com/kumahq/kuma/pull/16425https://github.com/kumahq/kuma/pull/16426https://github.com/kumahq/kuma/pull/16427https://github.com/kumahq/kuma/security/advisories/GHSA-3vcp-chfh-f6r2