Issue metadata
Sign in to add a comment
|
Security: Same-origin policy violation with data: URL shared workers
Reported by
chromium...@gmail.com,
Mar 22 2018
|
||||||||||||||||||||
Issue descriptionVERSION Chrome Version: 67.0.3377.0 (Official Build) canary (64-bit) Operating System: Mac REPRODUCTION CASE 1. load https://attack.shhnjk.com/ConnectedWorkers.html 2. Click on the button => Failed 3. Back to the origin tab 4. Click on the button again => Observe
,
Mar 22 2018
Sorry, I think my explanation was unclear. In step #2 you can see "Hello, User 1" from the "Attack" tab (expected behavior) In step #4 you can see "Hello, User 2! Successfully connected with other users!" (unexpected behavior) I was expecting to get the same result as in step #2. The problem here is a shared worker created from a data URL in one tab can be shared by another tab with a different origin.
,
Mar 22 2018
In step 4, isn't the worker in tab 3 shared with the worker in tab 2 (which is same origin)?
,
Mar 22 2018
(Notably, this used to behave differently and data:-sourced SharedWorkers were incorrectly shared across origins. That was fixed in Issue 787103 ).
,
Mar 22 2018
Yes, in step #4, the worker in tab 3 shared with worker in tab 2.
,
Mar 22 2018
Tab 2 and Tab 3 are same-origin to one another. Where's the SOP violation?
,
Mar 22 2018
Hmm... now I can understand... thanks for posting comment #4.
,
Mar 22 2018
Thank you so much for the comments and your feedback :-)
,
Mar 22 2018
Closing this as WontFix as it seems this is not actually an SOP violation. Feel free to comment/reopen if there are more details I'm missing.
,
Jun 29 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
, Mar 22 2018