Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.15.3, 0.16.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- tempo-operator
fixed in 0.15.3
- rhosdt/tempo-rhel8-operator
Version range not reported
- rhosdt/tempo-rhel8-operator
Version range not reported
- rhosdt/tempo-gateway-opa-rhel8
Version range not reported
- rhosdt/tempo-gateway-rhel8
Version range not reported
- rhosdt/tempo-jaeger-query-rhel8
Version range not reported
- rhosdt/tempo-query-rhel8
Version range not reported
- rhosdt/tempo-rhel8
Version range not reported
- github.com/grafana/tempo-operatorGo
fixed in 0.16.0