Front-end Security
summary
Examines concrete front-end XSS case studies including a Twitter URL/hash vulnerability that allowed javascript: execution via a window.location replace bug and required regex and sandboxing for a proper fix. Describes deployed defenses and tools: Content Security Policy with report-uri and nonces, HSTS headers, HttpOnly cookies, preferring POST over GET, CSP generators, scanner tooling and browser support matrices, and reports implementation outcomes (including 133 Flash vulnerabilities found in 2015).
AI-written summary · about
chapters (19)
- 0:00Frontend security intro
- 1:37Why frontend security matters
- 2:26What is XSS and types
- 3:55Non-persistent XSS Twitter case
- 7:51Fixing XSS flaw on Twitter
- 10:08Stored XSS and consequences
- 13:46Angular templates and XSS
- 15:35Active vs passive XSS
- 17:57Browsers as security helpers
- 18:19Content Security Policy basics
- 22:55CSP version 2 features
- 23:35HTTPS and MITM risks
- 26:27Public Wi-Fi security risks
- 27:10VK account hacks explained
- 28:11Strict Transport Security role
- 29:18Cookie protection methods
- 30:45Adobe Flash security issues
- 31:09Frontend security tips
- 32:33Q&A








