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/

Comments

Popular posts from this blog

Pwning a thin client in less than two minutes

Have you ever encountered a zero client or a thin client? It looks something like this...

If yes, keep reading below, if not, then if you encounter one, you know what you can do if you read below...

The model above is a T520, produced by HP - this model and other similar models are typically employed to support a medium/large VDI (Virtual Desktop Infrastructure) enterprise.

These clients run a Linux-based HP ThinPro OS by default and I had a chance to play with image version T6X44017 in particular, which is fun to play with it, since you can get a root shell in a very short time without knowing any password...

Normally, HP ThinPro OS interface is configured in a kiosk mode, as the concept of a thin/zero client is based on using a thick client to connect to another resource. For this purpose, a standard user does not need to authenticate to the thin client per se and would just need to perform a connection - e.g. VMware Horizon View. The user will eventually authenticate through the c…

UXSS in McAfee Endpoint Security, www.mcafee.com and some extra goodies...

During the HITB2017AMS talk given in Amsterdam with @Steventseeley, I promised that I would have disclosed vulnerabilities affecting a security vendor product other than Trend Micro.

For those who have come to my blog for the first time and are looking at "insecurities" of security vendors, you might be interested as well on how we found 200+ remote code execution vulnerabilities in Trend Micro software...

But this blog post is dedicated to two McAfee products instead: McAfee Endpoint Security and SiteAdvisor Enterprise (now part of McAfee Endpoint Security). For simplicity, I will just refer to McAfee Endpoint Security for the rest of this post.

First let's demonstrate a particular type of XSS, a UXSS, considering that fact that it only affects the McAfee Endpoint Security plugin and does not depend on a particular web site or web application.

There are two different injection points:

-UXSS when user visits a red labelled web site - the payload is rendered in the BlockP…

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 Internet.

Actuall…