You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[Threading and Tasks in Chrome](https://chromium.googlesource.com/chromium/src/+/master/docs/threading_and_tasks.md)
187
181
*[Important Abstractions and Data Structures](https://www.chromium.org/developers/coding-style/important-abstractions-and-data-structures)
188
182
@@ -209,12 +203,13 @@ _Version field has "?" symbol, if a version wasn't attached to the report_
209
203
## Misc
210
204
211
205
*[NodeFuzz](https://code.google.com/archive/p/ouspg/wikis/NodeFuzz.wiki) - web browser fuzzer
212
-
*[Muon](https://github.com/brave/muon) - Build browsers and browser like applications with HTML, CSS, and JavaScript
206
+
*[brave/Muon](https://github.com/brave/muon) - Build browsers and browser like applications with HTML, CSS, and JavaScript (part of the Brave's bug bounty)
213
207
*https://ios.browsr-tests.com - list of SOP bypasses in iOS
214
208
*https://github.com/rafaybaloch/SOP-Bypass-Mini-Test-Suite - list of SOP bypasses
We started stripping javascript: from any text pasted or dragged into the address bar, but this happens after checking for other malicious patterns. Compare:
12
+
13
+
```html
14
+
15
+
data:text/html,<ahref='chrome://inducebrowsercrashforrealz'>drag me into the address bar first</a>, <ahref='javascript:chrome://inducebrowsercrashforrealz'>try me next</a>
16
+
17
+
```
18
+
19
+
Not sure if this matters in practice, but seems like a simple fix, so creating a bug just in case.
## Security: XSS by ServiceWorker for domains hosting arbitrary content, even in sandboxes
31
+
32
+
### VULNERABILITY DETAILS
33
+
34
+
ServiceWorker can turn previously unexploitable xss bugs into serious vulnerabilities :-(
35
+
36
+
As an example I've attached a simple script that installs a ServiceWorker on the Dropbox storage domain. This only uses an XSS on the *sandbox domain* of Dropbox, which was previously unexploitable. That ServiceWorker can then sniff traffic and steal the user's files as they are accessed.
37
+
38
+
Serving user files from a separate sandbox domain with no cookies used to be relatively safe, and many sites assume that it still is safe, to the point where they will serve both HTML and 'text/javascript' files from the same domain.
39
+
40
+
Ideally there would be some kind of opt-in mechanism for this; the available opt-out mechanism is hard to implement (rejecting 'Service-Worker: script' might be tricky with a caching CDN).
0 commit comments