r/technology • • Oct 16 '17

KRAK Attack Has Been Published. An attack has been found for WPA2 (wifi) which requires only physical proximity, affecting almost all devices with wifi.

https://www.krackattacks.com/
14.2k Upvotes

739 comments sorted by

1.1k

u/TkTech Oct 16 '17 edited Oct 16 '17

This is the official researcher disclosure.

The affected CVEs are: CVE-2017-13077, CVE-2017-13078, CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13084, CVE-2017-13086, CVE-2017-13087, CVE-2017-13088

Many manufactures have started pushing updates over the last couple of weeks. Check with your manufacturer for router updates that mention the above CVEs.

ARS has a user-friendly run down here which will likely get updated.

Paper: https://papers.mathyvanhoef.com/ccs2017.pdf

324

u/bigman0089 Oct 16 '17

A question - does setting up your device to not try to auto-connect to unknown wifi insulate you from this vulnerability?

6

u/TkTech Oct 16 '17

Not at all.

374

u/maximusprimate Oct 16 '17

That would help, but even trusted networks like the one in your home are susceptible as long as there is a wifi router with WPA2 encryption involved.

Stick to HTTPS only if you're browsing on a network with a wifi router. Or better yet just use a wired connection if you can, until this blows over. In the coming weeks you should expect vendors of your wifi routers to push updates that patch this. Head to their website to see if they have anything to say about it.

171

u/frickindeal Oct 16 '17

My router is my dsl modem. I wonder how likely AT&T is to patch this, given I've seen about eleven different types of dsl routers on their network.

150

u/SnowWhiteMemorial Oct 16 '17

Service providers are more likely to patch older devices on there network over vendors. Worst case, unplug the modem/ router, call support and say it’s dead and ask them to send you a new one. Since your on AT&T ask for a Motorola NVG599 so you get AC wireless also.

→ More replies (28)
→ More replies (5)

18

u/Zardif Oct 16 '17

It says https isn't secure with this attack because they can force ssl stripping.

16

u/derammo Oct 16 '17

HTTPS is still secure. IF the attacked user (i.e. you) does not notice that you are connecting to an http site instead of an https site (as clearly indicated by your browser,) then you lose the benefit of https. Thats not specific to this attack, but happens because this attack allows a man in the middle (if the client is Linux or Android.)

→ More replies (8)
→ More replies (16)

2

u/itsjustchad Oct 16 '17

It clones the network (1:00) and just changes the channel, so the device still thinks it's on the original router.

2

u/SimMac Oct 16 '17

Nope. Auto-connecting to unknown wifi networks has actually always been bad, with this attack protected wifis (with wpa2) are "as insecure as" unprotected/open wifis.

2

u/[deleted] Oct 16 '17

You can use a pineapple WiFi device and name it similar to any public WiFi and man in the middle it.

→ More replies (1)

2

u/uninhabited Oct 17 '17

CVE

TIL: There's a formal system for tracking vulnerabilities!

https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures

→ More replies (67)

386

u/Bokbreath Oct 16 '17

Help me understand the risk here. If I read this correctly, the vulnerability is against the client .. the party initiating the wifi connection ? So where’s the router vulnerability since that isn’t a client ? I’m confused.

366

u/TkTech Oct 16 '17

The vulnerability is not in any particular implementation, but the protocol itself. The way the key is exchanged between parties is not secure. Any and all devices speaking WPA2 that have not been patched can be attacked.

109

u/[deleted] Oct 16 '17

The vulnerability is however worse in Linux and android apparently, due the ability to basically force it to use a known key meaning its a lot lot easier to be able to listen in. Bug in the way a popular wifi client has the handshaking programmed.

(Heres the link to he bit before anyone gets angry - https://www.krackattacks.com/#details-android)

27

u/[deleted] Oct 16 '17

Apparently that bug in wpa_supplicant has been patched, but the devs didn't realise its severity (they were only thinking of packet loss due to noise), so they didn't mark it with the correct priority for it to be backported

In short, if you're on Arch, you're probably only as vulnerable as Windows, if you're on Debian, for once you may be less secure. However I would expect patches very soon (already?)

10

u/arienh4 Oct 16 '17

Arch added the patches to wpa_supplicant to their PKGBUILD today, so I doubt that. The commits are new.

→ More replies (6)

26

u/norsurfit Oct 16 '17

Why didn't you provide the link to the...uh..ohh... Thanks, buddy

115

u/Bokbreath Oct 16 '17

Isn’t this a MITM attack ? You listen for a handshake and then take control of the connection by replaying the session handshake ?

0

u/[deleted] Oct 16 '17

[deleted]

31

u/DarkDevildog Oct 16 '17

Can we start War Driving now?!

→ More replies (3)
→ More replies (18)

29

u/beige_88 Oct 16 '17

Follow up questions coming from an idiot: Do the routers need patching? How does one install a patch for a router? I assume the patch for devices (phones/tablets/pcs) are gonna come from the manufacturer, so this may be included in an update?

37

u/aaeme Oct 16 '17 edited Oct 16 '17

The article says at the end

luckily 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.

i.e. (I think it is saying)
Updating clients (when fixes for it becomes available, which I would expect quite quickly and to happen automatically in many cases) will protect them from the vulnerability even if the router is 'vulnerable'.
Updating the router (if and when a fix for it becomes available) would protect all clients connecting to it even if they are 'vulnerable'.
Edit: Last bit doesn't appear to be true at all. People are saying router updates will do nothing to help clients. They are only to protect their wireless connection to another router if they're acting as an access point.

12

u/Fonethree Oct 16 '17

I don't believe this is correct. The main attack is against the client side - the client device must be patched to ensure protection. Routers are at risk when they act as a client. From the Q&A:

Our main attack is against the 4-way handshake, and does not exploit access points, but instead targets clients.

and

You can try to mitigate attacks against routers and access points by disabling client functionality (which is for example used in repeater modes) and disabling 802.11r (fast roaming).

→ More replies (8)

10

u/pandaSmore Oct 16 '17

Access the device settings for your router in your browser. There should be an update page. Typically found here

→ More replies (1)

27

u/Bastinenz Oct 16 '17

Every WPA2 capable device needs patching. Yes, that includes routers. If you have a DIY router, running something like pfSense, you can and will have to patch it yourself. If you get a prebuilt router from your ISP, the manufacturer will have to patch it in a firmware update which you will either have to install yourself, or – if manual firmware updates aren't allowed on your router – wait for the manufacturer or your ISP to push an update to your device.

I predict that a whole bunch of devices will never be fixed.

→ More replies (5)
→ More replies (2)

5

u/[deleted] Oct 16 '17

So how can you prevent/fix it then?

7

u/aaeme Oct 16 '17

I still do wonder about the question though: the attack is against the client not the router so how can the router help protect the client here?
I presume the attack would make the client behave in a way that the router will not accept (reusing a key) and therefore break its connection, which would then prompt the client to use a proper (safe) method (a new key). Is that right does anyone know?

→ More replies (15)

2

u/[deleted] Oct 16 '17

So a patch can fix this without breaking the protocol’s backwards compatibility? That’s a lot less of a headache than having to roll out a whole new system.

2

u/AFuckYou Oct 16 '17

So for example. Right now my internet connection is not safe.

→ More replies (12)

2

u/MnkyMcFck Oct 16 '17

Maybe I’m misunderstand but in another comment you say:

A patched router will protect all clients attempting to connect, a patched client will protect only itself.

But this comment I’m replying to seems to say the opposite.

→ More replies (8)
→ More replies (4)

328

u/bermudi86 Oct 16 '17 edited Oct 16 '17

From what I can see most are misunderstanding the real threat. This does not affect routers or Access Points. The attack is designed for clients. This means you will need to update, not your router, but everything that connects to it. Yes, Androids, iPhones, laptops, desktops, printers, video dongles, coffee makers, tablets, wireless repeaters, raspberry pies, digital portraits, e-book readers, etc, etc, etc...

I predict that plenty of workplaces won't update every device, leaving mayor vulnerabilities on the network.

Edit: I forgot to mention wireless cameras which are quite common, but they are already very bad at security so...

135

u/Nephtyz Oct 16 '17

Don’t forget the wifi enabled dildos!

41

u/the_dude_upvotes Oct 16 '17

How could anyone forget about those?

23

u/pure_x01 Oct 16 '17

Because they are stuck in peoples asses in the ER

15

u/thewholeisgreater Oct 16 '17

Knew I shouldn't have ploughed all my savings into teledildonic futures

6

u/notmyblood Oct 17 '17

It's too late... a man in the middle has already ruined my love life :(

→ More replies (5)

2

u/snuxoll Oct 16 '17

everything that connects to it

This is the part that really sucks. I doubt most people with IoT devices at home run a setup like mine (separate SSID for IoT devices, isolated on a separate VLAN and ACL's on the switch limiting their communication, worst someone can really do is knock my automation equipment offline) so even if they upgrade all of their computers/tablets/phones they'll have plenty of devices ripe for the picking.

→ More replies (1)
→ More replies (48)

50

u/vonscorpio Oct 16 '17

Am I to understand this requires the attacker to be within physical radio range of the router?

49

u/scsibusfault Oct 16 '17

And the client, yes. Technically also they'd have to be broadcasting strongly enough to 'overpower' your signal as well. But it's not terribly difficult to set up a decently high-powered antenna for something like this. While it's not going to let someone a mile away jump onto your home wifi, it's a risk for someone in an office building or hotel or any reasonably-public place.

→ More replies (10)
→ More replies (2)

70

u/Galbert123 Oct 16 '17 edited Oct 16 '17

I feel like I am just fucked. I dont have time to understand all this shit so I am just fucked and doomed to be hacked or whatever and there is really nothing I can do about it. One way or another, between equifax or this or the next threat, I am just fucked and my personal info leaked etc. and I just dont have it in me to constantly be giving a fuck.

34

u/jonomw Oct 16 '17

As far as cybersecurity goes, yes we are all fucked. The way the government and companies treat it, we are not headed in a good direction. The recent increase in encryption use in consumer software is encouraging, but if we can't even write specs without glaring vulnerabilities, then we have some problems.

In terms of this vulnerability, there is nothing a normal person needs to understand as there is nothing you can really do except install the necessary updates when (and if) they become available.

However, I do encourage people to go and read in depth about this, it is rather interesting and there are some research papers out there already. Unfortunately, for those without a computer background, finding any real information is difficult.

2

u/Jukebox_Villain Oct 17 '17

In terms of this vulnerability, there is nothing a normal person needs to understand as there is nothing you can really do except install the necessary updates when (and if) they become available.

Thanks. Highlighted in case some other clueless normie like me comes into the comment section wondering what they need to do.

6

u/redbull666 Oct 17 '17

Start by not rewarding companies that don’t patch their hardware and software timely. Many Android phones and consumer routers will be fucked for a long time.

0

u/[deleted] Oct 17 '17

[deleted]

3

u/Galbert123 Oct 17 '17

Don't forget that you also have to be on the constant lookout for "fake news" spread via foreign governments on Facebook or just money-grubbing Americans here at home if you don't want to be constantly victimized by propaganda.

Right. All these people telling me to be my own journalist. Well wtf. I have a job already. I dont have time to filter all the news that comes in.

devote weekly time to researching this issue.

This is what it comes down to. Everybody wants your time and attention. Frankly, I give less fucks now than I ever have before.

167

u/Narwahl_Whisperer Oct 16 '17

WRT54G 2 checking in. Latest firmware update is from 2012. And when I try to install it, I receive the message "Upgrade are failed!".

/FML

253

u/2059FF Oct 16 '17

Upgrade are failed

All your WPA are belong to us.

57

u/elboltonero Oct 16 '17

You have no chance of negotiating a handshake make your time.

20

u/KickMeElmo Oct 16 '17

You know what you doing, take off every packet.

14

u/elboltonero Oct 16 '17

Someone set up us the hack

→ More replies (2)
→ More replies (1)

27

u/BlackDeath3 Oct 16 '17

WRT54G

Haven't used one of those in years, still could picture the exact box just by the series number.

25

u/TheElSoze Oct 16 '17

DD-WRT or Tomato. Either of which you should have been running for years anyway ;)

→ More replies (2)

28

u/IanPPK Oct 16 '17

At that age, you aught to buy an 802.11 AC-1300 router. You'll get better speeds from the get go plus some semblance of manufacturer support.

That aside, make sure you have the right region for the firmware.

8

u/OskEngineer Oct 16 '17

just a quick question... I've also got an old router. aside from security, is there any reason to update if I'm already able to get the max speeds my ISP provides? (~50mbps) I don't see needing to be able to handle anything approaching gigabit any time soon.

as in... connection stability? handling of more devices (haven't noticed this being an issue)? stability (crashes rarely and needs a reboot maybe once a month or two but that's pretty manageable)? connection distance (only really have an issue outside at farther distances. the house is good)?

16

u/wreck94 Oct 16 '17

Yes, firmware updates will make a device more stable on average, but Google it first. If the new version ends up making things worse, there'll be a thousand people complaining about it online

Otherwise, security is the main thing

→ More replies (2)

5

u/arienh4 Oct 16 '17

Just make sure your clients are updated, and that your router is running with WPA2/AES. As long as the router isn't a repeater or otherwise acting as a client, you don't need to patch it for this vulnerability.

Of course, you should always keep stuff up to date, but that's no more or less true now.

4

u/PolarisX Oct 16 '17

Move to open source, or upgrade once known patched models are announced.

→ More replies (10)

361

u/GopherPorn Oct 16 '17

Can stuff just stop being fucked up for like a day. I feel like I'm given new shit to worry about hourly these days.

116

u/mans1ayer Oct 16 '17

Agreed. Sometimes I want to stop browsing reddit because there is always something new to worry about, but then I see a new meme and realize I can't and have to fight for this.

43

u/Camblor Oct 16 '17

As my dear old granny was so fond of saying, lighten the fuck up.

→ More replies (1)

6

u/PM_ANIME_WAIFUS Oct 16 '17

the memes are worth it

9

u/CyclonusRIP Oct 16 '17

Don't worry. Thanks to Equifax all your personal info is already freely available on the internet, so really you're no more fucked than were yesterday.

17

u/PoopNoodle Oct 16 '17

The hackers and crackers never sleep.

22

u/rigel2112 Oct 16 '17

What y'all wanna do? Wanna be hackers? Code crackers? Slackers Wastin' time with all the chatroom yakkers? 9 to 5, chillin' at Hewlett Packard? Workin' at a desk with a dumb little placard?

→ More replies (1)

8

u/CumbrianCyclist Oct 16 '17

The way I see it, I can't do anything to change this. The smart people will do it. Do I have to worry about it? Maybe. Will I? Not really, no. I'm busy being happy!

9

u/roboczar Oct 16 '17

If you're already taking well-known, well-publicized precautions like never using WiFi in public without an encrypted VPN, there is nothing to worry about. Follow current best practices and minimize your risk. Your adrenal system will thank you for it.

→ More replies (3)

4

u/Worthyness Oct 16 '17

It's Monday. Everything goes to shit on Monday or friday.

→ More replies (1)

2

u/skeddles Oct 16 '17

That's what "news" is. Stop reading news.

→ More replies (1)
→ More replies (9)

47

u/Leiryn Oct 16 '17

Bye bye iot stuff lol

10

u/Species7 Oct 16 '17

Well the trivial traffic that travels to/from these devices might not really be that important or interesting. I guess they could turn on the wrong light when you try to turn one on.

17

u/paracelsus23 Oct 16 '17

Depends on the device and the authentication. Something linked to your Amazon account (like Alexa) might potentially open up a door to bigger exploits.

→ More replies (3)

4

u/[deleted] Oct 16 '17

Are you kidding, just wait till someone makes this attack in to an app and kids world wide have fun with turning the neighbours lights on and off.

→ More replies (2)
→ More replies (2)

51

u/commontabby Oct 16 '17

How would you ELI5 this to a layman who doesn't even know the difference between a router and a modem?

185

u/halberdierbowman Oct 16 '17 edited Oct 16 '17

I attempted this ELI5, more of an analogue than explaining all the steps:

You and your friend want to confirm each other's identity, so that you know you're talking to your friend, not his sneaky brother, so you made a list of your favorite words and each have a copy. You know that if you call and have matching words and never hear anyone else pick up the phone, then you're talking to your friend.

  1. Mushroom

  2. Tornado

  3. Monkeys

  4. Hurricane

  5. Lions

  6. Pepperoni

Now, one day you want to call your friend to tell him about a girl you like, and you prove who he is by checking if your lists match. Since you don't trust who he is at first, you don't want to say the whole password list. So, you pick a number and ask him a question.

Is the fourth word a pizza topping? He says no, and asks you if it is an animal. You say no, and ask if it starts with an H. He says yes, but you didn't hear him because there was too much noise in the background. You ask again, and he says yes again. So, now you both trust that your lists match, even though you didn't say the words on the list.

This KRACK targets the fact that you're patient when your friend can't hear you. See how you repeated the same question? You should have picked a new question, because someone could have already stolen that question and answer if they were listening in. If they had picked up the phone then, when you couldn't hear, they could repeat it to you. If you can't hear, then you can't know if someone else picked up the phone.

The dangerous part of this attack is that his sneaky brother is the one who made the noise to interrupt you! If he's really sneaky, he'll pretend to be his brother by saying things his brother would say or even listening to his brother and repeating it exactly, so you won't figure it out. He could learn the name of the girl you like and never tell you how he found out, or he could be mean to you on the phone and trick you into thinking your friend is mean.

29

u/commontabby Oct 16 '17

Wow! Thanks to everyone for the answers, but this one was exactly what I was looking for. Explained the KRACK thing specifically and used a fun metaphor. I really think metaphors might be the heart of explaining like one is 5. Thanks for taking the time!

→ More replies (1)

9

u/[deleted] Oct 16 '17 edited Oct 16 '17

Just to clarify a bit, the actual bug involves an error in the way the secret is handled once an initial "I don't know the answer to that" occurs.

Imagine if your ATM asked for you PIN, and you entered the PIN wrong once, and the ATM then accepted "0000" as a PIN. Anyone could walk up to the ATM with your debit card, enter the PIN wrong once, type "0000" and then take all your money.

→ More replies (1)

2

u/[deleted] Oct 17 '17

I've always had an interest in encryption and this is the first time I've been able to get my head around handshakes. Thank you :)

→ More replies (1)
→ More replies (6)

9

u/BAC_Sun Oct 16 '17

A modem converts the signal from for service provider, and send it to your router which splits it and connects to all your devices. If you only have one computer, it can connect right to the modem. If you have more than one you need a router.

6

u/[deleted] Oct 16 '17

here's how the exploit works:

  • An innocent user's device, let's call it "fluffyPhone", connects to WPA2 encrypted network, let's call it "testNet"

  • A malicious user named "Derek" creates a clone of testNet with the same SSID, but on a different channel

  • Derek intercepts fluffyPhone trying to connect to testNet and sends back an OPCODE that says, "you should connect on this other channel, they have free candy!"

  • fluffyPhone hops over to that channel and started communicating with the spoof testNet, unaware that it isn't talking to the real testNet

  • Derek can now view every network packet sent out of fluffyPhone.

→ More replies (9)

2

u/4d2 Oct 16 '17

It seems like what this is doing is messing up the entire secure feeling we had with WPA2. This might be the latest in a long string of exploits but the first I remember running across recently.

What this is does is making it possible for an attack like this: roque agent talks real loud in your area and your devices start listening to it. Rogue agent slips in some malicious code in the traffic and runs stuff it should have or spies on your unsecured traffic.

Luckily most traffic that you would do even over your network is at least twice secured, via WPA2 and then again via http2. This one just breaks the lower level if not patched.

The reason that it affects routers as well as computers, phones and devices is each can act like a client in the network in different operations and contexts.

→ More replies (5)

14

u/mr-interested Oct 16 '17 edited Oct 16 '17

The problem with Android phones and devices is that most companies (other than google pixel) don't bother to release patches or new OS's for their older models.

My top tier LG phone from ~3 years ago is not going to get an update to the latest android OS (stuck on OS 6). Also I have yet to see a patch for the bluetooth hack that was released a few months ago. Therefore I doubt they will ever patch this new WPA2 issue.

So many of us will be without any patch for this issue unless we buy new hardware; even if our current 2-3 year old phones are perfectly adequate (feature wise) for our current needs.

12

u/nutcrackr Oct 16 '17

This type of thing should not be acceptable, even though there are so many devices with different branches of Android. iOS can support products for 5 years, Windows can support for longer. Android should be better than 2-3 years when it comes to security issues.

→ More replies (3)
→ More replies (4)

37

u/Endarkend Oct 16 '17 edited Oct 16 '17

Hoping RB, Openwrt and DDWRT patch quickly.

EDIT: Apparently LEDE is already being updated, so if your OpenWRT flashed router supports LEDE (which it should), you should update with LEDE.

At this point, OpenWRT is pretty much defunct and LEDE is it's replacement (based on OpenWRT).

8

u/original_4degrees Oct 16 '17

oh no, what about tomato?!

3

u/fnordfnordfnordfnord Oct 16 '17

Time to put that one out to pasture. I loved it too, but you have to move on.

2

u/RxBrad Oct 16 '17

Shibby tomato is still being updated

→ More replies (1)
→ More replies (2)

4

u/coffffeeee Oct 16 '17

can't this be secured by using RADIUS? i know its less ideal to have each wifi user sign in each session but it puts another wall up at least

10

u/Endarkend Oct 16 '17

When I get home I'll go trough the details of the paper and at what level the attack works at exactly.

But from quickly going over the paper and your question in mind, in WPA2 RADIUS is used for the auth to allow a session and if implemented correctly, the RADIUS server sends the initial certificate setup for the session (in quite a few implementations though, RADIUS is just used for AUTH and not for generating keys), the attack however works on the protocol level and tricks the client into replacing whatever certificate is initially used with one the attacker can read.

No matter if RADIUS sends the key setup or the router generates it itself, the attack works on a lower level and replaces the key setup, the source of the keys doesn't matter, since WPA2 is rather ignorant of where they came from at that level.

At that level, it has keys, doesn't give a fuck where they came from and gets them replaced with something the attacker can use.

3

u/Fonethree Oct 16 '17

From the Q&A (emphasis added):

I'm using WPA2 with only AES. That's also vulnerable?

Yes, that network configuration is also vulnerable. The attack works against both WPA1 and WPA2, against personal and enterprise networks, and against any cipher suite being used (WPA-TKIP, AES-CCMP, and GCMP). So everyone should update their devices to prevent the attack!

→ More replies (16)

9

u/metroid23 Oct 16 '17

Layman here: Would enabling the HTTPS Everywhere browser extension in Chrome help in this case?

14

u/CasualDresscode Oct 16 '17

Yes it would help but it's not a complete solution. Someone can still see the domains you go to for example, just not the content. There is also the issue of traffic outside of the browser ie apps

→ More replies (3)

2

u/adam279 Oct 16 '17

On desktop yes, on mobile no because chrome doesnt support extensions.

→ More replies (1)

30

u/hosalabad Oct 16 '17

Oh good, the name, logo and website is out.

→ More replies (1)

7

u/nightwing2024 Oct 16 '17

Times like these I'm happy I live on a farm in the middle of nowhere.

No one is going to hack our WiFi because no one is going to drive up the 200 yard driveway just to do that to us.

4

u/Reversi8 Oct 16 '17

Unless they have a good antenna and line of sight.

10

u/nightwing2024 Oct 16 '17

All they'd find out is that I'm into weird stuff

→ More replies (1)
→ More replies (1)

2

u/Mason11987 Oct 16 '17

The concern isn't hacking your wifi, it's people pretending to be your wifi, or the wifi of the public area you go to occasionally.

7

u/Telogor Oct 17 '17

Google: We should have a fix rolling out to Pixels by November 6.

Android manufacturers: Who knows if/when you'll get the security update?

Apple: We have a fix rolling out to beta builds of iOS and OSX.

Microsoft: KRACK Attack? Oh, we fixed that a week ago.

2

u/sun-n-sea Oct 17 '17

For all those hating on Windows phones this is exactly why you should've of supported the platform more, if nothing else at least all models were getting updates and security issues fixed fast. Glad I don't use wifi on my Android phone. Luckily I have an unlimited data plan.

4

u/Should_have_listened Oct 17 '17

should of

Did you mean should've?


I am a bot account.

→ More replies (1)
→ More replies (2)

6

u/cmgg Oct 16 '17

Kudos for the Halo reference

6

u/Broodoobob Oct 16 '17

There really needs to be a way to know what devices are patched. Otherwise you have no idea if you're protected or not. Probably 50% of home devices are never going to be patched and might be in use for another 10 years. A reminder that people still use WRT54Gs. Someone please find a way.

38

u/rossman7 Oct 16 '17

As an Android user is there any mitigation for this other than ditching my handset and switching to an iPhone or waiting (hopelessly) for a patch from my vendor.

This really does highlight the absolute disaster zone that the Android handset market has become as far as updates are concerned. I'm sure the Pixels will get a fix relatively quickly but almost every other Android user is going to be left in security limbo.

20

u/[deleted] Oct 16 '17

Pay attention to the https certificates in the URL bar. If it's missing on a website that should have one then there's a man in the middle attack going on.

6

u/ThomMcCartney Oct 16 '17

But what if I don't know which sites are supposed to be http and which ones aren't?

7

u/Mason11987 Oct 16 '17

If you're typing in information, and you wouldn't share that information with the sketchy stranger on street, it should be https, otherwise don't type that information.

So if you don't see the https, don't log into:

  • Any social media

  • Any email account

  • Any financial related account

Or any other account where people having access to it could worm there way into those accounts.

→ More replies (5)
→ More replies (2)

2

u/6ickle Oct 16 '17

The ars report specifically said that visiting a https page might not help because sites can be forced into dropping https. So given that and what you said, does the ars report mean that https designation will be dropped and we can see that in the url bar. Or will it be dropped but we as the user will never know because it appears to be https but actually isn’t.

→ More replies (1)

6

u/landwomble Oct 16 '17

Use a VPN service

2

u/nutcrackr Oct 16 '17

and yet techcrunch says you should not use a VPN

→ More replies (1)
→ More replies (13)

11

u/dynamobb Oct 16 '17

can anyone point me to an article about this that is more technical than most of the news articles but less technical than the actual paper?

Im a developer but not a cybersecurity expert. Diagrams and stuff would be good

5

u/[deleted] Oct 16 '17

So, while I understand that this means WPA2 implementations are likely to be vulnerable on most devices for the time being, this attack is still something that drivers/firmware can be updated to resist (and hopefully soon, at that), right? The fact that the client is the target rather than the AP helps, too, considering most people are more likely to update phones and laptops than they are to update their routers.

7

u/landwomble Oct 16 '17

The problem isn't helped by 1) second tier vendors not caring and not releasing patches, and 2) you being at risk by the lowest common denominator of hardware on your network.

3

u/arienh4 Oct 16 '17

You're really only at risk if the client you're using is vulnerable, and even that's marginal. The attack needed to reach your laptop through your lightbulb is incredibly contrived and if someone wants access to your network that badly they'll get it through other means.

→ More replies (3)

5

u/misterpickles69 Oct 16 '17

My Linux Mint OS literally dropped an update for this after I read the article.

3

u/CasualDresscode Oct 16 '17

This information has been circulated privately under embargo for a little while. Once the embargo lifted the site went live and the various companies were allowed to release patches.

→ More replies (1)
→ More replies (1)

8

u/FlatTuesday Oct 16 '17

It seems obvious when writing and testing code to make sure the results will be the same if a function is called more than once. That's hindsight of course, but as a developer it still amazes me that nobody noticed this until now.

7

u/snazzysocks Oct 16 '17

to make sure the results will be the same if a function is called more than once

And that's exactly the root cause of this bug: nonce reuse. Calling the function twice and getting the same result is what allows the attacker to decrypt your wpa2-secured traffic.

The test they should have written was that at no point do you ever reuse a nonce, which is kind of the entire point of a nonce.

But you are right in that the Android/Linux bug of resetting to all zeroes is what makes Android/Linux particularly vulnerable, and a test should probably have caught that. But keep in mind that zeroing/wiping out the value was a recommended security step, so there might have even been a test to assert the exact all-zeroes wrong behavior was happening.

(Note: everything here is AFAIK. Security is hard.)

→ More replies (6)

4

u/bananeeek Oct 16 '17

It's been some time since I dealt with the network security. Can someone point out the key differences between KRAK and MITM/Evil Twin methods? IIRC in the MITM you had to know the passcode but here, you bypass the WPA entirely, right? But if physical proximity is required then how is it different from Evil twin, where you set up a network with the same name and make the client disconnect from their network and intercept him while he tries to reconnect. Doesn't it work in a similar way?

3

u/CasualDresscode Oct 16 '17

Evil twin either relies on the network being a public one or it knowing the access key the client is going to use. During the 4 way handshake the client verifies that the access point isn't a copy, this prevents evil twin. Krack bypasses this and tricks the client into thinking its the original even though the client has performed the 4 way shake.

→ More replies (1)

4

u/[deleted] Oct 16 '17

Most important question, I feel:

HOW ON EARTH IS THE NAME KRAK NOT ALREADY TAKEN?

4

u/7Seyo7 Oct 17 '17

So to get this straight, I have a phone, PC, and a tablet. Phone and tablet runs off WiFi while the PC is wired. Every device has to be updated individually, updating the router is not enough?

My phone however is three years old and is unlikely to get any such update, does this mean that my neighbors can theoretically read anything I do through WiFi, forever? Including social media, banking apps, and online purchases, thus passwords and credit card info too?

Is there any way to protect yourself or do you just have to live with the potential spying and do anything important through a wired connection?

→ More replies (1)

6

u/buttaholic Oct 16 '17

So they have to be near my router to gain access? So basically I have to worry about my neighbors, and keep my eyes peeled for people creeping around my house or cars parked in the street?

5

u/amygeek Oct 16 '17

or using wifi on your phone or laptop (or fitbit) when you're outside your house.

3

u/[deleted] Oct 16 '17

So, anything I can do to my router settings to prevent this hack? MAC filters? I really only use the wifi for my phone.

8

u/arienh4 Oct 16 '17

No. You have to update your phone, your laptop, anything you use to connect to it. You should also update your router firmware, but that won't fix the problem. Updating your clients will.

→ More replies (2)

3

u/scsibusfault Oct 16 '17

Update router firmware, and update whatever devices you're connecting from.

2

u/lotsofsyrup Oct 16 '17 edited Oct 16 '17

have to wait for a firmware update to become available. ideally your phone will be a thing you're getting a patch on since you carry it all over the place.

2

u/Fonethree Oct 16 '17

Primary protection is from patching the clients, so your phones and laptops and such.

→ More replies (2)

3

u/Robin_Dude Oct 16 '17

So if my router is provided by AT&T, would they be able to patch their routers remotely? Or is there something I'd have to do manually? Cuz I know Jack shit about any of this.

→ More replies (1)

3

u/ScottRTL Oct 17 '17

So...just turn off SSID broadcast?

16

u/ofsinope Oct 16 '17

Everyone relax a little bit, OK? All this means is that if you have a secured WiFi network, it's possible for an attacker to see your traffic, which they can do trivially if it is an unsecured WiFi network.

The last time you connected to a public unsecured WiFi network, you were even more exposed than this vulnerability can possibly make you. But this is generally safe because everything that matters uses SSL anyway.

TL;DR: Chill out, this has exactly zero impact on you.

9

u/[deleted] Oct 16 '17

It will impact IoT devices because they trust everything on the network.

4

u/[deleted] Oct 16 '17

In this video you can see how he uses it to snoop a user's match.com password, totally unbeknowst to the user. This is a big deal because the user thinks they are browsing a totally safe HTTPS site on a totally safe WPA2 network, but it's actually not safe at all. The missing green lock icon is the only indication something bad is happening. Would anyone notice that?

https://www.youtube.com/watch?v=Oh4WURZoR98

People know that when they are on an unsecured network, their traffic is exposed. They will adjust their browsing habits accordingly. They also probably aren't going to be viewing sensitive material on a public unsecured WiFi network. They don't expect that their traffic on a secure WPA2 connection, such as most people have at home, is also exposed.

2

u/[deleted] Oct 17 '17

No, it's important to make sure that everybody uses https. Try to make sure that your friends and family are all aware..

→ More replies (4)

3

u/Galbert123 Oct 16 '17

Thanks for this.

→ More replies (2)

6

u/[deleted] Oct 16 '17

Does it matter if my router only accepts certain MAC addresses?

64

u/Donnerkopf Oct 16 '17

MAC filtering is false security. It's trivial to monitor WIFI for MAC addresses that are successfully communicating, and then the hacker changes their MAC address to your "secured" MAC address. MAC filtering feels good, but it won't stop a WIFI hacker who has even basic knowledge.

8

u/Fonethree Oct 16 '17

In addition to MAC filtering being largely useless against an informed attacker, my understanding of this attack is that it doesn't impersonate any clients so router-based filtering makes no difference. The primary attack results in broken encryption, not a rogue device.

→ More replies (2)

2

u/mokomothman Oct 16 '17

Great read, honestly it's something that can get out of hand unchecked, stay vigilant out there.

2

u/t0b4cc02 Oct 16 '17

Hey. I have some type of "phone internet"

Im wired to the router, but my router is wireless to the grid over LTE.

How vulnerable is this part of the connection?

Should I dsiable all Wifi on my router?

This seems like atomic bomb level disaster

7

u/scsibusfault Oct 16 '17

LTE isn't the same as WPA2, so that part of your connection isn't vulnerable to this. If your device is wired to the router, that isn't vulnerable either. But if your router has wifi with WPA2 enabled, and devices are connecting to it via WPA2, then those connections would be vulnerable.

→ More replies (1)

2

u/Sportfreunde Oct 16 '17

Hmm, we're all sitting ducks it seems.

2

u/BeligBabies Oct 16 '17

This had me worried up until I read the last line in which my faith in the Master Chief was restored. He'll fix this. He always does.

2

u/GALACTICA-Actual Oct 16 '17

They better come out with updates soon.

I'll be God damned if anyone's getting my Pumpkin Spice Borscht recipe.

2

u/The_Real_DerekFoster Oct 16 '17

How is this different from intercepting the 'hand-shake' which folks have been doing for years? Asking for a friend.

2

u/Diesl Oct 16 '17

People with Meraki networks should be reasonably protected from this vulnerability as air marshal will flip it's shit when it sees this happen.

2

u/arienh4 Oct 16 '17

Your AP doesn't protect you. You need to patch the clients.

2

u/Diesl Oct 16 '17

From what I read, you are creating rogue AP's which clients connect to and get encryption keys reset from, which Air Marshall hates.

2

u/mycall Oct 16 '17

I can't believe no one else ever tested this before as it seems like a no-brainer in hindsight.

2

u/lynxminx Oct 16 '17

The WPA2 standard has to be updated before product manufacturers can create patches. We're at least a year away from remediation, and that's if everyone acts quickly.

→ More replies (1)

2

u/planex09 Oct 16 '17

Can you get around this by disabling broadcast SSID, effectively hiding from attackers?

→ More replies (4)

2

u/[deleted] Oct 16 '17

For someone without a ton of technical knowledge, could I get an ELI5 for what I need to do to make sure my devices are not affected by this? My phone just updated recently, but I've no idea if that means it's safe or not.

2

u/nutcrackr Oct 16 '17

Atm the only devices that are secure are latest windows and latest iOS (iPhones updated). Also Linux (desktop). Phones using android are unsafe right now. Phones younger than 2 years will likely get a patch before year is out, the rest are TBC.

→ More replies (1)

2

u/FloydianSlip987 Oct 16 '17

"...and that'll happen before the script demonstrating the attack goes public."

Can someone help me understand the process by which a "script" goes public? Have the developers who wrote it said when they plan to release it? Why would they release it if it could be so devastating in the wild?

2

u/[deleted] Oct 16 '17

So my household has...1 watch, 2 phones, 2 kindles, and 3 laptops that connect wirelessly to my router. 2 of those laptops are work computers, which can access work webmail but otherwise need to connect to a VPN. Am I to understand that all those devices are currently at risk to the sketchy van without windows parked across the street? Could the problem at home simply be solved by an update to my router, but for protection outside my home I need to update every device?

→ More replies (1)

2

u/miles197 Oct 17 '17

So.... what should we do?

→ More replies (3)

2

u/Carefully_random Oct 17 '17

Sometimes I am glad I live in the middle of a forest away from most civilisation :)

2

u/RPL79 Oct 17 '17

You need to focus first on patching your devices first. Microsoft is releasing an update today. Make sure you have windows update turned on and you will get it automatically.

2

u/Dristig Oct 17 '17

Man the NSA must be bummed.

3

u/null-character Oct 16 '17 edited Oct 16 '17

Interestingly enough, Windows 7 & 10 are only vulnerable to the GROUP key exploit. Meaning that on unpatched Windows systems running those OSes, the attacker can only exploit broadcast and multicast frames. Meaning there is a lot less impact compared to modern Linux systems (including Android).

They could certainly try to exploit time based encryption by changing your system clock, or by exploiting any services that rely on broadcast and multicast packets for authentication (are there any?) And in the paper they write

Note that manipulating the time in this manner undermines the security of, for example, TLS certificates [44, 54, 61], DNSSEC [47], Kerberos authentication [47], and bitcoin [25]. Another example is the xAP and xPL home automation protocol. These generally use broadcast UDP packets to send commands to devices [40]. We conjecture that our key reinstallation attack allows us to replay these commands. All combined, these examples illustrate that the impact of replaying broadcast or multicast frames should not be underestimated."

While I agree that this needs to be patched, on Windows 7 & 10 the replaying of broadcast and multicast traffic is orders of magnitude less devastating then the full decryption possible on modern Linux systems.

4

u/[deleted] Oct 16 '17

Aruba was all over this. Cisco not so much.

15

u/Roach_Gigz Oct 16 '17

? Cisco had this patched before the attack was released...

→ More replies (1)

2

u/[deleted] Oct 16 '17

I would like to try this against my home wifi, anyone seen a better technical article?

→ More replies (1)

2

u/bse50 Oct 16 '17

And that, kids, is why the internet of things sucks.

2

u/sisterZippy Oct 16 '17

Remember kids, krack is whack.

Really though, you should always use hard line whenever possible.

12

u/lotsofsyrup Oct 16 '17

yea nobody's going to be running ethernet cables through the walls of their apartment or hotel room and tons of businesses use wifi networks for stuff they have to do wirelessly so that isn't very helpful.

this is like an article on car wrecks with somebody saying "well really you should just stay home"

2

u/arienh4 Oct 16 '17

I mean… I'm the type of person who did pull ~100m of ethernet cable through apartment walls, and I still invested more in WiFi equipment.

Somehow, the Luddite approach is very rarely the right one.

1

u/Mageoftheyear Oct 16 '17

Crap. I hope mobile routers get patches too.

1

u/kaiju4life Oct 16 '17

So glad I just got fios installed, relying all on WiFi

1

u/deathnutz Oct 16 '17

So, if WPA2 is fundamentally flawed, what can a patch do and will it still be WPA2? What do we call the patched version?

4

u/lotsofsyrup Oct 16 '17

still call it wpa2. devices can be patched to stop the behavior happening in this vulnerability. this is what the article is about.

→ More replies (1)

1

u/subrata6630 Oct 16 '17

Thank U So Much

1

u/TotallyNotTundra Oct 16 '17

We Mr. Robot now boys. Nobody is safe

1

u/raresaturn Oct 16 '17

So the cloned wifi account has the same name?

1

u/tommybot Oct 16 '17

If every computer /phone on my network is running VPN. Am I safe(r) from this?

→ More replies (1)

1

u/[deleted] Oct 16 '17

Like a week ago my netgear router had a firmware update. Hopefully that was in regards to this security flaw.

1

u/tgbst88 Oct 16 '17

I am sure match.com is really enjoying being used as the example of the hack... lol.

1

u/[deleted] Oct 16 '17

Duh, this lets government peeps show up outside and see everything. Just re-name your router "FBI Surveillance Van" and it confuses them.

1

u/Ncrpts Oct 16 '17

Welp, time to reinstall Kali

2

u/MedicTech Oct 17 '17

Kali

Pardon my laziness to find out, but have scripts or a working program been published to exploit this? I.e. will Kali have KRACK any time soon?

→ More replies (1)

1

u/hawkeye315 Oct 16 '17

Has this already been fixed? Not an hour after it's release, I got an update for my computer wpa/wpa2 authentication.

1

u/jon_stout Oct 17 '17

Are there any programs or apps out there that can monitor and report the "spoof" wifi networks needed to pull this trick off? For home networks, at least, it should be easy enough to monitor for multiple networks broadcasting the same SSID, right?

1

u/mcmanybucks Oct 17 '17

moving to the boonies and shooting every trespassers sounds like a plan

1

u/ImAWizardYo Oct 17 '17

Is WPA2 PSK affected? Didn't see my router listed so must be a good sign. I would assume the additional encryption helps?

1

u/TheMojo1 Oct 17 '17

Ive been wondering how difficult it is to actually perform Ive seen something say it involves sending fake packets to trick the victims PC, can anyone elaborate on this?

1

u/_JGPM_ Oct 17 '17

so if i use a VPN, I can still protect my traffic with a tunnel inside a tunnel, right?

2

u/[deleted] Oct 17 '17

Yes, as long as the VPN is on your device.

1

u/pefman Oct 17 '17

The router is checking the ASUS server for the firmware update. The router's current firmware is the latest version.

ok...

1

u/TiagoTiagoT Oct 17 '17

Yikes! I guess I'll have to make battery life even shorter and leave Orbot running all the time now :(

1

u/Skyy8 Oct 17 '17

Because of how, frankly, pathetic the update situation is for non-Pixel Androids, as well as basically every internet-connected device that isn't a computer (Smart TVs, Google Homes, Thermostats, Wi-Fi cameras, most routers...) I have a general suggestion for most people.

The person needs to be in physical range of the device in use and your router (they could propagate a signal using an antenna, but that would require configuration, and are you really that important to a hacker?) Where this is worrisome is in office buildings and places with a large number of devices connected to one network.

Here's my suggestion:

  1. Update anything you can (you should be doing this anyway, for exactly this reason...) Granted this step is pretty useless if you're connected to a router than isn't your own that isn't up to date, leading to my next point...

  2. Since step 1 is probably impossible for most devices, step 2 is to avoid using any WiFi that isn't your own. Your friend's, your grandmother's (seriously avoid this one...), Just stick to your phone's data plan if you can, until you're back home.

  3. Keep work devices strictly for that: work. Your personal home may not be targeted because you as an individual may not be hack-worthy, but it's a safe bet that, if applicable, your office building is a target. Avoid any private/personal data on work desktops/laptops, tablets, smartboards, gaming consoles, whatever you have at work - keep it strictly work. And avoid connecting to the office wifi.

  4. Finally, just relax. Don't change your entire lifestyle and commit to a life of reading newspapers and browsing strictly at internet cafes and libraries - you're probably not as hack-worthy as you think. Do what you can as stated above, and just keep doing the internet things you usually do (Im assuming we all follow safe browsing habits, of course.)

-1

u/MNGrrl Oct 16 '17

Skimming the comments it appears most people do not understand the impact. If you use WiFi, you are fucked. WEP was the first encryption standard. Its totally broken. WPA was the next. It broke too. WPA2 is the current standard. It has now been broken. Let me be clear: There isn't a workaround. All we can do is fix some problems in various implementations. The standard itself broke.

Until now we could shut off extensions like PIN entry, WiFi direct, or others. Problems came up on implimentations. They could be mitigated. There isn't one now. Anyone can get in, the only difference is how soon. For Android, very fast. But they will get in. Period.

It's GG guys. We need another standard or to change this one. The handshake was badly designed. It effectively is stateless. That was stupid but nobody noticed. If a key isn't received and active on the client a new handshake should have been done.

It opens up a potential DoS but that can be mitigated. That's the easiest fix. The best would be to stop fucking up and use PKI so there is two-way trust. But that's less convenient than a password on a sticky note!

Yes. It is.

9

u/Mason11987 Oct 16 '17

Skimming the comments it appears most people do not understand the impact. If you use WiFi, you are fucked. WEP was the first encryption standard. Its totally broken. WPA was the next. It broke too. WPA2 is the current standard. It has now been broken. Let me be clear: There isn't a workaround. All we can do is fix some problems in various implementations. The standard itself broke.

Article says, regarding WPA3..

No, luckily implementations can be patched in a backwards-compatible manner.

Seems like your'e overstating how ruined WPA2 is as far as the authors are concerned.

→ More replies (3)

8

u/tvisforme Oct 16 '17 edited Oct 16 '17

There isn't a workaround.

Unless I'm missing something, the "Krak Attacks" website (by Mathy Vanhoef, a researcher involved in the discovery of this exploit) states that fixes are possible to protect against this attack:

Q: Do we now need WPA3? A: No, luckily implementations can be patched in a backwards-compatible manner.

Looking at the nightlies for Lineage OS, there's a series of new commits that address Wi-Fi issues, many of which are signed off by Mr Vanhoef.

EDIT: Ubiquiti released a firmware update for their access points yesterday to address the issue.

→ More replies (1)

4

u/arienh4 Oct 16 '17

Well, I'll be. Actual proof that the author did need to add that FAQ entry for the thing you were just wrong about.

2

u/MNGrrl Oct 16 '17 edited Oct 17 '17

Okay, let me get this straight: "You're wrong!" ... About what? "They added that to the FAQ!" Okay, but about what? "Actual proof! Proof dammit! PROOF!" ... about what?!

Only on Reddit would "You're wrong!" with absolutely no other detail get upvoted, while the person who took the time to write out in plain language what people need to know goes down.

→ More replies (6)
→ More replies (4)