This question already has an answer here:

This is a common sight in content security policies:

style-src 'unsafe-inline'

I know that this "UI redressing attacks" that can be use for phishing or just defamation. But are there other threats as well? In particular, I am interested in:

  • Script execution
  • Data exfiltration

Can a liberal CSP for styles lead to any of those? If so, how?

marked as duplicate by Anders, Community Oct 18 '18 at 13:10

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • (Strongly) related: Cross site styling vulnerability?. You might want to point to that question in your question, and limit this question specifically to CSP issues (eg bypass of other CSP directives via this one), but exclude CSS injection in general. – tim Oct 18 '18 at 11:34
  • One of the comments in Dropbox sees this as a form of separating code on the website via referencing to whitelisted source instead. "This enforces code-data separation: all code running in the page has to come from script files in a whitelist of sources". – NASAhorse Oct 18 '18 at 12:23