"no-cors" CSS SOP violation
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Per our current set of definitions a service worker reveals what resources a "no-cors" CSS stylesheet attached to a document loads. In particular this can leak confidential tokens in the URLs.
Entered the public record here: http://krijnhoetmer.nl/irc-logs/whatwg/20150703#l-286
According to @jakearchibald resource timing (paging @igrigorik) did this first, in both Chrome and Firefox.
I think we should revert both, seems like bad precedent to cut more holes in SOP.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the issue and the linked WHATWG IRC log, then examine the service worker and resource timing behavior described for "no-cors" CSS stylesheets. Determine whether both exposures should be reverted; done means reaching and documenting a decision on the SOP and confidential-URL implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100