Kong Mesh: kumactl connects to the control plane without verifying the TLS certificate when no CA is configured
- 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.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7
- 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
When an operator adds an HTTPS control plane profile to kumactl without providing a CA certificate, kumactl disables TLS verification and sends API tokens over the unverified connection. An attacker on the network path between the operator and the control plane can intercept user or admin API tokens and then act against the control plane as that user.
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.26; From 2.8.0 · fixed in 2.9.16; From 2.10.0 · fixed in 2.11.14; From 2.12.0 · fixed in 2.12.11; From 2.13.0 · fixed in 2.13.7
- github.com/kumahq/kumaGo
All versions
- github.com/kumahq/kuma/v2Go
fixed in 2.7.26; From 2.9.13 · fixed in 2.11.14; From 2.12.4 · fixed in 2.12.11; From 2.13.0 · fixed in 2.13.7
- github.com/kumahq/kuma/v2Go
fixed in 2.7.26
- github.com/kumahq/kuma/v2Go
From 2.8.0 · fixed in 2.9.16
- github.com/kumahq/kuma/v2Go
From 2.10.0 · fixed in 2.11.14
- github.com/kumahq/kuma/v2Go
From 2.12.0 · fixed in 2.12.11
- github.com/kumahq/kuma/v2Go
From 2.13.0 · fixed in 2.13.7
- github.com/kumahq/kumaGo
through 1.8.1