Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Privilege escalation issue in the Rucio WebUI #4928

Closed
bari12 opened this issue Oct 21, 2021 · 0 comments
Closed

Privilege escalation issue in the Rucio WebUI #4928

bari12 opened this issue Oct 21, 2021 · 0 comments

Comments

@bari12
Copy link
Member

bari12 commented Oct 21, 2021

Motivation

The move to FLASK as a webui backend introduced a cookie leak in the auth_token workflows of the webui. This potentially leak the contents of cookies to other sessions. Impact is that Rucio authentication tokens are leaked to other users accessing the webui within a close timeframe, thus allowing users accessing the webui with the leaked authentication token. Privileges are therefore also escalated.

Modification

The underlying issue is that one of the cooke variables is defined as global, thus leaking within the wsgi_container in sessions executed in close time. A fix is currently in preparation.

Related issue is #4810

@bari12 bari12 changed the title Privilige escalation issue in the Rucio WebUI Privelege escalation issue in the Rucio WebUI Oct 21, 2021
bari12 added a commit to bari12/rucio that referenced this issue Oct 21, 2021
@bari12 bari12 changed the title Privelege escalation issue in the Rucio WebUI Privilege escalation issue in the Rucio WebUI Oct 21, 2021
bari12 added a commit to bari12/rucio that referenced this issue Oct 21, 2021
@bari12 bari12 closed this as completed in 1dba6b5 Oct 21, 2021
bari12 added a commit that referenced this issue Oct 21, 2021
…escalation

WebUI: Fix privilege escalation; Fix #4928
bari12 added a commit that referenced this issue Oct 21, 2021
@bari12 bari12 added this to the 1.26.7-webui milestone Oct 21, 2021
bari12 added a commit that referenced this issue Oct 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants