Описание
A flaw was found in insights-client. The component's ServiceAccount is bound to a ClusterRole granting cluster-wide secrets get, list, and watch permissions, while the code only requires access to a single specific Secret. This excessive privilege means that a compromise of the insights-client pod or ServiceAccount token would grant an attacker read access to all Secrets across the hub cluster, including managed-cluster kubeconfigs and other sensitive credentials.
Отчет
This is a Moderate flaw in Red Hat Advanced Cluster Management for Kubernetes. The insights-client component is granted cluster-wide secrets read access through its ClusterRole, but only requires access to a single Secret (openshift-config/pull-secret). This over-broad RBAC creates a privilege amplification vector: any vulnerability that compromises the insights-client pod or its ServiceAccount token would grant the attacker read access to all Secrets across the hub cluster.
Меры по смягчению последствий
Restrict the insights-client ClusterRole to the minimum required permissions. Replace the cluster-wide secrets get/list/watch with a namespaced Role granting get access only to the specific Secret openshift-config/pull-secret in the openshift-config namespace.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Advanced Cluster Management for Kubernetes 2 | rhacm2/insights-client-rhel9 | Affected |
Показывать по
Дополнительная информация
Статус:
6.5 Medium
CVSS3
Связанные уязвимости
A flaw was found in insights-client. The component's ServiceAccount is bound to a ClusterRole granting cluster-wide secrets get, list, and watch permissions, while the code only requires access to a single specific Secret. This excessive privilege means that a compromise of the insights-client pod or ServiceAccount token would grant an attacker read access to all Secrets across the hub cluster, including managed-cluster kubeconfigs and other sensitive credentials.
A flaw was found in insights-client. The component's ServiceAccount is bound to a ClusterRole granting cluster-wide secrets get, list, and watch permissions, while the code only requires access to a single specific Secret. This excessive privilege means that a compromise of the insights-client pod or ServiceAccount token would grant an attacker read access to all Secrets across the hub cluster, including managed-cluster kubeconfigs and other sensitive credentials.
6.5 Medium
CVSS3