Description
On a Kong Mesh global control plane, resources received over the zone-to-global KDS sync are attributed using the in-band, sender-controlled ControlPlane.Identifier rather than the authenticated zone identity derived from the connection. Authenticated zones can have the global control plane store and re-distribute those resources as belonging to another zone. The result is a cross-zone isolation bypass: the holder of a single enrolled zone's credential can inject, attribute, and overwrite resources in another zone's namespace mesh-wide. The root cause lives in Kuma's open-source KDS sync code, which Kong Mesh's control plane is built on.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Kong Inc. Kong Mesh
Default version status: unaffected
0 to < 2.7.29affected2.8.0 to < 2.9.19affected2.10.0 to < 2.11.18affected2.12.0 to < 2.12.14affected2.13.0 to < 2.13.10affected2.14.0 to < 2.14.2affected
References
- https://github.com/kumahq/kuma/security/advisories/GHSA-m58j-fjmc-h3g4 ↗
- https://github.com/kumahq/kuma/pull/17456 ↗
- https://github.com/kumahq/kuma/pull/17458 ↗
- https://github.com/kumahq/kuma/pull/17461 ↗
- https://github.com/kumahq/kuma/pull/17463 ↗
- https://github.com/kumahq/kuma/pull/17462 ↗
- https://github.com/kumahq/kuma/pull/17460 ↗
- https://github.com/kumahq/kuma/pull/17459 ↗
- https://developer.konghq.com/mesh/changelog/ ↗