Rucio WebUI has a Stored Cross-site Scripting (XSS) vulnerability its Identity Name
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 35.8.3, 38.5.4, 39.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
Rucio is a software framework that provides functionality to organize, manage, and access large volumes of scientific data using customizable policies. Versions prior to 35.8.3, 38.5.4, and 39.3.1 have a stored Cross-Site Scripting (XSS) vulnerability in the Identity Name of the WebUI where attacker-controlled input is persisted by the backend and later rendered in the WebUI without proper output encoding. This allows arbitrary JavaScript execution in the context of the WebUI for users who view affected pages, potentially enabling session token theft or unauthorized actions. Versions 35.8.3, 38.5.4, and 39.3.1 fix the issue.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- rucio rucio
fixed in 35.8.3; From 36.0.0rc1 · fixed in 38.5.4; From 39.0.0rc1 · fixed in 39.3.1
- rucio-webuiPyPI
fixed in 35.8.3
- rucio-webuiPyPI
From 36.0.0rc1 · fixed in 38.5.4
- rucio-webuiPyPI
From 39.0.0rc1 · fixed in 39.3.1
- rucio-webuiPyPI
fixed in 35.8.3; From 36.0.0rc1 · fixed in 38.5.4; From 39.0.0rc1 · fixed in 39.3.1