{"uuid": "1276c817-a661-4c87-9c6f-70c2c4d4c285", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-2842", "type": "seen", "source": "https://t.me/cvedetector/21874", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-2842 - Tempo Operator ClusterRoleBinding Escalation\", \n  \"Content\": \"CVE ID : CVE-2025-2842 \nPublished : April 2, 2025, 12:15 p.m. | 2\u00a0hours, 4\u00a0minutes ago \nDescription : 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.  \nThis 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. \nSeverity: 4.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"02 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-02T16:39:36.000000Z"}