Tempo-operator: tempo operator token exposition lead to read sensitive data
- 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 the Tempo Operator. When the Jaeger UI Monitor Tab functionality is enabled in a Tempo instance managed by the Tempo Operator, the Operator creates a ClusterRoleBinding for the Service Account of the Tempo instance to grant the cluster-monitoring-view ClusterRole. This can be exploited if a user has 'create' permissions on TempoStack and 'get' permissions on Secret in a namespace (for example, a user has ClusterAdmin permissions for a specific namespace), as the user can read the token of the Tempo service account and therefore has access to see all cluster metrics.
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