Difference between revisions of "Training 2017 - Exploiting Websites by using offensive HTML, SVG, CSS and other Browser-Evil"
From BruCON 2017
(→Exploiting Websites by using offensive HTML, SVG, CSS and other Browser-Evil) |
|||
Line 1: | Line 1: | ||
=Exploiting Websites by using offensive HTML, SVG, CSS and other Browser-Evil= | =Exploiting Websites by using offensive HTML, SVG, CSS and other Browser-Evil= | ||
− | Probably one of the best courses when it comes to exploiting websites and application has returned at BruCON once more. Mario (will host this 3-day course and will guide you through the latest and greatest when it comes to exploiting web application and sites. | + | Probably one of the best courses when it comes to exploiting websites and application has returned at BruCON once more. Mario of Cure53 ([[Image:300px-twitter-icon.jpg|17px]] [https://twitter.com/0x6D6172696F @0x6D6172696F] will host this 3-day course and will guide you through the latest and greatest when it comes to exploiting web application and sites. |
===Course Description=== | ===Course Description=== |
Revision as of 13:51, 24 May 2017
Contents
Exploiting Websites by using offensive HTML, SVG, CSS and other Browser-Evil
Probably one of the best courses when it comes to exploiting websites and application has returned at BruCON once more. Mario of Cure53 ( @0x6D6172696F will host this 3-day course and will guide you through the latest and greatest when it comes to exploiting web application and sites.
Course Description
Course Contents
More and more web applications delegate business logic to the client. HTML.next, JavaScript, SVG, Canvas, ECMAScript 7/ES2016, AngularJS and ReactJS are just some terms that describe the contents of the modern web stack. But how does the attack surface look for those? What if there’s not GET parameters anymore that our scanner scan tamper with? What can we do when the server just delivers raw data and the rest is done by the browser? Classic web-pentests are “so nineties” in this realm. And keeping up the pace with progress is getting harder and harder.
But there is hope. The focus of this training is on the offensive and dangerous parts of HTML, JavaScript and related technologies, the nasty and undocumented stuff, dozens of new attack techniques straight from the laboratory of horrors of those maintaining the HTML5 Security Cheatsheet. We’ll learn how to attack any web-application with either unknown legacy features – or the half-baked results coming to your browser from the labs of W3C, WHATWG and the ES2016 mailing lists. Whether you want to attack modern web applications or shiny browser extensions and Chrome Packaged Apps – we have that covered.
Whoever works with or against the security of modern web applications will enjoy and benefit from this workshop. A bit of knowledge on HTML and JavaScript is required, but rookies and rocket scientists will be satisfied equally.
HTML is a living standard. And so is this training. The course material will be provided on-site and via access to a private Github repository so all attendees will be receive updated material even months after the actual training. All attendees are granted perpetual access to updated slides and material.
Target audience
Requirements
Students should :
Hardware/software Requirements
Testimonials
Trainer Biography
Links :
- []
Mon. 2 - 4 October 2017 (09:00 - 17:00) (3-day)