Technical impact
Rucio permits unauthenticated clients to request an SSH challenge token for any account and then reuse that token as an authentication token. This flaw allows an attacker to impersonate any user, including privileged administrative accounts, with full control over the system. The weakness stems from the authentication routine not distinguishing between short‑lived challenge nonces and stored authentication tokens, a classic example of Improper Authentication (CWE‑287).
Affected Systems
The affected product is Rucio, a scientific data management framework. Versions from 1.14.0 up through 35.9.1, 38.6.1, 40.4.2, and 41.1.1 are vulnerable. Rucio releases 35.9.1, 38.6.1, 40.4.2, and 41.1.1 contain the patch that separates challenge tokens from authentication tokens.
Risk and Exploitability
The vulnerability has a CVSS score of 10, indicating critical severity. EPSS is not available, so the current exploitation likelihood cannot be quantified, but the absence of restrictions on the challenge token endpoint means an attacker could exploit it from any network position that can reach the Rucio API. The flaw is not listed in CISA’s KEV catalog, yet the open‑source nature of Rucio means that the exploit code could be freely distributed. Until a supported version is deployed, the risk persists.
Github GHSA