Re:Stealing Data with CSS: Attack and Defense
by deathanatos on Friday February 16, 2018 @09:23PM
(#16398518)
Say the site has an XSS vector, but the site owner has taken the reasonable precaution of putting in a Content-Security-Policy that would disallow XSS from injecting <script> tags; this would seem to poke a hole in that protection. (Unless, perhaps, similar protections where applied to CSS, but I don't think most people expect CSS to do this; the attack outline in the article was novel (and clever) to me.)
[ Parent
| on HN ]
Re:Stealing Data with CSS: Attack and Defense
by anglebracket on Friday February 16, 2018 @10:54PM
(#16398880)
Generally if you have a CSP without `unsafe-inline` you'd have have a policy that would restrict all subresources (`default-src 'none'`,) then punch holes in the policy by resource type (`img-src`, `script-src`, etc.)
For ex. if you have a proper CSP with `default-src 'none'` you should be fine so long as you didn't allow `*` or `unsafe-inline` in any of the other `<X>-src` directives.