Code injection into web apps is not a new phenomenon. It's been a constant on the web even longer than IE6. It's been around since the very first .cgi scripts were chmod +x'ed, resulting in a chroot 0wn3d.

Code injection is mainly brought about by web programmers not making sure that the input received from users is what was expected.

This talk, will concentrate mainly on XSS injection, but will also talk a little about SQLi and CSRF. We'll go over the kinds of programming mistakes that result in code injection, and how to change your mindset to prevent these issues.


Comments are closed.

Rated 5

Anonymous at 20:38 on 1 Mar 2012

What does the slide #2 mean (IWYGWYETG)?

Apart from it, pretty nifty tricks on XSS which every form designer should be aware about!

I recently found someone who'd done zero validations on a production site form, and it had been like that for 5 months. Thankfully enough, probably hackers were dumb enough to realise that maybe XSS exploit checks were in place, and hence they didn't do anything nasty. Phew!

IWYGWYETG is the title of the post (Is What You Get What You Expect To Get)