Thread 1/14
I'm going to cover some of this in my Defcon talk on Fri, but it's important to understand the wifi threat model. https://x.com/defcon/status/1026635046021677056
8/7/2018, 10:47:41 AM π
Favs: 35
Retweets: 17
← @singe Twitter archive
Thread 1/14
I'm going to cover some of this in my Defcon talk on Fri, but it's important to understand the wifi threat model. https://x.com/defcon/status/1026635046021677056
8/7/2018, 10:47:41 AM π
Favs: 35
Retweets: 17
2/14 When defending against rogue AP attacks, enterprise wifi auth security basically comes down to a single certificate validation, that of the RADIUS server.
8/7/2018, 10:48:11 AM π
Favs: 2
Retweets: 2
3/14 In wifi it's hard to do cert validation because the CN doesn't match the wifi name like a website cert's CN matches the hostname.
8/7/2018, 10:48:47 AM π
Favs: 3
Retweets: 0
4/14 So the most common way to validate a cert is based on it's CA. That the default for Linux and Windows. The Defcon cert is from DigiCert. Windows can be fixed, Linux can't.
8/7/2018, 10:49:48 AM π
Favs: 2
Retweets: 0
5/14 If you just validate on CA, then I can buy a DigiCert signed cert, and your wifi client will happily accept that as valid. Defcon's Linux config is vulnerable to this.
8/7/2018, 10:51:00 AM π
Favs: 4
Retweets: 0
6/14 That means a rogue AP can automatically intercept the credentials you create on the portal. Username in the clear but creds need MSCHAPv2 cracking. Here's an eg with Defcon's config.
8/7/2018, 10:51:37 AM π
Favs: 3
Retweets: 0
7/14 So don't sign up with creds you use anywhere else, and make the password obnoxious. Apart from disclosure, if they are cracked, your device will connect to the bad AP without you knowing, and then MitM happens.
8/7/2018, 10:52:05 AM π
Favs: 2
Retweets: 1
8/14 As an aside, if you hand config your iOS/macOS device, instead of using the config Defcon provides, then your device will connect instantly, without cracking required (vuln reported), and MitM will happen. So use the recommended config.
8/7/2018, 10:52:45 AM π
Favs: 2
Retweets: 0
9/14 Another aside, we'll show you how you can MitM the rest of the devices without cracking in a new attack we'll release on Fri. Linux & Windows could defend against this, but the Defcon (and most) config's don't. https://defcon.org/html/defcon-26/dc-26-speakers.html#Singe
8/7/2018, 10:53:45 AM π
Favs: 5
Retweets: 0
10/14 Back to cert validation. The Windows config Defcon suggests prevents this by also validating the certificate CN. While I can buy a DigiCert cert, I can't buy one for http://wifireg.defcon.org, so you're safe.
8/7/2018, 10:54:17 AM π
Favs: 1
Retweets: 0
11/14 The iOS/macOS config also prevents this, because it loads the exact wifireg cert, and validates on that. So because I can't clone that exact cert, you're safe.
8/7/2018, 10:54:39 AM π
Favs: 1
Retweets: 0
12/14 That said, if you don't follow Defcon's sage advice and use their profile, then I can do this, and unless you're validating on fingerprint, you won't be able to spot the malicious cert. And no valid CA doesn't matter to iOS. https://github.com/sensepost/apostille
8/7/2018, 10:55:42 AM π
Favs: 5
Retweets: 0
13/14 Another aside, even if you use the profile, if you have iCloud synching on, your other iDevices could connect to the Defcon network, and if they don't also have a VPN, you might get a surprise (not tested). So VPN all the things.
8/7/2018, 10:56:14 AM π
Favs: 1
Retweets: 0
14/14 So, tl;dr. Use the Defcon wifi, but use strong disposable creds, avoid using Linux/Android, prefer iOS/macOS (via Defcon's profile) or Windows (with Defcon's config) & make sure you have a decent VPN on all devices.
8/7/2018, 10:57:20 AM π
Favs: 4
Retweets: 4
As a bonus, to those hoping to run WiFi attacks, rather donβt be a dick & just let people use the WiFi in peace.
8/7/2018, 11:11:30 AM π
Favs: 12
Retweets: 0