Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove same-origin blanket enforcement from CSP Embedded Enforcement #251

Open
shhnjk opened this issue Sep 6, 2023 · 1 comment
Open
Labels
blocked Coming to a position is blocked on issues identified with the spec or proposal. from: Google Proposed, edited, or co-edited by Google. topic: security venue: W3C Web Application Security WG Proposal is being reviewed in the W3C's Web Application Security WG (aka WebAppSec)

Comments

@shhnjk
Copy link

shhnjk commented Sep 6, 2023

WebKittens

No response

Title of the spec

Remove same-origin blanket enforcement in CSP Embedded Enforcement

URL to the spec

https://github.com/w3c/webappsec-cspee/pull/28/files

URL to the spec's repository

https://github.com/w3c/webappsec-cspee/

Issue Tracker URL

No response

Explainer URL

w3c/webappsec-cspee#28

TAG Design Review URL

No response

Mozilla standards-positions issue URL

mozilla/standards-positions#878

WebKit Bugzilla URL

No response

Radar URL

No response

Description

CPS Embedded Enforcement's blanket enforcement logic specific to same-origin iframes exposes a new way to block certain resources from loading in the iframe. This allowed attacks which are not possible before (example).

Given this part of blanket enforcement is rarely used (~0.000015% in Chrome), Chromium is planning to remove the specific logic in the CSP Embedded Enforcement. Therefore, we'd like to get Webkit's position on this.

@annevk
Copy link
Contributor

annevk commented Sep 6, 2023

I can't find any history of WebKit having taken a position on CSPEE. Assuming we haven't, this would be blocked on taking a position on CSPEE. I see that Mozilla took a position of non-harmful on that: mozilla/standards-positions#326.

@annevk annevk added topic: security venue: W3C Web Application Security WG Proposal is being reviewed in the W3C's Web Application Security WG (aka WebAppSec) from: Google Proposed, edited, or co-edited by Google. labels Sep 6, 2023
@annevk annevk added the blocked Coming to a position is blocked on issues identified with the spec or proposal. label Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Coming to a position is blocked on issues identified with the spec or proposal. from: Google Proposed, edited, or co-edited by Google. topic: security venue: W3C Web Application Security WG Proposal is being reviewed in the W3C's Web Application Security WG (aka WebAppSec)
Projects
None yet
Development

No branches or pull requests

2 participants