Issue metadata
Sign in to add a comment
|
Certain actions cause browser to revert versions on restart
Reported by
tsuserga...@gmail.com,
Feb 16 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 8872.76.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.105 Safari/537.36 Platform: Platform 8872.76.0 (Official Build) stable-channel candy Steps to reproduce the problem: 1. Use a Chromebook on the latest version of Chrome (v56) 2. Visit chrome://flags 3. Change some options, doesn't really matter what you change. 4. Hit "Restart Now" 5. Chromebook is now freed from Enterprise restrictions that are set on the device level, cloud enterprise flags do remain in effect. What is the expected behavior? The Chromebook restarts, checks the device enterprise flags, and enforces them. What went wrong? The Chromebook restarts, doesn't check anything except the cloud for enterprise flags, and allows the user to change restricted settings and options that are preserved through restarts for the account on that Chromebook. Coupled with sync encryption this allows a user to compromise local security settings without leaving any logs. Did this work before? Yes Last version (See bug #690567 ) of Chrome Chrome version: 55.0.2883.105 Channel: stable OS Version: 8872.76.0 Flash Version: Shockwave Flash 24.0 r0 My previous bug report (referenced) was closed as WontFix, this problem has regressed and is even worse now.
,
Feb 28 2017
kerrnel@ -- any chance that you want to take a quick look at this or know who might be the right person for this? I'm not sure how to even test this.
,
Feb 28 2017
There are a few things here that I do not understand, so let me try to clarify them. For starts, what do you mean that it causes the browser to revert versions? The description doesn't mention anything about the version reverting, it says that enterprise flags aren't enforced.
,
Feb 28 2017
Sorry for the confusion, anyway on the Chromebook I was testing this bug caused the browser to go back one update (very strange) in chrome://version however I have been unable to replicate this part of the issue in the latest update. From what I can see in the latest update the methods of causing the issue have been patched however I believe the underlying issue is still there and exploitable, just not through my method.
,
Feb 28 2017
So to be clear, can you currently reproduce this issue on the most recent version of Chrome OS?
,
Feb 28 2017
Yes, the issue is not replicable in the latest version. I will be watching for a regression and update the ticket accordingly.
,
Feb 28 2017
Cannot reproduce.
,
Mar 1 2017
Enterprise policy bypass appears to be related to the GPU crashing (Tested with chrome://gpucrash, resulted in same black screen) however the issue has been fixed. Some options in chrome://flags cause a GPU crash on restart.
,
Mar 1 2017
Reproduced with chrome://flags hard GPU crash. Flags enabled: experimental-canvas-features accelerated-2d-canvas 2d-dynamic-rendering-mode-switching Caused a bad GPU crash, Chromebook exited enterprise mode immediately. Bug present on latest version of Chrome. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by tsuserga...@gmail.com
, Feb 16 2017