Rucio: Improper Authentication via SSH Challenge Tokens
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in rucio 35.9.1, rucio 38.6.1, rucio 40.4.2 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| rucio | >=41.0.0 <41.1.1, >=1.14.0 <35.9.1, >=36.0.0 <38.6.1, >=39.0.0 <40.4.2 | ||
| pypi: rucio | >=1.14.0.post1 <35.9.1, >=36.0.0rc1 <38.6.1, >=39.0.0rc1 <40.4.2, >=41.0.0rc1 <41.1.1 | 35.9.1, 38.6.1, 40.4.2, 41.1.1 |
Exploit evidence
1 public sources
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket