openshift distributed tracing 3.5 Schwachstellen (CVE)

Für openshift distributed tracing 3.5 veröffentlichte CVE-Einträge, neueste zuerst. Folgen Sie, um bei neuen Einträgen eine E-Mail zu erhalten.

4 Ergebnisse
7.8Hoch
CVE-2025-7425

Libxslt: libxml2: heap use-after-free in libxslt caused by atype corruption in xmlattrptr

GNOME libxml2; Red Hat Red Hat Enterprise Linux 10; Red Hat Red Hat Enterprise Linux 7 Extended Lifecycle Support; Red Hat Red Hat Enterprise Linux 8

A flaw was found in libxslt where the attribute type, atype, flags are modified in a way that corrupts internal memory management. When XSLT functions, such as the key() process, result in tree fragments, this corruption prevents the proper cleanup of ID attr…

7.8Hoch
CVE-2025-5914

Libarchive: double free at archive_read_format_rar_seek_data() in archive_read_support_format_rar.c

libarchive; Red Hat Red Hat Enterprise Linux 10; Red Hat Red Hat Enterprise Linux 7 Extended Lifecycle Support; Red Hat Red Hat Enterprise Linux 8

A vulnerability has been identified in the libarchive library, specifically within the archive_read_format_rar_seek_data() function. This flaw involves an integer overflow that can ultimately lead to a double-free condition. Exploiting a double-free vulnerabi…

4.3Mittel
CVE-2025-2842

Tempo-operator: tempo operator token exposition lead to read sensitive data

tempo-operator; Red Hat Red Hat OpenShift distributed tracing 3.5.3; Red Hat Red Hat OpenShift distributed tracing 3

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-mon…

4.3Mittel
CVE-2025-2786

Tempo-operator: serviceaccount token exposure leading to token and subject access reviews in openshift tempo operator

tempo-operator; Red Hat Red Hat OpenShift distributed tracing 3.5.3; Red Hat Red Hat OpenShift distributed tracing 3

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 …