CyberRota Analysis
AI-GeneratedElastic Cloud on Kubernetes (ECK) is vulnerable due to the cleartext storage of sensitive information, specifically service account tokens, in workload specifications instead of referencing them from Kubernetes Secrets. This flaw allows any user with permission to read workload specifications in the affected namespace to access sensitive Elasticsearch credentials, potentially leading to unauthorized information disclosure. Organizations utilizing ECK should prioritize addressing this vulnerability to mitigate risks associated with credential exposure and unauthorized access.
Original NVD Description
Cleartext Storage of Sensitive Information in an Environment Variable (CWE-526) in Elastic Cloud on Kubernetes (ECK) can lead to information disclosure via Retrieve Embedded Sensitive Data (CAPEC-37). When ECK reconciles a Fleet Server resource that authenticates to Elasticsearch with a service account token, the token is written into the generated workload specification in cleartext rather than being referenced from the Kubernetes Secret that ECK maintains for the other credentials on the same path. Any principal able to read workload specifications in the affected namespace can therefore read a live Elasticsearch credential, even when Kubernetes RBAC does not grant that principal access to Secrets.