~/talk

The Insecurity Caused By Trusting Your Client-Side Storage

Talkat OWASP Global AppSec Amsterdam 2019 · on Friday, 2019-09-27· at 11:05· D201, RAI· [security, web-platform]
links:none on file
slides:none on file

Client-side stores like cookies localStorage and IndexedDB lead to persistent client-side XSS when developer code later writes those values into the DOM. The authors build a taint-tracking Chromium and an exploit candidate generator that records flows, crafts payloads and verifies them in browsers. Scanning top sites finds ~2,000 using client-side stores, 418 exploitable domains (30% of cookie flows 24% of localStorage flows) and a simple check finds 60 IndexedDB vulnerabilities validated end to end.

AI-written summary · about

  1. 0:00Intro
  2. 3:02Cookies
  3. 4:21Web Storage
  4. 6:55What we are doing
  5. 8:55The tainted chromium
  6. 12:04Exploiting web applications
  7. 13:26Exploit patterns
  8. 15:40Attack vectors
  9. 20:30Demo
  10. 22:04IndexDB Credibility
  11. 24:23Exploitable Data
  12. 27:03JSON Objects
  13. 28:47Cold Cashing
  14. 30:20Solutions
  15. 32:49Host Names
  16. 34:00Conclusion
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.