Re: [w3c/ServiceWorker] Support No-Vary-Search header in Cache API (Issue #1798)

ricea left a comment (w3c/ServiceWorker#1798)

> Specifically, it seems like if the malicious page is the top-level browsing context and the browser is partitioning, then any fetches made by the (first-party) ServiceWorker will themselves be partitioned with the malicious site as the partition key, so the only way any entropy could be extracted is if the malicious page convinces the user to log into the site in an iframe (thereby having the partition key).

In Chrome cookies are not partitioned. In the default configuration, third-party cookies are enabled, so if the user has logged into `target` in any context the attack will work, with no user action required.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1798#issuecomment-3501353935
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1798/3501353935@github.com>