Issue metadata
Sign in to add a comment
|
Security: Signed in pages remain in signed in state after crash.
Reported by
paragyer...@gmail.com,
Apr 23 2016
|
||||||||||||||||||
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 see the following link for instructions on filing security bugs: http://www.chromium.org/Home/chromium-security/reporting-security-bugs VULNERABILITY DETAILS Hi, I want to report a security issue where after Chrome crash the signed in pages remain in signed in state. I had few HTTPS sites which should ideally be logged out after crash. VERSION Chrome Version: [49.0.2623.112 m] + [stable, beta, or dev] Operating System: [Win 7 Professional, Service Pack 1] REPRODUCTION CASE On this chrome version every crash doesn't logs off the site. FOR CRASHES, PLEASE INCLUDE THE FOLLOWING ADDITIONAL INFORMATION Type of crash: [browser] Crash State: [see link above: stack trace, registers, exception record] Client ID (if relevant): [see link above]
,
Aug 2 2016
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
,
Oct 1 2016
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
,
Oct 2 2016
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
,
Oct 2 2016
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by vakh@chromium.org
, Apr 25 2016