 So a really fun thing about working in computer technology is answers given 24 hours ago could completely change today. So if you ask me was Wi-Fi WPA2 fairly secure and hard to crack, I'd say, yeah, brute force is definitely a problem, but we're pretty confident that it's somewhat secure, but you know, subject to change that should be like at the end of every sentence. And that's because of the key in reinstallation attacks, breaking WP2 by forcing a nonce reuse. This is fun, and especially when you are on the side of defense, which I've always said is the way, way harder side to be on, because well, now it's our responsibility to update our clients and secure all the devices and deal with all the questions that are going to be coming from this, which is why I'm making a video on it, because I'll be sharing this with some of our clients who ask questions like, what does this mean? Am I protected? What are you guys doing about this? What do I pay you for? And all the fun questions that come with a major security vulnerability disclosure. So this is the key reinstallation attacks breaking WP2. And what they found is, and they have a great demo here, I'm going to make it full screen, that show the crack attack. And I love that security vulnerabilities don't just get assigned some boring CVE number, which is important so we can understand the vulnerability and ID the vulnerability and disclose the vulnerability and fix the vulnerability. We get cool fun names and logos, but this is a really serious attack. So they have and they have not released the scripts that make all this function, but they give a proof of concept that when you take this crack attack and then apply it with other things, other tools out there, how they're able to hijack sessions and do some downgrade attacks. Now, the way this works is we're looking at a flaw in the way the four way handshake works. So I'll link to all this below in the description, but this is Wikipedia and on the 802.11 standards and it's the four way handshake that they're able to break and the way the encryption they found out that you can essentially hijack this and that's what this whole demo is is the details. They have an entire white paper here. This is based on which was abusing WP2 H11 group keys. And this does affect both AES and TKIP encryption. So it's not just a matter of affecting just Wi-Fi, it affects the two, both of the encryption. Now, the couple of the, they have some Q&A details and demos. Do we need WP3? I, I thought this was funny in some of the Q&A, they say, should I change my Wi-Fi password? That doesn't mitigate this at all. These are great questions that they have in here. And the problem really comes into, if you're using TKIP, this attack means they can inject traffic. And that's actually what gets really scary. Good news is if you're using AES, they can only snoop your traffic. And so that's really kind of a distinguishing factor. Most people, most of our clients, we're always using AES and other encryption methods on our network. So they may be vulnerable to snooping, but not vulnerable to injection, at least right now. And this is, there's plenty of fixes on the way. So how are we handling some of the fixes on this? Good news is we use a lot of Unify products and they're really on top of this. Matter of fact, last edit 54 minutes ago, and this is 8 AM on Monday, they actually had a beta released of the firmware if you're signing up for any of their beta channel stuff. So this is still not completely released yet. As of right now this morning, here's our Unify is still on version 3.8. I'm going to, while we're doing a video here, we'll go ahead and check for a firmware update, see if that's made it down, checking for firmware update, go back over to my devices. All right, nothing yet, but the way we mitigate this is in our Unify controllers, we have automatically upgrade firmware, unless there's any reason not to do it because you have some other concerns. We generally push out the firmware as soon as it becomes available to us. The system automatically keeps a rolling check for it. So this is how we're doing our best to keep our clients up to date. Now, the snooping part is definitely a problem, a concern when you're using AES. The good news is, most, especially with our network, most of our stuff is all kept encrypted anyways. So even though this is our trusted side of the network because it's behind a password, which we turns out doesn't matter because they can crack it or they can get onto the network, it only allows them to snoop. So I always make the assumption that if I can't encrypt it, I should encrypt it because everything could at some point be compromised. So this doesn't really raise too many security concerns for us. Now, one of the things they did in this attack was show that they did a downgrade of the person's Wi-Fi, I'm sorry, not their Wi-Fi, but of the connection, they showed that they injected it to take someone who normally would go to an SSL connection because most things are done over SSL or secure connections now, and it brings it down to non-SSL. Well, some sites support that still, which is unfortunate because they're not properly configured, so it is a good thing. But internally, for our networks, we just disable any non-SSL ports. So when you're connecting to different web-based applications that we have running in our network, it's always SSL. There's not an option to downgrade us to another attack, hence kind of mitigating some of these problems, and I believe Google's mitigated this as well because you can't connect to Google, for example, on a non-SSL connection. Google says, nope, can't do it, so there's some safety nets inside of this. And this is only if you're running TKP and it allows them to inject this in there. So be waiting for the updates. I'll link below to all the different papers and all the pieces in here, and they have a lot of detail if you're into some of the security research at the very detail level of how they found this. Very clever to read all of the paper and all this little information. I mean, this is pretty in-depth about how the whole protocol works and all the details exactly how they do the key framing and how they figured out how to get things in there, and the demo video really good as well. I mean, it's a very good proof of concept along with what can be done once you have it, which I think is important for some people to say, okay, so you can snoop. Now what? Well, this is what we can do. We can bounce you over to this network and things like that. So like I said, you have to wait for firmware updates. If you're running consumer Wi-Fi, I'm sorry. I don't know if they'll ever do updates for this, but if you want to know if you're affected, do you have a device as Wi-Fi? You're probably affected. That's pretty much the rule of thumb for this. So everything needs to be updated, not just the Wi-Fi devices. I believe you have to update all the firmware and a lot of other devices themselves. That way they are not vulnerable to this attack either because it's a way that the keys are exchanged. I believe we need updates on both sides, not just the access points, but the devices themselves to really make this secure. So get out there, get patching. If you like the content here, like and subscribe. If they release the tools, I may download and play with them to see how this works against some different devices. So I'm very curious myself. But once again, get out there, get patching, keep the 10 fall ahead on, and never just assume everything secure like it was maybe 24 hours ago before this got released. Thanks.