Описание
Karmada PULL Mode Cluster Privilege Escalation
Impact
What kind of vulnerability is it? Who is impacted?
The PULL mode clusters registered with the karmadactl register command have excessive privileges to access control plane resources. By abusing these permissions, an attacker able to authenticate as the karmada-agent to a karmada cluster would be able to obtain administrative privileges over the entire federation system including all registered member clusters.
Patches
Has the problem been patched? What versions should users upgrade to?
Since Karmada v1.12.0, command karmadactl register restricts the access permissions of pull mode member clusters to control plane resources. This way, an attacker able to authenticate as the karmada-agent cannot control other member clusters in Karmada.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Restricts the access permissions of pull mode member clusters to control plane resources according to Karmada Component Permissions Docs.
References
Are there any links users can visit to find out more?
- Enhancements made from the Karmada community: https://github.com/karmada-io/karmada/pull/5793
- Karmada Component Permissions: https://karmada.io/docs/administrator/security/component-permission
Ссылки
- https://github.com/karmada-io/karmada/security/advisories/GHSA-mg7w-c9x2-xh7r
- https://nvd.nist.gov/vuln/detail/CVE-2024-56513
- https://github.com/karmada-io/karmada/pull/5793
- https://github.com/karmada-io/karmada/commit/2c82055c4c7f469411b1ba48c4dba4841df04831
- https://karmada.io/docs/administrator/security/component-permission
Пакеты
github.com/karmada-io/karmada
< 1.12.0
1.12.0
Связанные уязвимости
Karmada is a Kubernetes management system that allows users to run cloud-native applications across multiple Kubernetes clusters and clouds. Prior to version 1.12.0, the PULL mode clusters registered with the `karmadactl register` command have excessive privileges to access control plane resources. By abusing these permissions, an attacker able to authenticate as the karmada-agent to a karmada cluster would be able to obtain administrative privileges over the entire federation system including all registered member clusters. Since Karmada v1.12.0, command `karmadactl register` restricts the access permissions of pull mode member clusters to control plane resources. This way, an attacker able to authenticate as the karmada-agent cannot control other member clusters in Karmada. As a workaround, one may restrict the access permissions of pull mode member clusters to control plane resources according to Karmada Component Permissions Docs.
Уязвимость системы управления кластерами Kubernetes для запуска облачных приложения на нескольких кластерах Karmada, связанная с некорректным присваиванием привилегий, позволяющая нарушителю повысить свои привилегии
