Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator
Summary
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. Affected products named by the advisory: Red Hat OpenShift distributed tracing 3.5; Red Hat OpenShift distributed tracing 3.
What this means
In plain English
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. Privilege escalation can let an existing user or process gain permissions beyond those originally granted.
Recommended action
Primary action: update to a vendor-listed fixed release: 0.15.3.
Rewritten locally from the scraped official advisory data above; no generative API is used. The vendor advisory is authoritative.
- before 0.15.3
Official advisory · high-confidence parse· fetched 19 hours ago·verify at source
- 0.15.3
Official advisory · high-confidence parse· fetched 19 hours ago·verify at source
Mitigation
Upgrade to a fixed release: 0.15.3. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 19 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.