Rucio authentication bypass via SSH challenge tokens
rucio
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| rucio PyPI |
|
|
rucio
| Product | Affected | Fixed in |
|---|---|---|
| rucio PyPI |
|
|
Rucio is a scientific data management framework. From 1.14.0 until 35.9.1, 38.6.1, 40.4.2, and 41.1.1, validate_auth_token in lib/rucio/core/authentication.py does not distinguish short-lived SSH challenge nonces from authentication tokens stored in the same token table. An unauthenticated attacker can request /auth/ssh_challenge_token for an arbitrary account by supplying X-Rucio-Account, then present the returned X-Rucio-SSH-Challenge-Token as X-Rucio-Auth-Token to authenticate to other API endpoints as that account, including an administrative account. This issue is fixed in versions 35.9.1, 38.6.1, 40.4.2, and 41.1.1.
From the CVE record · GitHub_M
Rucio's token validation accepts short-lived SSH challenge nonces as authentication tokens. An unauthenticated attacker can request a challenge token for an arbitrary account through an API endpoint, then use it to access other endpoints as that account, including an administrative account; no user interaction is described.
Check deployments using PyPI rucio versions >=1.14.0.post1 <35.9.1, >=36.0.0rc1 <38.6.1, >=39.0.0rc1 <40.4.2, or >=41.0.0rc1 <41.1.1.