Author Topic: Reaver  (Read 1630 times)

0 Members and 2 Guests are viewing this topic.

xC

  • Guest
Reaver
« on: September 08, 2013, 09:49:20 pm »
Was looking around BackTrack and came across Reaver. Very effective method of bruteforcing WPS pins, however it is quite a long and tedious process if you don't know the specified range of the pin (took about 2 hours). I found the main provider around here has the same pin for each modem they deploy, so it was quite easy to recover passwords after that though. I would think it would probably red flag the provider with 10,000 pin attempts but if you are willing to risk it, try it out.

Code: [Select]
Reaver Open Source
Reaver implements a brute force attack against Wifi Protected Setup (WPS) registrar PINs in order to recover WPA/WPA2 passphrases, as described in http://sviehb.files.wordpress.com/2011/12/viehboeck_wps.pdf.

Reaver has been designed to be a robust and practical attack against WPS, and has been tested against a wide variety of access points and WPS implementations.

On average Reaver will recover the target AP's plain text WPA/WPA2 passphrase in 4-10 hours, depending on the AP. In practice, it will generally take half this time to guess the correct WPS pin and recover the passphrase.

https://code.google.com/p/reaver-wps/



Offline vezzy

  • Royal Highness
  • ****
  • Posts: 771
  • Cookies: 172
    • View Profile
Re: Reaver
« Reply #1 on: September 08, 2013, 10:28:57 pm »
I'd be surprised if anyone here doesn't know of Reaver. It's a pretty famous tool in general.

There's a different, more clean implementation of the WPS bruteforce attack known as Bully, which has more options, is refactored and has improved memory performance. The source is here.

Kali may have some issues running it, but it should work fine on other distros.
Quote from: Dippy hippy
Just brushing though. I will be semi active mainly came to find a HQ botnet, like THOR or just any p2p botnet

xC

  • Guest
Re: Reaver
« Reply #2 on: September 08, 2013, 10:48:35 pm »
I never really looked into BackTrack until last night, so I will definitely try out Kali. I just thought it was quite convienient rather than waiting for handshakes with airodump, and aireplay was no help at all. I admit this tool is quite noobish, but I guess it's a last scenario, or first for beginners, or if you're lazy. I will look into Bully as well.
« Last Edit: September 08, 2013, 10:49:51 pm by xC »

Offline vezzy

  • Royal Highness
  • ****
  • Posts: 771
  • Cookies: 172
    • View Profile
Re: Reaver
« Reply #3 on: September 08, 2013, 11:22:59 pm »
I use it pretty often, since I'm a freeloader (I haven't been hooked up to an ISP in about a couple of years or so).

It's a very old vulnerability, one that is very convenient to exploit and an example of user accessibility gone wrong. Some routers don't even let you disable it.

The other option is to make large tables of PMKs with Pyrit and use GPGPU power to achieve insane dictionary attack speeds, but that still depends on how good your wordlist is. You could generate profiled wordlists with something like CUPP, since lots of users use private information for their credentials, but yeah it's all relative.

Reaver hasn't been updated since January 2012, so Bully aims to pick off from where it left. Though I still find myself using Reaver more often.
Quote from: Dippy hippy
Just brushing though. I will be semi active mainly came to find a HQ botnet, like THOR or just any p2p botnet

Offline Snayler

  • Baron
  • ****
  • Posts: 812
  • Cookies: 135
    • View Profile
Re: Reaver
« Reply #4 on: September 09, 2013, 05:12:05 am »
Yeah, reaver is pretty well known. In fact, it was already mentioned multiple times in these forums, not to mention there are already 2 topics exclusively about it:
https://evilzone.org/security-tools/%28wpawpa2%29-reaver
https://evilzone.org/security-tools/reaver-wps
There's a different, more clean implementation of the WPS bruteforce attack known as Bully, which has more options, is refactored and has improved memory performance. The source is here.
Thanks for this! Cookie for you, sir.