- [DeepSec 2015]50 Shades of WAF
- [DeepSec 2015] File Format Fuzzing in Android – Giving a Stagefright to the Android Installer
- [DeepSec 2015]How to Break XML Encryption – Automatically
- [DeepSec 2015] Hacking Cookies in Modern Web Applications and Browsers
- [DeepSec 2015] Can societies manage the SIGINT monster?
- [LHS Microcast] DeepSec 2015
- [LHS Microcast] Interview w/ Jen Ellis
- Taking out the Eurotrash
- All good things must come to an end
- [DeepSec 2014] Advanced Powershell Threat: Lethal Client Side Attacks using Powershell
The contents of this personal blog are solely my own opinions and comments, as such they do not reflect the opinions of my employer(s) past, present or future. No legal liability is accepted for anything you do, think, or consider fact as the basis of articles and links posted on this blog.
"Three to one...two...one...probability factor of one to one...we have normality, I repeat we have normality. Anything you still can’t cope with is therefore your own problem."
Note: A large portion of content I post on my blog comes from "live blogging" of security conferences. These posts are in notes form and are written live during a talk. As such errors and emissions are expected. I'm only human after all!
wow Chris, nice work!
Thanks… It’s an interesting find, but certainly not major issue. When it comes down to it, it exposes a reflective XSS flaw, and maybe some data stored using the Typo3 XOR functions (also based on the EncKey). Still, no world ending DNS vuln here.
It’s just nice to give something back (to an open source project) and make something more secure instead of constantly breaking things 😉 That and I really enjoyed reversing the process and writing the tool(s) (my first python script, and it actually works… who’d have thought).
Not sure what’s next… maybe I’ll keep looking at Typo3 for a while 😉
Congrats again on this, Chris!