Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-mg7w-c9x2-xh7r: 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?

  1. Enhancements made from the Karmada community: https://github.com/karmada-io/karmada/pull/5793
  2. Karmada Component Permissions: https://karmada.io/docs/administrator/security/component-permission
ghsa
#vulnerability#git#auth

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?

  1. Enhancements made from the Karmada community: karmada-io/karmada#5793
  2. Karmada Component Permissions: https://karmada.io/docs/administrator/security/component-permission

References

  • GHSA-mg7w-c9x2-xh7r
  • karmada-io/karmada#5793
  • karmada-io/karmada@2c82055
  • https://karmada.io/docs/administrator/security/component-permission

ghsa: Latest News

GHSA-3m86-c9x3-vwm9: Graylog vulnerable to privilege escalation through API tokens