Rucio: Improper Authentication via SSH Challenge Tokens
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| rucio | rucio | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Rucio | Rucio |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-x585-4vv8-2mh2 | Rucio: Unauthenticated administrator impersonation through SSH challenge tokens |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.143% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rucio
Rucio rucio |
|
| Vendors & Products |
Rucio
Rucio rucio |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Rucio: Improper Authentication via SSH Challenge Tokens | |
| Weaknesses | CWE-287 | |
| References |
|
|
| Metrics |
cvssV3_1
|