March 3, 2007

And now, cracking Bluetooth PIN on FPGA

Months ago , I had a post in Neominds.org blog ( site is now down for some reasons. try google cache ) about FPGA technology and how it's being used by both good/bad guys to own your passwords. As that post is not available now and I've no local copy I'll write a very short brief again.

After few paragraphs about goodness of FPGA & ASIC technology, I explained how and why widely used cipher algorithms are implemented on these technologies. I used OpenCiphers as a sample for software part, and random FPGA boards of PicoComputing as hardware part of scenario. As always some real-world samples was needed, so I posted about FPGA implementation of LM/NTLM released by OpenCiphers, followed by introducing pico-WEPcrack as a working FPGA based WEP cracker. Finally I finished the post with a comparison between FPGA based and PC based of cracking and shocking results, based on my own experiences and provided results in OpenCiphers page.

Now, I'm back to that old topic again, to share more interesting news.While reading about speakers of upcoming ShmooCon, a talk named " Hacking the Airwaves with FPGAs" catched my eyes. Yes it was about some real FPGA work which I've been aware of. At first glance it didn't look much interesting as it should, but hey there were some brand news in that talk : Bluetooth. those few lines were enough for me to recall previous excellent releases of OpenCiphers. So I revisited their site and, guess what ? They had two new finished projects, ready for FPGA fans. these additions were for WPA and Bluetooth PIN cracking.
WPA case was not so interesting for me, as I choose this technique for last try. I'm sure you know how to extract WPA keys out of air by packet-injection in few minutes and as there are many resources for this out there, I'm not going to make a clone ! so keep reading. anyway if you're too much excited in cracking WPA on FPGA, I can redirect you to latest versions of coWPAtty .

OpenCiphers Bluetooth PIN however, looks great again. If you've been an active member of community you already know about 23C3 , and if you've already missed this talk I must say that you really should not check it anymore, because you do NOT deserve it.
The talk provided information on latest attacks against Bluetooth technology, and how to capture Bluetooth traffic, extract PIN out of dumped captures and finally crack the PIN using offline attacks , for later use in a targeted attack against victim's bluetooth device. And these all become possible because of some implementation bugs, which is very common in most of bluetooth related vendors. Of course some tools are required for that, so BTcrack was released among the talk. Detailed how-to was also provided, but I prefer to withheld it. If you're kind of person who should know this, then you probably know where to look for this how-to ;)

Hey we lost the subject ! I was talking about cracking speed...
As you've checked presentation, you'll see that BTcrack's top speed is something around 185.000 keys per second. it means cracking a 4 _digit_ PIN in less than second , and about 20 minutes of brute-forcing for a 6 _digit_ long PIN. Note that I'm saying 4 digit keys. Although digits are the only options for many cases ( like mobile phones) but a PIN is NOT limited to digits. so above results may not be useful in a real-world attack, if victim use a PIN consisted of digits and alphabets. and victim will not going to wait for you whole of the day, to crack his PIN.
Here the magical speed of FPGA implementations comes handy , and once aging shocking for unfamiliar eyes. OpenCipher's implementation of PIN-crack, based on a single Pico's FPGA board have increased that speed to 10 millions keys per second !

Now imagine one of those portable FPGA solutions, attached to your laptop, ready to own any target in matter of seconds, no matter how smart s/he is in choosing the PIN ;)

February 21, 2007

Nmap Secrets...

Are you a big fan of Nmap like me ? If so keep reading else blogID =+ 1 .
If you`re a real Nmap kind of guy you've probably checked the most complete released material about Nmap named as "Secrets of Network Cartography". The book contained many interesting and useful tips on how to use Nmap more professionally. Even if you belive yourself as a expert give it a try. But wait, don`t go for old version anymore if you've missed it. new release of the book + some more gifts are in way and you can upgrade your knowledge about Nmap with brand new materials which will be published in less than 4 hours ( At the time of writing this ). Upcoming event will be a free webinar which will announce some new features of Nmap and some quick tips on using it. This webinar have also a gift for you. I`m not going to leak it of course :p . If you really enjoy Nmap related gifts, join the webinar and at the end you'll be thankful of me announcing it to you ;)

February 20, 2007

Snort Night-matter 2007 !

We all remember the bright "Yellow" color of SANS threat-meter while every one was coding his own version of exploit for CVE-2005-3252 (AKA Back-Orifice Pre-Processor overflow) to blindly target running Snort and SourceFire appliances. It was really kind of cool and at the same time dangerous flaw which has been used to compromise MANY targeted and random victims. Although Snort team was fast enough to release fixed version of snort, but as always tons of administrators left the upgrade process for next working week and guess what? Most of them had a crash-dump of snort, ready for analyze ! This was the major flaw of Snort in 2005.

Second major flaw in snort announced as CVE-2006-6931 (AKA Rule Matching Backtrack DoS) when three researchers from University of Wisconsin-Madison released a paper describing how it's possible to take down most of current brands in IDS technology with which a technique called "Backtracking Algorithmic Complexity Attacks". Snort was one of vulnerable brands, could be DoSed more easily than some other brands , by sending a single crafted packet. 2006 finished without any other major flaw in snort getting publicly announced ( Oh thanks God!!! ).

Guess what? right, another major flaw in snort for 2007 making many 1337 c0d3rs busy out there, writing another remote for snort. Once again ISS (Neel Mehta) is credited for the flaw, which seems has been result of his previous research on Snort back in 2006, getting published in 2007. CVE-2006-5276 is placeholder of mentioned flaw affecting "DCE/RPC PreProcessor" of Snort 2.6.1 / 2.6.1.1 / 2.6.1.2 / 2.7.0 BETA1 . I just wonder why ISS and Snort (SourceFire) waited that long time to publish this one. Maybe enough snorts have not been owned last time... ;)
I'm not sure when we will see first public PoC but black-market has already released new toys in markets. Keep this one serious and update your Snort/Sourcefire ASAP as this flaw can be reliably exploited and it's not hard to discover where the flaw can be triggered. SANS handler J.Esler posted useful dairy describing quick workaround for the flaw. Don`t forget to take a look at his post.

[Updated on February 23 ]
Seems first public PoC is out . The bad news for kids is that it's a DoS code . So far three working exploits have been released commercially by different consultancy companies. The ones I'm aware of, can target SourceFire appliance and snort running on SUSE,Debian,RHEL3/4 and FreeBSD.