Open
Bug 1319346
Opened 8 years ago
Updated 2 years ago
WebChannel not isolated by originAttributes
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
REOPENED
Tracking | Status | |
---|---|---|
firefox53 | --- | affected |
firefox57 | --- | fix-optional |
People
(Reporter: hectorz, Unassigned)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [domsecurity-backlog2][OA][userContextId][tor])
Try using WebChannel from within a container tab will throw an error:
> {webChannelId} error message. No Such Channel
This is because when using origin as originOrPermission when creating a WebChannel, `_originCheckCallback` will check `{allowedOrigin}.prePath === requestPrincipal.origin` to find a matching WebChannel[1];
Since a) another check for WebChannel already uses `originNoSuffix`[2] and b) `userContextId` are ignored when matching permissions[3], I think it might be okay to just use `requestPrincipal.originNoSuffix` here?
[1]: https://dxr.mozilla.org/mozilla-central/rev/0534254e9a40/toolkit/modules/WebChannel.jsm#184
[2]: https://hg.mozilla.org/mozilla-central/rev/af0f02e07f6a#l21.53
[3]: https://hg.mozilla.org/mozilla-central/rev/299a09f24493
Updated•8 years ago
|
Component: General → DOM: Security
Product: Firefox → Core
Comment 1•8 years ago
|
||
Ethan, is this also an issue for Tor?
Flags: needinfo?(etseng)
Priority: -- → P1
Whiteboard: [domsecurity-active][OA][userContextId][tor]
Comment 2•8 years ago
|
||
That's not Ethan's email, let's change to right one(ettseng@mozilla.com).
Flags: needinfo?(etseng) → needinfo?(ettseng)
Reporter | ||
Comment 3•8 years ago
|
||
Dupe of bug 1319904, which was already fixed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Comment 4•8 years ago
|
||
I'm not sure this is a duplicate. Reopening for now and we can decide after further investigation.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 5•8 years ago
|
||
(In reply to Tanvi Vyas [:tanvi] from comment #1)
> Ethan, is this also an issue for Tor?
I went through comments in bug 1319904.
It looks to me this is a general Origin Attributes issue that has to be fixed in WebChannel.
So yes, I assume it also affects Tor First Party Isolation.
Arthur, can you help to confirm this?
Flags: needinfo?(ettseng) → needinfo?(arthuredelstein)
Comment 6•8 years ago
|
||
(In reply to Ethan Tseng [:ethan] from comment #5)
> (In reply to Tanvi Vyas [:tanvi] from comment #1)
> > Ethan, is this also an issue for Tor?
>
> I went through comments in bug 1319904.
> It looks to me this is a general Origin Attributes issue that has to be
> fixed in WebChannel.
> So yes, I assume it also affects Tor First Party Isolation.
>
> Arthur, can you help to confirm this?
Sorry for the delay -- yes, it looks to me like the issue affects first-party isolation as a part of originAttributes. As far as I can tell, the patch in bug 1319904 should solve the problem for first-party isolation as well.
Flags: needinfo?(arthuredelstein)
Comment 7•8 years ago
|
||
Bug 1319904 makes WebChannel NOT isolated by Origin Attributes.
Comment 8•8 years ago
|
||
Set it as blocking First Party Isolation for tracking.
Blocks: FirstPartyIsolation
Comment 9•8 years ago
|
||
Tanvi, this is was marked as a P1, got closed and reopened? Do we need to set a new priority? Potentially we need to find an owner for this one! Can you have a look please?
Flags: needinfo?(tanvi)
Comment 10•8 years ago
|
||
(In reply to Tanvi Vyas - behind on bugmail [:tanvi] from comment #7)
> Bug 1319904 makes WebChannel NOT isolated by Origin Attributes.
You're absolutely right. Sorry for my mistake. Indeed this looks like we need to implement a fix for first party isolation.
Comment 11•8 years ago
|
||
As discussed in the meeting, this bug is low priority but nice to have.
Priority: P1 → P3
Whiteboard: [domsecurity-active][OA][userContextId][tor] → [domsecurity-backlog][OA][userContextId][tor]
Comment 12•7 years ago
|
||
(In reply to Ethan Tseng [:ethan] from comment #11)
> As discussed in the meeting, this bug is low priority but nice to have.
Clearing my ni? queue at the moment. Thanks Ethan for de-prioritizing this work in comment 11. Clearing the ni? for Tanvi in that case.
Flags: needinfo?(tanvi)
Updated•7 years ago
|
Whiteboard: [domsecurity-backlog][OA][userContextId][tor] → [domsecurity-backlog2][OA][userContextId][tor]
Comment 13•7 years ago
|
||
Bulk change per https://bugzilla.mozilla.org/show_bug.cgi?id=1401020
status-firefox57:
--- → fix-optional
Updated•5 years ago
|
Blocks: dfpi-isolation-needed
Summary: WebChannel doesn't work in a container tab → WebChannel not isolated by originAttributes
Updated•5 years ago
|
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•