Описание
A flaw was found in insights-client. The setDefault() function logs the value of every environment variable it processes, including CCX_TOKEN, a bearer credential used in disconnected cluster deployments. When glog verbosity is set to level 2 or higher, the token is written in clear text to the pod log on every startup. An attacker with access to pod logs or centralized logging could obtain the credential, leading to unauthorized access to the CCX API.
Отчет
This is a Moderate flaw in Red Hat Advanced Cluster Management for Kubernetes. The insights-client component logs the CCX_TOKEN bearer credential in clear text at startup when glog verbosity is set to level 2 or higher. This credential is used by disconnected cluster deployments as an alternative to cloud.redhat.com. An attacker with access to pod logs or centralized logging could obtain the credential and use it to access the CCX API on behalf of the affected organization.
Меры по смягчению последствий
Ensure glog verbosity on the insights-client Deployment is set below level 2 (-v=0 or -v=1). If CCX_TOKEN must be configured for disconnected environments, restrict access to pod logs in the open-cluster-management namespace and to centralized logging backends.
Дополнительная информация
Статус:
6.3 Medium
CVSS3
Связанные уязвимости
A flaw was found in insights-client. The setDefault() function logs the value of every environment variable it processes, including CCX_TOKEN, a bearer credential used in disconnected cluster deployments. When glog verbosity is set to level 2 or higher, the token is written in clear text to the pod log on every startup. An attacker with access to pod logs or centralized logging could obtain the credential, leading to unauthorized access to the CCX API.
A flaw was found in insights-client. The setDefault() function logs the value of every environment variable it processes, including CCX_TOKEN, a bearer credential used in disconnected cluster deployments. When glog verbosity is set to level 2 or higher, the token is written in clear text to the pod log on every startup. An attacker with access to pod logs or centralized logging could obtain the credential, leading to unauthorized access to the CCX API.
6.3 Medium
CVSS3