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

Users getting logged on as others after seeing 502 bad gateway error #3385

Closed
1 of 6 tasks
cwb124 opened this issue Feb 7, 2019 · 7 comments
Closed
1 of 6 tasks

Users getting logged on as others after seeing 502 bad gateway error #3385

cwb124 opened this issue Feb 7, 2019 · 7 comments
Labels
bug P0 Critical Issue

Comments

@cwb124
Copy link

cwb124 commented Feb 7, 2019

Frontend Deployment type

  • Cloud Foundry Application (cf push)
  • Kubernetes, using a helm chart
  • Docker, using docker compose
  • Docker, single container deploying all components
  • npm run start
  • Other (please specify below)

I have Stratos deployed from the stable branch as of Feb 6. This is deployed to a very heavily used CF foundation.

We have had two users report a potential security issue where they received a 502 Bad Gateway error when trying to log into Stratos. When they hit refresh on their browser window (Chrome) they were logged into the Stratos UI but as another user who is in an org that they are not a member of. I think this is a serious security flaw. I am unable to recreate it but I have screenshots from the user that backs up the claim.

@nwmac
Copy link
Contributor

nwmac commented Feb 7, 2019

@cwb124 Okay - I'll need your help to get to the bottom of this - its not something we've encountered but we definitely need to understand what issue is here as clearly as you describe it there is a security problem.

Are you able to share any further information to help diagnose?

What would really help is if you can using the Chrome browser, open the developer tools, go to the network tab and check 'Preserve Log'. If you can then reproduce the issue in the browser and then export the network log to a HAR file, so we can take a look - you can do this by right-clicking on any of the network requests on the left and choose "Save as HAR with content". If you could share that with us, that would be very helpful.

Otherwise, would it be possible to for us to arrange to meet with you or one of your users and user a shared session to observe and diagnose the issue as it happens for them?

Notes on exporting the network log to a HAR file are also here: https://developers.google.com/web/tools/chrome-devtools/network-performance/reference

@nwmac nwmac added security issue P0 Critical Issue bug labels Feb 7, 2019
@cwb124
Copy link
Author

cwb124 commented Feb 7, 2019

We have communication out for users to let us know if they experience it. We've been using Stratos for the better part of a year and I've only had this issue reported to us twice but both were reported in the last week or so. My team is unable to reproduce so I am not sure where we go from here. I apologize for the vagueness of this bug and the lack of logs/data but will do our best to get something in the event it happens again.

@richard-cox
Copy link
Contributor

@cwb124 Couple of quick question to help us attempt to reproduce ...

  1. How many instances does the Stratos cf application have?
  2. Is there an external database service linked to the Stratos application?

@KlapTrap KlapTrap closed this as completed Feb 7, 2019
@KlapTrap KlapTrap reopened this Feb 7, 2019
@cwb124
Copy link
Author

cwb124 commented Feb 7, 2019

5 instances of Console in the particular environment where we saw this happen twice. We haven't seen this reported in any of our other 7 sites that use Stratos btw, but this one is the heaviest used. No external database linked.

@nwmac
Copy link
Contributor

nwmac commented Feb 7, 2019

@cwb124 are you using SSO for login, or the Stratos username/password?

@cwb124
Copy link
Author

cwb124 commented Feb 7, 2019

No SSO in our environments.

@nwmac
Copy link
Contributor

nwmac commented Feb 14, 2019

Addressed in 2.3.0

@nwmac nwmac closed this as completed Feb 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug P0 Critical Issue
Projects
None yet
Development

No branches or pull requests

4 participants