CVE-2025-54064 (GCVE-0-2025-54064)
Vulnerability from cvelistv5 – Published: 2025-07-17 14:40 – Updated: 2025-07-17 20:01- CWE-532 - Insertion of Sensitive Information into Log File
| URL | Tags |
|---|---|
| https://github.com/rucio/helm-charts/security/adv… | x_refsource_CONFIRM |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| rucio | helm-charts |
Affected:
rucio-server < 32.0.1
Affected: rucio-server >= 33.0.0, < 35.0.1 Affected: rucio-server >= 36.0.0, < 37.0.2 Affected: rucio-ui < 32.0.2 Affected: rucio-ui >= 33.0.0, < 35.1.1 Affected: rucio-ui >= 36.0.0, < 37.0.4 Affected: rucio-webui < 32.0.1 Affected: rucio-webui >= 33.0.0, < 35.1.1 Affected: rucio-webui >= 36.0.0, < 37.0.2 |
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-54064",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-07-17T20:01:37.791373Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2025-07-17T20:01:54.062Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "helm-charts",
"vendor": "rucio",
"versions": [
{
"status": "affected",
"version": "rucio-server \u003c 32.0.1"
},
{
"status": "affected",
"version": "rucio-server \u003e= 33.0.0, \u003c 35.0.1"
},
{
"status": "affected",
"version": "rucio-server \u003e= 36.0.0, \u003c 37.0.2"
},
{
"status": "affected",
"version": "rucio-ui \u003c 32.0.2"
},
{
"status": "affected",
"version": "rucio-ui \u003e= 33.0.0, \u003c 35.1.1"
},
{
"status": "affected",
"version": "rucio-ui \u003e= 36.0.0, \u003c 37.0.4"
},
{
"status": "affected",
"version": "rucio-webui \u003c 32.0.1"
},
{
"status": "affected",
"version": "rucio-webui \u003e= 33.0.0, \u003c 35.1.1"
},
{
"status": "affected",
"version": "rucio-webui \u003e= 36.0.0, \u003c 37.0.2"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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`."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-532",
"description": "CWE-532: Insertion of Sensitive Information into Log File",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2025-07-17T14:40:59.619Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/rucio/helm-charts/security/advisories/GHSA-cmfq-f2v2-vj33",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/rucio/helm-charts/security/advisories/GHSA-cmfq-f2v2-vj33"
}
],
"source": {
"advisory": "GHSA-cmfq-f2v2-vj33",
"discovery": "UNKNOWN"
},
"title": "rucio-server, rucio-ui, and rucio-webui vulnerable to insertion of X-Rucio-Auth-Token in apache access logfiles"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2025-54064",
"datePublished": "2025-07-17T14:40:59.619Z",
"dateReserved": "2025-07-16T13:22:18.204Z",
"dateUpdated": "2025-07-17T20:01:54.062Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2025-54064",
"date": "2026-11-16",
"epss": "0.00465",
"percentile": "0.40782"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "helm-charts",
"vendor": "rucio",
"versions": [
{
"status": "affected",
"version": "rucio-server \u003c 32.0.1"
},
{
"status": "affected",
"version": "rucio-server \u003e= 33.0.0, \u003c 35.0.1"
},
{
"status": "affected",
"version": "rucio-server \u003e= 36.0.0, \u003c 37.0.2"
},
{
"status": "affected",
"version": "rucio-ui \u003c 32.0.2"
},
{
"status": "affected",
"version": "rucio-ui \u003e= 33.0.0, \u003c 35.1.1"
},
{
"status": "affected",
"version": "rucio-ui \u003e= 36.0.0, \u003c 37.0.4"
},
{
"status": "affected",
"version": "rucio-webui \u003c 32.0.1"
},
{
"status": "affected",
"version": "rucio-webui \u003e= 33.0.0, \u003c 35.1.1"
},
{
"status": "affected",
"version": "rucio-webui \u003e= 36.0.0, \u003c 37.0.2"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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`."
},
{
"lang": "es",
"value": "Rucio es un framework de software que proporciona funcionalidad para organizar, administrar y acceder a grandes vol\u00famenes de datos cient\u00edficos mediante pol\u00edticas personalizables. Los diagramas de Helm comunes de Rucio para `rucio-server`, `rucio-ui` y `rucio-webui` definen el formato de registro para el registro de acceso de Apache de estos componentes. El `X-Rucio-Auth-Token`, que forma parte de cada encabezado de solicitud enviado a Rucio, es parte de este formato de registro. Por lo tanto, cada l\u00ednea de registro de acceso expone potencialmente las credenciales (token interno de Rucio o JWT en caso de autenticaci\u00f3n OIDC) del usuario. Debido a la longitud del token (especialmente para un JWT), los tokens a menudo se truncan y, por lo tanto, no se pueden usar como credenciales; sin embargo, la credencial (parcial) no debe formar parte del archivo de registro. El impacto de este problema se amplifica si los registros de acceso se ponen a disposici\u00f3n de un grupo m\u00e1s amplio de personas que los propios administradores de instancias. Se ha publicado una versi\u00f3n actualizada para los diagramas de Helm `rucio-server`, `rucio-ui` y `rucio-webui`. El cambio tambi\u00e9n se implement\u00f3 para las versiones LTS de Rucio actualmente compatibles. Las versiones parcheadas son rucio-server 37.0.2, 35.0.1 y 32.0.1; rucio-ui 37.0.4, 35.0.1 y 32.0.2; y rucio-webui 37.0.2, 35.1.1 y 32.0.1. Como soluci\u00f3n alternativa, se puede actualizar la variable `logFormat` y eliminar el `X-Rucio-Auth-Token`."
}
],
"id": "CVE-2025-54064",
"lastModified": "2026-06-17T09:39:21.473",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-54064",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-07-17T20:01:37.791373Z",
"version": "2.0.3"
}
}
]
},
"published": "2025-07-17T15:15:27.733",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/rucio/helm-charts/security/advisories/GHSA-cmfq-f2v2-vj33"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-532"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
},
"redhat_vex": {
"current_release_date": "2025-07-19T15:00:31+00:00",
"cve": "CVE-2025-54064",
"id": "CVE-2025-54064",
"initial_release_date": "2025-01-01T00:00:00+00:00",
"product_status:known_not_affected": "1",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "rucio-server, rucio-ui, and rucio-webui vulnerable to insertion of X-Rucio-Auth-Token in apache access logfiles",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-54064.json",
"version": "3"
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-54064",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-07-17T20:01:37.791373Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2025-07-17T20:01:51.257Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "helm-charts",
"vendor": "rucio",
"versions": [
{
"status": "affected",
"version": "rucio-server \u003c 32.0.1"
},
{
"status": "affected",
"version": "rucio-server \u003e= 33.0.0, \u003c 35.0.1"
},
{
"status": "affected",
"version": "rucio-server \u003e= 36.0.0, \u003c 37.0.2"
},
{
"status": "affected",
"version": "rucio-ui \u003c 32.0.2"
},
{
"status": "affected",
"version": "rucio-ui \u003e= 33.0.0, \u003c 35.1.1"
},
{
"status": "affected",
"version": "rucio-ui \u003e= 36.0.0, \u003c 37.0.4"
},
{
"status": "affected",
"version": "rucio-webui \u003c 32.0.1"
},
{
"status": "affected",
"version": "rucio-webui \u003e= 33.0.0, \u003c 35.1.1"
},
{
"status": "affected",
"version": "rucio-webui \u003e= 36.0.0, \u003c 37.0.2"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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`."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-532",
"description": "CWE-532: Insertion of Sensitive Information into Log File",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2025-07-17T14:40:59.619Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/rucio/helm-charts/security/advisories/GHSA-cmfq-f2v2-vj33",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/rucio/helm-charts/security/advisories/GHSA-cmfq-f2v2-vj33"
}
],
"source": {
"advisory": "GHSA-cmfq-f2v2-vj33",
"discovery": "UNKNOWN"
},
"title": "rucio-server, rucio-ui, and rucio-webui vulnerable to insertion of X-Rucio-Auth-Token in apache access logfiles"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2025-54064",
"datePublished": "2025-07-17T14:40:59.619Z",
"dateReserved": "2025-07-16T13:22:18.204Z",
"dateUpdated": "2025-07-17T20:01:54.062Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.