Título: Vulnerabilidad "Wi-fi Protected Set-up" Publicado por: PacoA en 31 Diciembre 2011, 09:33 am Han publicado un nuevo tipo de vulnerabilidad que permite sacar la clave de casi todos los routers, aunque la seguridad sea WPA. :rolleyes: Algunos enlaces:
http://es.engadget.com/2011/12/30/herramienta-para-atacar-la-vulnerabilidad-de-conexiones-wifi-con/ http://sviehb.files.wordpress.com/2011/12/viehboeck_wps.pdf http://www.tacnetsol.com/news/2011/12/28/cracking-wifi-protected-setup-with-reaver.html Mis conocimientos de Linux son mínimos. ¿Alguien se atreve a hacer un tuto para usarlo desde un live CD? Un abrazo Título: Re: Vulnerabilidad "Wi-fi Protected Set-up" Publicado por: manolin2 en 31 Diciembre 2011, 10:19 am muy interesante.... intentare ver como hecho a correr la herramienta....saludos..y feliza año
Título: Re: Vulnerabilidad "Wi-fi Protected Set-up" Publicado por: ChimoC en 31 Diciembre 2011, 12:49 pm Buenas:
Eso es lo que os comentaba aqui --> https://foro.elhacker.net/hacking_wireless/esta_pass_es_descifrable_de_alguna_manera-t348468.0.html;msg1701214#msg1701214 Un saludo ChimoC P.D.: IMagino que alguien del foro os comentará los comandos ;D Título: Re: Vulnerabilidad "Wi-fi Protected Set-up" Publicado por: manolin2 en 31 Diciembre 2011, 18:06 pm imaginacion si tenemos.... sobre todo en estas fiestas... :rolleyes: ..ire desmpolvando los libros de BASIC....
Título: Re: Vulnerabilidad "Wi-fi Protected Set-up" Publicado por: ChimoC en 4 Enero 2012, 18:33 pm Buenas:
Módulo --> https://foro.elhacker.net/wireless_en_linux/modulos_wifiway_30-t349461.0.html;msg1702774#msg1702774 Un saludo ChimoC Título: Re: Vulnerabilidad "Wi-fi Protected Set-up" Publicado por: PacoA en 6 Enero 2012, 10:18 am Interesante.
¿algún ejemplo de como se usa? Título: Re: Vulnerabilidad "Wi-fi Protected Set-up" Publicado por: ChimoC en 8 Enero 2012, 00:51 am Buenas:
Acabamos de probar con un router Belkin_N_Wireless y ha tardado 12 horas en dar la clave Habrá que deshabilitar WPS Un saludo ChimoC Usually, the only required arguments to Reaver are the interface name and the BSSID of the target AP: # reaver -i mon0 -b BSSID The channel and SSID (provided that the SSID is not cloaked) of the target AP will be automatically identified by Reaver, unless explicitly specified on the command line: # reaver -i mon0 -b BSSID -c CANAL -e ESSID Since version 1.3, Reaver implements the small DH key optimization as suggested by Stefan which can speed up the attack speed: # reaver -i mon0 -b 00:01:02:03:04:05 --dh-small By default, if the AP switches channels, Reaver will also change its channel accordingly. However, this feature may be disabled by fixing the interface's channel: # reaver -i mon0 -b 00:01:02:03:04:05 --fixed The default receive timeout period is 5 seconds. This timeout period can be set manually if necessary (minimum timeout period is 1 second): # reaver -i mon0 -b 00:01:02:03:04:05 -t 2 The default delay period between pin attempts is 1 second. This value can be increased or decreased to any non-negative integer value. A value of zero means no delay: # reaver -i mon0 -b 00:01:02:03:04:05 -d 0 Some APs will temporarily lock their WPS state, typically for five minutes or less, when "suspicious" activity is detected. By default when a locked state is detected, Reaver will check the state every 315 seconds (5 minutes and 15 seconds) and not continue brute forcing pins until the WPS state is unlocked. This check can be increased or decreased to any non-negative integer value: # reaver -i mon0 -b 00:01:02:03:04:05 --lock-delay=250 For additional output, the verbose option may be provided. Providing the verbose option twice will increase verbosity and display each pin number as it is attempted: # reaver -i mon0 -b 00:01:02:03:04:05 -vv The default timeout period for receiving the M5 and M7 WPS response messages is .1 seconds. This timeout period can be set manually if necessary (max timeout period is 1 second): # reaver -i mon0 -b 00:01:02:03:04:05 -T .5 Some poor WPS implementations will drop a connection on the floor when an invalid pin is supplied instead of responding with a NACK message as the specs dictate. To account for this, if an M5/M7 timeout is reached, it is treated the same as a NACK by default. However, if it is known that the target AP sends NACKS (most do), this feature can be disabled to ensure better reliability. This option is largely useless as Reaver will auto-detect if an AP properly responds with NACKs or not: # reaver -i mon0 -b 00:01:02:03:04:05 --nack While most APs don't care, sending an EAP FAIL message to close out a WPS session is sometimes necessary. By default this feature is disabled, but can be enabled for those APs that need it: # reaver -i mon0 -b 00:01:02:03:04:05 --eap-terminate When 10 consecutive unexpected WPS errors are encountered, a warning message will be displayed. Since this may be a sign that the AP is rate limiting pin attempts or simply being overloaded, a sleep can be put in place that will occur whenever these warning messages appear: # reaver -i mon0 -b 00:01:02:03:04:05 --fail-wait=360 |