A flaw was found in Tempo Operator, where it creates a ServiceAccount, ClusterRole, and ClusterRoleBinding when a user deploys a TempoStack or TempoMonolithic instance. This flaw allows a user with full access to their namespace to extract the ServiceAccount token and use it to submit TokenReview and SubjectAccessReview requests, potentially revealing information about other users' permissions. While this does not allow privilege escalation or impersonation, it exposes information that could aid in gathering information for further attacks.
Workaround:
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2025:3607 | vendor advisory |
https://access.redhat.com/errata/RHSA-2025:3740 | vendor advisory |
https://access.redhat.com/security/cve/CVE-2025-2786 | vdb entry |
https://bugzilla.redhat.com/show_bug.cgi?id=2354811 | issue tracking |