Stole user session after crash
Reported by
gabriel....@gmail.com,
May 11 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 Steps to reproduce the problem: 1. Open chrome and access any service like gmail or facebook 2. lock the user windows session 3. Log in the same computer with a other user 4. Open the task manager and finish all chrome process of the first user 5. Then open the chrome and click to recover the pages What is the expected behavior? Is to open the chrome without it asking to recover the pages of the first user What went wrong? The chrome recover the pages with the sessions and cookies of the previous user (That one who lock his windows session). So the second user is logged in the first user account of gmail or facebook. Did this work before? N/A Chrome version: 50.0.2661.94 m Channel: stable OS Version: 7 Home Basic - Service Pack 1 Flash Version: Shockwave Flash 21.0 r0
,
May 11 2016
Hi, thanks for the answer. I check, and the profile path is pointing to same location, but the default is not set to pointing in a different location for each user? I never needed to change this settings. Looks like the first user who install the chrome keeps his profile path. The chrome should'n check this settings per user? thanks again.
,
May 12 2016
Thank you for providing more feedback. Adding requester "wfh@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 12 2016
,
May 12 2016
Thanks for your feedback. Each Windows user will have a different profile. Can you post a screenshot of what you see in chrome://version for each different Windows user?
,
May 21 2016
,
May 21 2016
Gabriel, are you sure you are logging into two different (OS) user accounts? It sounds unlikely that two separate accounts would have access to the same AppData folder and use it by default.
,
May 21 2016
Moving off the security queue, since it doesn't seem like there's a Chrome vulnerability. Keeping restricted due to username in the file path.
,
Jun 6 2016
WontFix as both profiles were running off same profile dir so this is WAI. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by wfh@chromium.org
, May 11 2016