Kong Mesh: default control plane config leaks the admin token cross-origin via a CORS wildcard and localhost admin
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.7.25, 2.9.15, 2.11.13, 2.12.10, 2.13.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Kong Inc. Kong Mesh
fixed in 2.7.25; From 2.8.0 · fixed in 2.9.15; From 2.10.0 · fixed in 2.11.13; From 2.12.0 · fixed in 2.12.10; From 2.13.0 · fixed in 2.13.5
- github.com/kumahq/kumaGo
All versions
- github.com/kumahq/kuma/v2Go
fixed in 2.7.25; From 2.9.13 · fixed in 2.11.13; From 2.12.4 · fixed in 2.12.10; From 2.13.0 · fixed in 2.13.5
- github.com/kumahq/kumaGo
fixed in 2.7.25
- github.com/kumahq/kumaGo
From 2.9.0 · fixed in 2.9.15
- github.com/kumahq/kumaGo
From 2.11.0 · fixed in 2.11.13
- github.com/kumahq/kumaGo
From 2.12.0 · fixed in 2.12.10
- github.com/kumahq/kumaGo
From 2.13.0 · fixed in 2.13.5