What is the severity of REDHAT-BUG-2354811?

The severity of REDHAT-BUG-2354811 is considered to be significant due to potential unauthorized access to sensitive resources.

How do I fix REDHAT-BUG-2354811?

To fix REDHAT-BUG-2354811, ensure that only authorized users have full access to their namespace and review the permissions associated with ServiceAccount, ClusterRole, and ClusterRoleBinding.

What impact does REDHAT-BUG-2354811 have on OpenShift security?

REDHAT-BUG-2354811 can lead to unauthorized users gaining access to the ServiceAccount token, potentially compromising the security of the OpenShift environment.

Which versions of OpenShift are affected by REDHAT-BUG-2354811?

REDHAT-BUG-2354811 affects Red Hat OpenShift Container Platform, but specific versions should be confirmed with Red Hat's official documentation.

Is there a workaround for REDHAT-BUG-2354811?

A possible workaround for REDHAT-BUG-2354811 is to limit namespace permissions and regularly audit ServiceAccount access to reduce exposure.

Vulnerability/
REDHAT-BUG-2354811

medium

25/3/2025

2/4/2025

REDHAT-BUG-2354811

First published: Tue Mar 25 2025(Updated: )

The Tempo Operator in OpenShift Distributed Tracing creates a ServiceAccount, ClusterRole, and ClusterRoleBinding when a user deploys a TempoStack or TempoMonolithic instance. This design allows any user with full access to their namespace to retrieve the associated ServiceAccount token and utilize it to make privileged API calls to: Validate bearer tokens using the TokenReview API. Check user permissions using the SubjectAccessReview API.

Affected Software	Affected Version	How to fix
Red Hat OpenShift Container Platform

Never miss a vulnerability like this again

Reference Links

https://bugzilla.redhat.com/show_bug.cgi?id=2354811

Frequently Asked Questions

What is the severity of REDHAT-BUG-2354811?
The severity of REDHAT-BUG-2354811 is considered to be significant due to potential unauthorized access to sensitive resources.
How do I fix REDHAT-BUG-2354811?
To fix REDHAT-BUG-2354811, ensure that only authorized users have full access to their namespace and review the permissions associated with ServiceAccount, ClusterRole, and ClusterRoleBinding.
What impact does REDHAT-BUG-2354811 have on OpenShift security?
REDHAT-BUG-2354811 can lead to unauthorized users gaining access to the ServiceAccount token, potentially compromising the security of the OpenShift environment.
Which versions of OpenShift are affected by REDHAT-BUG-2354811?
REDHAT-BUG-2354811 affects Red Hat OpenShift Container Platform, but specific versions should be confirmed with Red Hat's official documentation.
Is there a workaround for REDHAT-BUG-2354811?
A possible workaround for REDHAT-BUG-2354811 is to limit namespace permissions and regularly audit ServiceAccount access to reduce exposure.

collector/redhat-bugzilla
source/Red Hat
alias/CVE-2025-2786
agent/references
agent/last-modified-date
agent/severity
agent/type
agent/description
agent/first-publish-date
agent/source
agent/event
agent/softwarecombine
agent/tags
agent/guess-ai
agent/software-canonical-lookup
vendor/red hat
canonical/red hat openshift container platform

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.