New issue
Advanced search Search tips

Issue 824606 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: Bug-Security



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 description

VERSION
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 
 
Can you flesh out this report with a bit more detail? E.g.  in #2, what do you mean when you say "Failed", and what do you "Observe" in step #4 and what do you expect to observe?

When I run this repro, I see "User 1" from the "Attack" tab, then "User 1" from the "Vuln" tab, then "User 2, connected to others" from the second "Vuln" tab.
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.

In step 4, isn't the worker in tab 3 shared with the worker in tab 2 (which is same origin)?
Components: Blink>Workers
(Notably, this used to behave differently and data:-sourced SharedWorkers were incorrectly shared across origins. That was fixed in  Issue 787103 ).
Yes, in step #4, the worker in tab 3 shared with worker in tab 2.
Tab 2 and Tab 3 are same-origin to one another. Where's the SOP violation?
Hmm... now I can understand... thanks for posting comment #4.
Thank you so much for the comments and your feedback :-)

Comment 9 by cthomp@chromium.org, Mar 22 2018

Status: WontFix (was: Unconfirmed)
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.
Project Member

Comment 10 by sheriffbot@chromium.org, Jun 29 2018

Labels: -Restrict-View-SecurityTeam allpublic
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