Tuesday, October 17th 2017

Taking Hold of Your Signal - Critical Flaw Discovered in WPA2 Wi-Fi Security

Researchers have recently discovered a critical flaw that affects all WPA2 protected Wi-Fi devices. This can't be remedied solely by user intervention, or password changes, or even by the usage of HTTPS website; this is a flaw with the core of WPA's protection scheme, and means that an attacker could intercept every single traffic data point that your device sends over Wi-Fi, including passwords, credit card details, images - the whole treasure trove. Adding insult to injury, it's even possible for attackers using this method to inject malware into your devices. The new attack method - dubbed KRACK for Key Reinstallation Attack - basically forces your device's encryption code to default to a known, plain-text all-zero decryption key, which is trivial for hackers to reuse.

Adding to the paranoia, this is basically a device and software-agnostic attack - it's effective against devices running Android, Linux, and OpenBSD, and to a lesser extent macOS and Windows, as well as MediaTek Linksys, and other types of devices. HTTPS isn't the best solution either, simply because some website's implementation of it isn't the best, and there are scripts (such as SSLScript) that can force a website to downgrade its connection to a simple HTTP link - which can then be infiltrated by the attacker.
Asked whether this signaled the need for a reworked security protocol - ala WPA3 - , one of the principal researches responsible for bringing this problem to light answered that "No, luckily [WPA2] implementations can be patched in a backwards-compatible manner. This means a patched client can still communicate with an unpatched access point, and vice versa. In other words, a patched client or access points sends exactly the same handshake messages as before, and at exactly the same moments in time. However, the security updates will assure a key is only installed once, preventing our attacks. So again, update all your devices once security updates are available."

This is a video where the researchers show how fast it is to hack an Android device through this flaw:


The US-CERT (United States Computer Emergency Readiness Team) has already acknowledged the issue, alerting companies and state-based services to the flaw. Follow the sources below for the researchers' KRACK attack page, and the white paper, on the second link, which may shed some more light on this issue. In the meantime, be sure to check for device updates for all your internet access points - which if you hadn't noticed already, is pretty much everything around you.
Sources: KRACK Attacks, KRACK Attack Paper, US CERT, Ars Technica
Add your own comment

43 Comments on Taking Hold of Your Signal - Critical Flaw Discovered in WPA2 Wi-Fi Security

#26
zlobby
RejZoRThe WiFi encryption is independent of HTTPS going through it. The amount of critical webpages even allowing non encrypted traffic is becoming ridiculously small, so that trick to force it to downgrade back to normal HTTP is super unlikely. So, realistic chances for someone "hacking" you this way efficiently are incredibly small. It would require a very targeted attack for which home computers are frankly not worth it.

This again proves AES 256 is still very much secure, it's the handshake that was intercepted in this case. Technically, if they fix the handshake thingie, the problem is solved until someone else figures out other method.
Many other protocols running wild in the home network has no built-in security. They rely on the security of the underlying layers like WiFi, which in this case is compromised.
Posted on Reply
#27
moproblems99
Prima.VeraGreat job showing all the details of the hack, so making it so popular that even an average Joe can now hack WPA2 Networks....
Actually, this was reviewed and disclosed back in May.
Posted on Reply
#28
zlobby
moproblems99Actually, this was reviewed and disclosed back in May.
And I was sleeping so much better before, knowing only l33t hax0rz could pen my networks. Now, everyone can!
Can they?
Posted on Reply
#29
trparky
bugGood luck getting patches for Android phones, even the discontinued Windows Phone may get speedier patches :(
And that's the reason why I dumped that steaming pile of crap that is Android and went with the Apple iPhone instead. Guaranteed software updates for at least four years no matter where you are in the world or what carrier you have. You get the same iOS updates the same day everyone across the world gets it.
R-T-BThank goodness for unlocked bootloaders and LineageOS.
Yeah, if you're lucky your device has an unlocked bootloader like most Google branded devices have but if you have either a Samsung, LG, or HTC device... um, that's not the case.
Posted on Reply
#30
Prima.Vera
Does this apply to WPA-2 Enterprise which uses certificates?
Posted on Reply
#31
trparky
Prima.VeraDoes this apply to WPA-2 Enterprise which uses certificates?
From what I read, yes.
Posted on Reply
#32
Chaitanya
transpondsterAP don't need upgrades, it's client side bug
Better explanation and yep looks like its clients that need updating.
Posted on Reply
#33
lexluthermiester
ChaitanyaDon't think most consumer devices will get update for this flaw. Mostly enterprise grade wifi AP will updated in next few weeks.
Not all consumer/enterprise devices have the flaw as this vulnerability requires that the serving device be forced to accept an older, previously used key. Not all wifi serving devices[routers and AP's] do this and not all client devices[PC's, tablet's and phones] do it either. While this flaw exists in the WPA/WPA2 protocol, each device can be configured independently to use, or not use, individual features of the protocol. What is and is not vulnerable is going greatly depend on how each device is configured to implement the key renewal procedure. Additionally, because there are different ways to renew a key based on how it was issued, exploiting a device is doing to require that the attacker know what they are doing. "Script-kiddies" and amateurs are not going to be able to pull it off.
bugBut why the AP? Every WiFi enabled device does the handshake and should be vulnerable, if I understood what this flaw does.
As stated above, it depends on how a device handles the key renewal. Handshaking is only one part of a very complex procedure.
bugAnd here's our answer: arstechnica.com/information-technology/2017/10/how-the-krack-attack-destroys-nearly-all-wi-fi-security/
That article is misunderstanding and misinterpreting the known facts and thus comes to a conclusion that is as flawed as the protocol they are discussing. Again, how the WPA protocol is implemented will define what device is and is not vulnerable. Not all devices can be exploited and as such not all devices need updating.
bugGood luck getting patches for Android phones, even the discontinued Windows Phone may get speedier patches :(
Most Windows phones, ironically, are already patched due to the discovery of a related vulnerability. Additionally Android phones with 4.4.4 or earlier are NOT vulnerable. 5.0 is. 5.1 is not. 6.0.x is. 7.0.x is. 7.1.x is not. Some Linux distro's are already patched as well. Hell, even Windows Xp is ok.

The devil is in the details and while this is serious problem not everyone should panic. Wifi serving devices[routers and AP's] are going to be the most important type of devices to patch. Once that group is patched the flaw will be mitigated because the serving device controls the key exchange and renewal. While a client device can still be exploited, once patched a serving device will reject key streams from a tampered device, thus forcing a disconnection and reinitialization which forces a complete key reset. The effected device will then try to reconnect and the serving device will create a new key that is unknown to the attacker.

It should be noted that this vulnerability is completely unrelated to the known problems with router password capturing due to packet sniffing and MAC address spoofing vulnerabilities inherent within the WPA/WPA2 protocols. However, those can only be used to gain access to a wifi connection and steal internet. They can not be used to view the data traffic coming in and out of the network itself. That is what makes "KRACK" so scary.
Posted on Reply
#34
bug
Thanks for your input. In the end, it is a client problem, but luckily not every client is automatically vulnerable. That is actually a big relief.
Posted on Reply
#35
Megan
As much as I have read, the only fix is to patch and the providers or companies need to release the patch for all the vulnerable devices but this postsuggests that using a VPN can also help if the provider whose device you own has not yet released the patch or ain't releasing it. Does it makes sense?
Posted on Reply
#36
bug
MeganAs much as I have read, the only fix is to patch and the providers or companies need to release the patch for all the vulnerable devices but this postsuggests that using a VPN can also help if the provider whose device you own has not yet released the patch or ain't releasing it. Does it makes sense?
If you absolutely need to get something done and you're not sure of your equipment, a VPN will help. But VPNs are slow, nobody wants to run through a VPN 24/7.
Posted on Reply
#37
arbiter
bugIf you absolutely need to get something done and you're not sure of your equipment, a VPN will help. But VPNs are slow, nobody wants to run through a VPN 24/7.
Depends on the VPN provider you get a decent one they will be just as fast as if you are not using it.
Posted on Reply
#38
kn00tcn
trparkyYeah, if you're lucky your device has an unlocked bootloader like most Google branded devices have but if you have either a Samsung, LG, or HTC device... um, that's not the case.
why are you false?

wiki.lineageos.org/devices/ so much samsung, lg, htc...

stats.lineageos.org/ so much non-google used, the first to appear is TENTH place
lexluthermiesterMost Windows phones, ironically, are already patched due to the discovery of a related vulnerability. Additionally Android phones with 4.4.4 or earlier are NOT vulnerable. 5.0 is. 5.1 is not. 6.0.x is. 7.0.x is. 7.1.x is not. Some Linux distro's are already patched as well.
review.lineageos.org/#/q/topic:krack-n+(status:merged) but there are multiple, if 7.1 is not affected, why did lineage put the fixes into 7.1? fedora didnt patch until the day of or day after
Posted on Reply
#39
lexluthermiester
kn00tcnreview.lineageos.org/#/q/topic:krack-n+(status:merged) but there are multiple, if 7.1 is not affected, why did lineage put the fixes into 7.1? fedora didnt patch until the day of or day after
That lineageOS link doesn't open, however, and I couldn't find a reference in their current posts. Not saying that it's not there, just didn't find it myself. However, they may have proactively patched existing code with known fixes just in case. As for Fedora, as I stated, some Linux distro's are already patched. This directly implied that not all have been and that, obviously, some will need patching. Fedora seems to have needed it and did so. How does that confuse you?
Posted on Reply
#40
kn00tcn
lexluthermiesterThat lineageOS link doesn't open, however, and I couldn't find a reference in their current posts. Not saying that it's not there, just didn't find it myself. However, they may have proactively patched existing code with known fixes just in case. As for Fedora, as I stated, some Linux distro's are already patched. This directly implied that not all have been and that, obviously, some will need patching. Fedora seems to have needed it and did so. How does that confuse you?
link still works, or you could try an individual patch review.lineageos.org/#/c/193406/ then click the 'krak-n' topic

what i meant by fedora was that a distro known for being decently updated & secure didnt get the patch until after the huge disclosure

official google roms for pixel/nexus also didnt get it until november according to news articles, apple didnt until a similar delay with 11.1 instead of 11.0.3 or something

just seems odd for MS to have a fix months in advance, while at the same time the issue is a complex series of bugs left open after disclosure & only openbsd patched early
Posted on Reply
#41
lexluthermiester
kn00tcnlink still works, or you could try an individual patch review.lineageos.org/#/c/193406/ then click the 'krak-n' topic

what i meant by fedora was that a distro known for being decently updated & secure didnt get the patch until after the huge disclosure

official google roms for pixel/nexus also didnt get it until november according to news articles, apple didnt until a similar delay with 11.1 instead of 11.0.3 or something

just seems odd for MS to have a fix months in advance, while at the same time the issue is a complex series of bugs left open after disclosure & only openbsd patched early
I see what your saying now. And agreed, that seems a bit weird, even a tad iffy. Here at my home we just shut off the wifi until verified patches are available. It's made things a little interesting. After telling most of my neighbors about all of this, many of them have done the same.
Posted on Reply
#42
kn00tcn
lexluthermiesterI see what your saying now. And agreed, that seems a bit weird, even a tad iffy. Here at my home we just shut off the wifi until verified patches are available. It's made things a little interesting. After telling most of my neighbors about all of this, many of them have done the same.
https was supposedly fine, so it's as if you used open wifi or some restaurant with a shared key

boy it could have been much worse if it was a major protocol issue like WEP or if clients couldnt fix it
Posted on Reply
#43
micropage7
R0H1TI bet the NSA was sitting on this for a while, who knows what exploits they still have.
maybe, and theres no system that 100% safe or bug free
Posted on Reply
Add your own comment
Dec 22nd, 2024 08:07 EST change timezone

New Forum Posts

Popular Reviews

Controversial News Posts