dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-54064

MEDIUM · 6.9 CVSS v4.0 Published 2025-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Rucio helm-charts for rucio-server, rucio-ui, and rucio-webui configure Apache access logs to include the X-Rucio-Auth-Token header, exposing authentication tokens (Internal Rucio tokens or JWTs for OIDC) in plaintext log files. While tokens are often truncated due to length, partial credentials are still disclosed.

MitigationUpgrade helm-charts to patched versions (rucio-server 37.0.2/35.0.1/32.0.1, rucio-ui 37.0.4/35.0.1/32.0.2, rucio-webui 37.0.2/35.1.1/32.0.1) or modify the logFormat configuration to exclude the X-Rucio-Auth-Token variable.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify deployed Rucio helm-chart releases
    Run 'helm list -A' to list all helm releases and their versions. Identify releases named rucio-server, rucio-ui, or rucio-webui and note their versions.
    Affected if Any of these releases are deployed with versions below the patched versions (rucio-server 32.0.1/35.0.1/37.0.2, rucio-ui 32.0.2/35.0.1/37.0.4, rucio-webui 32.0.1/35.1.1/37.0.2).
  2. Inspect the Apache logFormat configuration
    Access the rucio-server, rucio-ui, or rucio-webui pods/containers. Check the Apache configuration files (typically in /etc/httpd/conf.d/ or /etc/apache2/sites-available/) for the LogFormat or CustomLog directives. Look for the string 'X-Rucio-Auth-Token' in the format string.
    Affected if The Apache LogFormat or CustomLog directive contains '%{X-Rucio-Auth-Token}i' or the literal string X-Rucio-Auth-Token.
  3. Review deployed helm-chart values
    Run 'helm get values <release-name>' for each rucio release to see the deployed configuration. Look for any custom logFormat settings or values that might override the default Apache logging configuration.
    Affected if The values include a custom logFormat that explicitly includes the X-Rucio-Auth-Token header variable.
  4. Examine access log files for token exposure
    Locate and inspect the Apache access log files in the deployed pods (typically under /var/log/httpd/ or /var/log/apache2/). Search for occurrences of the string 'X-Rucio-Auth-Token' or examine log entries for authentication token patterns (long alphanumeric strings).
    Affected if The access logs contain visible authentication tokens or partial token strings in the X-Rucio-Auth-Token header field.

A user is affected if they run rucio-server, rucio-ui, or rucio-webui helm-charts with versions below the patched releases AND their Apache configuration includes X-Rucio-Auth-Token in the log format, resulting in tokens being written to access logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade helm-charts to patched versions (rucio-server 37.0.2/35.0.1/32.0.1, rucio-ui 37.0.4/35.0.1/32.0.2, rucio-webui 37.0.2/35.1.1/32.0.1) or modify the logFormat configuration to exclude the X-Rucio-Auth-Token variable.

Recommended fix High confidence

Upgrade helm-charts to rucio-server 37.0.2/35.0.1/32.0.1, rucio-ui 37.0.4/35.0.1/32.0.2, and rucio-webui 37.0.2/35.1.1/32.0.1 based on your current LTS release

  1. Identify the current Rucio LTS release in use (32, 35, or 37) by checking the helm-chart version or Rucio server version
  2. For rucio-server: upgrade helm-chart to version 37.0.2 (if on LTS 37), 35.0.1 (if on LTS 35), or 32.0.1 (if on LTS 32)
  3. For rucio-ui: upgrade helm-chart to version 37.0.4 (if on LTS 37), 35.0.1 (if on LTS 35), or 32.0.2 (if on LTS 32)
  4. For rucio-webui: upgrade helm-chart to version 37.0.2 (if on LTS 37), 35.1.1 (if on LTS 35), or 32.0.1 (if on LTS 32)
  5. Verify that the X-Rucio-Auth-Token is no longer present in Apache access logs after the upgrade
  6. Alternatively, as a workaround without upgrading: modify the helm-chart value `logFormat` to remove the `%{X-Rucio-Auth-Token}o` variable
Caveat Minimal risk; this is a security-focused helm-chart update; ensure any custom logFormat overrides are compatible with the new default

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54064 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54064 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data