New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 881847 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Content-Security-Policy blocks inline styles, even when they are whitelisted via hash

Reported by ianpoli...@gmail.com, Sep 7

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36

Steps to reproduce the problem:
1. Use a CSP that blocks inline styles
2. Use inline CSS within a page (in this case, initiated via JavaScript)
3. Whitelist the styles with SHA256 hash(es) in the style-src directive
4. Load the page

What is the expected behavior?
The browser executes and renders the inline CSS, with no CSP violations

What went wrong?
Chrome 69 is blocking the execution of inline CSS, even when the CSS is hashed and whitelisted in the CSP. The console log outputs the in-use CSP, as well as a hash value that would be required to allow execution. However, the suggested hash(es) already exist in the CSP.

Did this work before? N/A 

Chrome version: 69.0.3497.81  Channel: stable
OS Version: 10.0
Flash Version: 

Chrome 68 permitted these exact hashes, but Chrome 69 does not.

Haven't included an attached file, since a full online  test is required, I believe. I'm testing with reCAPTCHA v2 at https://venturedisplay.co.uk/recaptcha/
 
2018-09-07 16_10_32.png
19.7 KB View Download
Cc: mkwst@chromium.org vogelheim@chromium.org
Components: Blink>SecurityFeature>ContentSecurityPolicy
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Bug-Regression
Owner: andypaicu@chromium.org
Status: Assigned (was: Unconfirmed)
Hi, adding some of the chrome web platform people, as this is the second time I've seen this report for Chrome 69. Removing security labels because extra blocking is a functionality, not a security bug.

This one strikes me as a real bug because the error message suggests a hash that is indeed listed in the CSP.

Sign in to add a comment