CVE-2025-54064

rucio-server, rucio-ui, and rucio-webui vulnerable to insertion of X-Rucio-Auth-Token in apache access logfiles

MEDIUM
6.9
CVSS Score
Published: July 17, 2025 at 02:40 PM UTC
Updated: June 17, 2026 at 09:39 AM UTC
1 product affected across 1 vendorHelm Charts

Using helm-charts by rucio?

Get instant alerts when new vulnerabilities affect helm-charts - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.9
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

Rucio is a software framework that provides functionality to organize, manage, and access large volumes of scientific data using customizable policies. The common Rucio helm-charts for the `rucio-server`, `rucio-ui`, and `rucio-webui` define the log format for the apache access log of these components. The `X-Rucio-Auth-Token`, which is part of each request header sent to Rucio, is part of this log format. Thus, each access log line potentially exposes the credentials (Internal Rucio token, or JWT in case of OIDC authentication) of the user. Due to the length of the token (Especially for a JWT) the tokens are often truncated, and thus not usable as credential; nevertheless, the (partial) credential should not be part of the logfile. The impact of this issue is amplified if the access logs are made available to a larger group of people than the instance administrators themselves. An updated release has been supplied for the `rucio-server`, `rucio-ui` and `rucio-webui` helm-chart. The change was also retrofitted for the currently supported Rucio LTS releases. The patched versions are rucio-server 37.0.2, 35.0.1, and 32.0.1; rucio-ui 37.0.4, 35.0.1, and 32.0.2; and rucio-webui 37.0.2, 35.1.1, and 32.0.1. As a workaround, one may update the `logFormat` variable and remove the `X-Rucio-Auth-Token`.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 32.0.1v < 32.0.2v < 35.0.1v < 35.1.1v < 37.0.2v < 37.0.4
Affected range stops below 32.0.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 32.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 35.0.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 35.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 37.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 37.0.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.9MEDIUMGitHub_M
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-532

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card