Skip to main content

Hack In the Box 2012 Amsterdam - Recap


I have promised I would have something written about my Hack In the Box 2012 Amsterdam conference experience.

First thing, it was one of the best security conference I have ever been. Big props to Dhillon (@l33tdawg) and the HITB crew for organising such event. I have been organising conferences in the past (OWASP NZ Day 2009 and 2010) and I know something about what happens in the background.

The conference venue was awesome, a pimping five stars hotel ;-) and again need to thank the crew for the wise choice. Bad thing is that I checked out with my wallet "lighter" than usual, after having dinners at the Japanese restaurants and trying all the amenities of the fitness center.

My talk (pdf || slideshare) was on the first day along with two other media interviews with Mirko Zorz (@helpnetsecurity) of Help Net Security and Edward Kovacs (@EduardKovacs) of Softpedia.

Both interviews went pretty well and they will be published soon. Unfortunately, I wasn't able to see many talks during the first day. However, I have found interesting and entertaining reading the slides of the following presentations:

- Killing a bounty program, Twice. - Itzhak (Zuk) Avraham (@ihackbanme) and Nir Goldshlager (@Nirgoldshlager)
- One flew over the cuckoo's nest - Claudio Guarnieri (@botherder).

On the second day, I enjoyed Nicolas Gregoire (@Agarri_FR)'s talk about "Attacking XML processing". His demo part was very cool and it gave me some new ideas. Attended Steven Seeley (@net__ninja) talk about Ghost In the Windows 7 Allocator, from which I learnt several things I didn't know about Windows heap. Also attended some talks which are unrelated to my current area of research and which resulted to give me some collateral ideas:

- CXML VXML Auditing for IVR Pentesters - Rahul Sasi - @fb1h2s
- Automatically Searching for Vulnerabilities - Nikita Tarakanov - @NTarakanov

All the slides/material of HITB2012AMS material can be found here: http://conference.hitb.org/hitbsecconf2012ams/materials/

During the conference, I have spent some great time going around Amsterdam with with  @net__ninja.

Also met with Peter Van Eeckhoutte (@corelanc0d3r) from the Corelan team, who I need to thank for the very cool article he wrote about my talk. I also had few beers with Fred Raynal (@fredraynal) and met new friends, such as Claudio Guarnieri (@botherder) and Marco Balduzzi (@embyte).

After my presentation, I have met with Arthur Gerkis (@ax330d) and Christian Holler (@mozdeco) - they both gave me some new ideas for fuzzing browsers, which I expect to adopt and try in the next few months.

Hopefully, I will have a chance to get an invite to the HITB KUL next year ;-). I will definitely re-submit next year to HITB2013AMS if I got new things to share.

Finally, all the bugs, demo and exploits which were shown during my preso will be released sometime soon so please keep watching this space or follow my tweets if you are interested ;-).

Other blog posts about HITB2012AMS which you might find relevant:

https://www.corelan.be/index.php/category/security/cons-seminars/
http://blog.rootshell.be/2012/05/24/hitb-amsterdam-wrap-up-day-1/
http://blog.rootshell.be/2012/05/25/hitb-amsterdam-wrap-up-day-2/

Labels:

Comments

Post a Comment

Popular posts from this blog

TrendMicro ScanMail for Microsoft Exchange (SMEX) predictable session token - CVE-2015-3326

It's time for another advisory ( CVE-2015-3326 ), a simple one, for a vulnerability which can be found quickly and trivially. For those of you who just want to give a glance at the post, I suggest to directly watch the picture which says it all! The following vulnerability was discovered on TrendMicro SMEX (ScanMail for Microsoft Exchange) 10 SP2 but it affects other versions as well. While surfing the SMEX web administrative interface using a web proxy, I have noticed something in the HTTP request - the session token itself and its format, a number. After observing a significant number of logins, the session token was always represented with an number composed of minimum 4 digits and maximum 5 digits, as shown in the screen shot below:   Although the observed session tokens were never generated sequentially, the lack of a cryptographically strong PRNG for the session identifier, allows a malicious user to trivially guess the token. This attack can be easily automated.
1 comment
Read more

Alcatel Lucent Omnivista or: How I learned GIOP and gained Unauthenticated Remote Code Execution (CVE-2016-9796)

It is time for another advisory or better a blog post about Alcatel Lucent Omnivista  and its vulnerabilities. Omnivista is a central management network tool and it is typically used in medium/large organisation with a complex VoIP/SIP infrastructure. Interestingly enough, this software belongs to the niche of "undownloadable" software and it requires a license to work as well. My "luck" came during an engagement where it was already installed and this post documents one of the many 0days discovered during such audit. The reasons why I wanted to dedicate a single blog post on this vulnerability are several. First, remote code execution (RCE) is always a sweet bug to show. Second, I strongly believe that documenting vulnerabilities in applications using old protocols and standards, respectively GIOP and CORBA, can be beneficial for the infosec community, since no many examples of vulnerabilities in such applications are available or published on the Interne
6 comments
Read more

Microsoft .NET MVC ReDoS (Denial of Service) Vulnerability - CVE-2015-2526 (MS15-101)

Microsoft released a security bulletin ( MS15-101 ) describing a .NET MVC Denial of Service vulnerability ( CVE-2015-2526 ) that I reported back in April. This blog post analyses the vulnerability in details, starting from the theory and then providing a PoC exploit against a MVC web application developed with Visual Studio 2013. For those of you who want to see the bug, you can directly skip to the last part of this post or watch the video directly... ;-) A bit of theory The .NET framework (4.5 tested version) uses backtracking regular expression matcher when performing a match against an expression. Backtracking is based on the NFA (non-deterministic finite automata) algorithm engine which is designed to validate all input states. By providing an “evil” regex expression – an expression for which the engine can be forced to calculate an exponential number of states - it is possible to force the engine to calculate an exponential number of states, leading to a condition defined su
3 comments
Read more