Issue metadata
Sign in to add a comment
|
Security: Unexpectedly signed into Chrome after using webplwiz
Reported by
jeromest...@gmail.com,
Feb 7 2018
|
||||||||||||||||||||
Issue descriptionThis template is ONLY for reporting security bugs. If you are reporting a Download Protection Bypass bug, please use the "Security - Download Protection" template. For all other reports, please use a different template. Please READ THIS FAQ before filing a bug: https://chromium.googlesource.com /chromium/src/+/master/docs/security/faq.md Please see the following link for instructions on filing security bugs: https://www.chromium.org/Home/chromium-security/reporting-security-bugs NOTE: Security bugs are normally made public once a fix has been widely deployed. VULNERABILITY DETAILS Please provide a brief explanation of the security issue. VERSION Chrome Version: Version 64.0.3282.119 (Official Build) (64-bit) + [stable, beta, or dev] ? stable i think. Operating System: win 10 vers 1709 REPRODUCTION CASE login to chrome via google login, create new windows user via webplwiz windows app, login as new user, delete other windows user, open chrome, you will see you are still logged in as whoever you were in the old windows account. FOR CRASHES, PLEASE INCLUDE THE FOLLOWING ADDITIONAL INFORMATION none
,
Feb 8 2018
Closing due to lack of response.
,
May 18 2018
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by elawrence@chromium.org
, Feb 7 2018Labels: Needs-Feedback OS-Windows
Summary: Security: Unexpectedly signed into Chrome after using webplwiz (was: Security: issue)