KRACK attack ~ New WPA2 Attack!

glitch956 · 10-17-2017, 08:59 PM

phyrrus9 · 10-17-2017, 09:02 PM

(10-17-2017, 08:59 PM)glitch956 Wrote: https://pastebin.com/aZyyS16w

Oh god....I don't think I can take anything seriously that's written in mixed python and english...

S3xySmurf · 10-17-2017, 09:40 PM

(10-17-2017, 09:02 PM)phyrrus9 Wrote:
(10-17-2017, 08:59 PM)glitch956 Wrote: https://pastebin.com/aZyyS16w

Oh god....I don't think I can take anything seriously that's written in mixed python and english...

They did say that the scripts needed cleaning up a lot but I'm unsure if this is actually legit, I can't see these guys using pastebin to share the code when they have their own Github and website.

phyrrus9 · 10-17-2017, 09:42 PM

(10-17-2017, 09:40 PM)S3xySmurf Wrote:
(10-17-2017, 09:02 PM)phyrrus9 Wrote:
(10-17-2017, 08:59 PM)glitch956 Wrote: https://pastebin.com/aZyyS16w

Oh god....I don't think I can take anything seriously that's written in mixed python and english...

They did say that the scripts needed cleaning up a lot but I'm unsure if this is actually legit, I can't see these guys using pastebin to share the code when they have their own Github and website.

This looks like someone just spent the time reading through the whitepaper and slapped something together. I'll probably get around to playing with it when im at work tonight and I can get paid for it

Synthx · 10-17-2017, 10:02 PM

I watched the Hak5 ThreatWire video about it, this seems very interesting, and I actually didn't know that WPA2 failed requests sometimes like that. Hope to see this patched quickly for the sake of many people's privacy!

Edit: Here's the video...

phyrrus9 · 10-17-2017, 10:05 PM

(10-17-2017, 10:02 PM)$ynthx Wrote: I watched the Hak5 ThreatWire video about it, this seems very interesting, and I actually didn't know that WPA2 failed requests sometimes like that. Hope to see this patched quickly for the sake of many people's privacy!

Edit: Here's the video...

The resubmission thing actually comes down to an old 802.1x spec, which specifies that packets should be retransmitted if timeout or lost. It was carried into WPA, the issue is they reused the nonce string, probably out of laziness.

S3xySmurf · 10-18-2017, 01:36 AM

(10-17-2017, 09:42 PM)phyrrus9 Wrote:
(10-17-2017, 09:40 PM)S3xySmurf Wrote:
(10-17-2017, 09:02 PM)phyrrus9 Wrote: Oh god....I don't think I can take anything seriously that's written in mixed python and english...

They did say that the scripts needed cleaning up a lot but I'm unsure if this is actually legit, I can't see these guys using pastebin to share the code when they have their own Github and website.

This looks like someone just spent the time reading through the whitepaper and slapped something together. I'll probably get around to playing with it when im at work tonight and I can get paid for it

Did you manage to get this working as I've tested but it booted me off my network when running the script and arping, I killed wpa_supplicant and restarted the network-manager service and everything seems fine but I still get the same errors ?

Spoiler:Code:
Successfully initialized wpa_supplicant
Could not read interface p2p-dev-wlp5s0 flags: No such device
nl80211: Could not set interface 'p2p-dev-wlp5s0' UP
nl80211: deinit ifname=p2p-dev-wlp5s0 disabled_11b_rates=0
p2p-dev-wlp5s0: Failed to initialize driver interface
P2P: Failed to enable P2P Device interface
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
[01:30:37] Detected normal association frame
wlp5s0: No network configuration found for the current AP
wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
[01:30:56] Detected normal association frame
wlp5s0: No network configuration found for the current AP
wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
[01:31:15] Detected normal association frame
wlp5s0: No network configuration found for the current AP
wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN

The errors I'm seeing are a bug in wpa_supplicant.

phyrrus9 · 10-18-2017, 02:47 AM

(10-18-2017, 01:36 AM)S3xySmurf Wrote:
(10-17-2017, 09:42 PM)phyrrus9 Wrote:
(10-17-2017, 09:40 PM)S3xySmurf Wrote: They did say that the scripts needed cleaning up a lot but I'm unsure if this is actually legit, I can't see these guys using pastebin to share the code when they have their own Github and website.

This looks like someone just spent the time reading through the whitepaper and slapped something together. I'll probably get around to playing with it when im at work tonight and I can get paid for it

Did you manage to get this working as I've tested but it booted me off my network when running the script and arping, I killed wpa_supplicant and restarted the network-manager service and everything seems fine but I still get the same errors ?

Spoiler:
Code:
Successfully initialized wpa_supplicant Could not read interface p2p-dev-wlp5s0 flags: No such device nl80211: Could not set interface 'p2p-dev-wlp5s0' UP nl80211: deinit ifname=p2p-dev-wlp5s0 disabled_11b_rates=0 p2p-dev-wlp5s0: Failed to initialize driver interface P2P: Failed to enable P2P Device interface wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN [01:30:37] Detected normal association frame wlp5s0: No network configuration found for the current AP wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1 wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN [01:30:56] Detected normal association frame wlp5s0: No network configuration found for the current AP wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1 wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN [01:31:15] Detected normal association frame wlp5s0: No network configuration found for the current AP wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1 wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN

The errors I'm seeing are a bug in wpa_supplicant.

1. you need to run as root
2. need to make sure you're using the right interface
3. if you're using a mainstream linux "flavor", you're gonna have a bad time, they tend to have wl daemons everywhere to make them user friendly

S3xySmurf · 10-18-2017, 03:58 AM

(10-18-2017, 02:47 AM)phyrrus9 Wrote:
(10-18-2017, 01:36 AM)S3xySmurf Wrote:
(10-17-2017, 09:42 PM)phyrrus9 Wrote: This looks like someone just spent the time reading through the whitepaper and slapped something together. I'll probably get around to playing with it when im at work tonight and I can get paid for it

Did you manage to get this working as I've tested but it booted me off my network when running the script and arping, I killed wpa_supplicant and restarted the network-manager service and everything seems fine but I still get the same errors ?

Spoiler:

Code:
Successfully initialized wpa_supplicant Could not read interface p2p-dev-wlp5s0 flags: No such device nl80211: Could not set interface 'p2p-dev-wlp5s0' UP nl80211: deinit ifname=p2p-dev-wlp5s0 disabled_11b_rates=0 p2p-dev-wlp5s0: Failed to initialize driver interface P2P: Failed to enable P2P Device interface wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN [01:30:37] Detected normal association frame wlp5s0: No network configuration found for the current AP wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1 wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN [01:30:56] Detected normal association frame wlp5s0: No network configuration found for the current AP wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1 wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN [01:31:15] Detected normal association frame wlp5s0: No network configuration found for the current AP wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1 wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN

The errors I'm seeing are a bug in wpa_supplicant.

1. you need to run as root
2. need to make sure you're using the right interface
3. if you're using a mainstream linux "flavor", you're gonna have a bad time, they tend to have wl daemons everywhere to make them user friendly

I thought it was the distro I'm using that was causing the problem, I'll try Kali, although this script also killed my Alfa Awus036H just turns off when selecting that as the WiFi device.

phyrrus9 · 10-18-2017, 04:18 AM

(10-18-2017, 03:58 AM)S3xySmurf Wrote:
(10-18-2017, 02:47 AM)phyrrus9 Wrote:
(10-18-2017, 01:36 AM)S3xySmurf Wrote: Did you manage to get this working as I've tested but it booted me off my network when running the script and arping, I killed wpa_supplicant and restarted the network-manager service and everything seems fine but I still get the same errors ?

Spoiler:

Code:
Successfully initialized wpa_supplicant Could not read interface p2p-dev-wlp5s0 flags: No such device nl80211: Could not set interface 'p2p-dev-wlp5s0' UP nl80211: deinit ifname=p2p-dev-wlp5s0 disabled_11b_rates=0 p2p-dev-wlp5s0: Failed to initialize driver interface P2P: Failed to enable P2P Device interface wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN [01:30:37] Detected normal association frame wlp5s0: No network configuration found for the current AP wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1 wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN [01:30:56] Detected normal association frame wlp5s0: No network configuration found for the current AP wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1 wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN [01:31:15] Detected normal association frame wlp5s0: No network configuration found for the current AP wlp5s0: CTRL-EVENT-DISCONNECTED bssid=80:37:73:37:64:20 reason=3 locally_generated=1 wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD wlp5s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN

The errors I'm seeing are a bug in wpa_supplicant.

1. you need to run as root
2. need to make sure you're using the right interface
3. if you're using a mainstream linux "flavor", you're gonna have a bad time, they tend to have wl daemons everywhere to make them user friendly

I thought it was the distro I'm using that was causing the problem, I'll try Kali, although this script also killed my Alfa Awus036H just turns off when selecting that as the WiFi device.

Kali is another one of those "flavors" that's been made too user friendly and too hacker unfriendly. You could run this on gentoo, arch, or even debian (if you have an install without some fancy desktop environment)

KRACK attack ~ New WPA2 Attack!
Author Message