https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 18:46:11 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-271179 EUVD-2026-271179 https://cve.radiocsirt.org/vuln/euvd-2026-271179 https://cve.radiocsirt.org/vuln/fkie_cve-2026-25138 <p>Rucio is a software framework that provides functionality to organize, manage, and access large volumes of scientific data using customizable policies. Prior to versions 35.8.3, 38.5.4, and 39.3.1, the WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames. Versions 35.8.3, 38.5.4, and 39.3.1 fix the issue.</p> <p>Rucio is a software framework that provides functionality to organize, manage, and access large volumes of scientific data using customizable policies. Prior to versions 35.8.3, 38.5.4, and 39.3.1, the WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames. Versions 35.8.3, 38.5.4, and 39.3.1 fix the issue.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-25138 https://cve.radiocsirt.org/vuln/ghsa-38wq-6q2w-hcf9 <p><strong>Affected:</strong> PyPI: rucio-webui</p> <p>### Summary The WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames.</p> <p>### Details When submitting invalid credentials to `/ui/login`, the WebUI responds with different error messages based on the existence of the provided username (identity). A non-existent username results in an error indicating that no account is associated with the identity, while an existing username with an incorrect password produces a different authentication-related error.</p> <p>This behavioral difference allows an attacker to distinguish valid usernames from invalid ones by observing the response content.</p> <p>### Proof of Concept **Bogus Login (Non-existent Username &#34;15251087&#34;)** Response contains: ``` Cannot get find any account associated with 15251087 identity. ```</p> <p>**Bogus Login (Existing Username &#34;root&#34;, Wrong Password)** Response contains: ``` Cannot get auth token. It is possible that the presented identity root is not mapped to any Rucio account root. ```</p> <p>The difference in error messages confirms whether a username exists.</p> <p>### Impact An unauthenticated attacker can enumerate valid usernames, which may be leveraged for targeted password guessing, credential stuffing, or social engineering attacks.</p> <p>### Remediation / Mitigation Return a generic authentication failure message for all login errors, regardless of whether the username exists. Avoid disclosing account or identity existenc…</p> <p><strong>Affected:</strong> PyPI: rucio-webui</p> <p>### Summary The WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames.</p> <p>### Details When submitting invalid credentials to `/ui/login`, the WebUI responds with different error messages based on the existence of the provided username (identity). A non-existent username results in an error indicating that no account is associated with the identity, while an existing username with an incorrect password produces a different authentication-related error.</p> <p>This behavioral difference allows an attacker to distinguish valid usernames from invalid ones by observing the response content.</p> <p>### Proof of Concept **Bogus Login (Non-existent Username &#34;15251087&#34;)** Response contains: ``` Cannot get find any account associated with 15251087 identity. ```</p> <p>**Bogus Login (Existing Username &#34;root&#34;, Wrong Password)** Response contains: ``` Cannot get auth token. It is possible that the presented identity root is not mapped to any Rucio account root. ```</p> <p>The difference in error messages confirms whether a username exists.</p> <p>### Impact An unauthenticated attacker can enumerate valid usernames, which may be leveraged for targeted password guessing, credential stuffing, or social engineering attacks.</p> <p>### Remediation / Mitigation Return a generic authentication failure message for all login errors, regardless of whether the username exists. Avoid disclosing account or identity existenc…</p> https://cve.radiocsirt.org/vuln/ghsa-38wq-6q2w-hcf9 https://cve.radiocsirt.org/vuln/pysec-2026-3053 <p><strong>Affected:</strong> PyPI: rucio-webui</p> <p>### Summary The WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames.</p> <p>### Details When submitting invalid credentials to `/ui/login`, the WebUI responds with different error messages based on the existence of the provided username (identity). A non-existent username results in an error indicating that no account is associated with the identity, while an existing username with an incorrect password produces a different authentication-related error.</p> <p>This behavioral difference allows an attacker to distinguish valid usernames from invalid ones by observing the response content.</p> <p>### Proof of Concept **Bogus Login (Non-existent Username &#34;15251087&#34;)** Response contains: ``` Cannot get find any account associated with 15251087 identity. ```</p> <p>**Bogus Login (Existing Username &#34;root&#34;, Wrong Password)** Response contains: ``` Cannot get auth token. It is possible that the presented identity root is not mapped to any Rucio account root. ```</p> <p>The difference in error messages confirms whether a username exists.</p> <p>### Impact An unauthenticated attacker can enumerate valid usernames, which may be leveraged for targeted password guessing, credential stuffing, or social engineering attacks.</p> <p>### Remediation / Mitigation Return a generic authentication failure message for all login errors, regardless of whether the username exists. Avoid disclosing account or identity existenc…</p> <p><strong>Affected:</strong> PyPI: rucio-webui</p> <p>### Summary The WebUI login endpoint returns distinct error messages depending on whether a supplied username exists, allowing unauthenticated attackers to enumerate valid usernames.</p> <p>### Details When submitting invalid credentials to `/ui/login`, the WebUI responds with different error messages based on the existence of the provided username (identity). A non-existent username results in an error indicating that no account is associated with the identity, while an existing username with an incorrect password produces a different authentication-related error.</p> <p>This behavioral difference allows an attacker to distinguish valid usernames from invalid ones by observing the response content.</p> <p>### Proof of Concept **Bogus Login (Non-existent Username &#34;15251087&#34;)** Response contains: ``` Cannot get find any account associated with 15251087 identity. ```</p> <p>**Bogus Login (Existing Username &#34;root&#34;, Wrong Password)** Response contains: ``` Cannot get auth token. It is possible that the presented identity root is not mapped to any Rucio account root. ```</p> <p>The difference in error messages confirms whether a username exists.</p> <p>### Impact An unauthenticated attacker can enumerate valid usernames, which may be leveraged for targeted password guessing, credential stuffing, or social engineering attacks.</p> <p>### Remediation / Mitigation Return a generic authentication failure message for all login errors, regardless of whether the username exists. Avoid disclosing account or identity existenc…</p> https://cve.radiocsirt.org/vuln/pysec-2026-3053