Insane in the IFRAME -- The case for client-side HTML sanitization
•Transferir como PPTX, PDF•
3 gostaram•4,792 visualizações
Server-side HTML sanitization is a familiar web application building block, yet despite years of offensive security research, defensive “sanitizer science” is still a kind of voodoo magic. This talk will make the case that as server-side HTML sanitizers lack the ability to effectively simulate every potential user agent, the client itself is the only party empowered to perform accurate sanitization. We will examine the DOM API primitives required to perform such client-side sanitization and review results and learning from a prototype implementation.
Recomendados
Mais conteúdo relacionado
Semelhante a Insane in the IFRAME -- The case for client-side HTML sanitization
Semelhante a Insane in the IFRAME -- The case for client-side HTML sanitization (20)
Último
Último (20)
Insane in the IFRAME -- The case for client-side HTML sanitization
- 1. David Ross Principal Software Security Engineer Trustworthy Computing Security Microsoft
- 2. @randomdross
- 5. *
- 11. difficult
- 13. • No independent parsing / context handling
- 14. everything else
- 17. 3. Remove elements / attributes / etc. not explicitly allowed* *Old (less-performant) approach: Build yet another DOM by copying safe elements / attributes / etc. to a new DOM during tree walk
- 22. setAttribute
- 28. [Demo] [Benchmark] Options precedence / inheritance rules: (Options specified on target element) > (options specified on sanitize() call) > (default options)
- 32. Mario Heiderich @0x6D6172696F JSAgents / IceShield Gareth Heyes @garethheyes JSLR Ben Livshits Loris D’Antoni FAST Caja HTML sanitizer Stefano Di Paola Eduardo ‘Sirdarckcat’Vela N.
- 34. I just presented on HTML sanitization at OWASP AppSec EU 2013. AMA! (self.AMA) 1 Submitted 1 second ago by randomdross 0 comments share