# Windows Phone devices can be tricked into revealing wi-fi passwords

**URL:** <https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587>\
**Category:** Factual Questions\
**Created:** [August 7, 2013, 2:03pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587 "2013-08-07T14:03:44Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![deltasigma](https://avatars.discourse-cdn.com/v4/letter/d/e5b9ba/32.png) [@deltasigma](https://boards.straightdope.com/u/deltasigma)\
**Post date:** [August 7, 2013, 2:03pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/1 "2013-08-07T14:03:44Z")

</div>

I don’t learn any more about networking than I have to (and generally not even that), but even I think [this is pretty sloppy](http://www.pcworld.com/article/2046025/rogue-hotspots-can-steal-your-windows-phones-saved-wi-fi-passwords-microsoft-warns.html).

Basically how it works is described in the article this way. Your company wi-fi SSID is say ACME1. If you have your phone set to auto connect to wi-fi networks, when it sees any with that name, it reveals your authentication info.

Once that is intercepted, a hacker can use that to log in to the real ACME1 location.

What’s more, Microstiffie has no plans to fix this security hole.

---

<div class="post-metadata">

**Author:** ![Bricker](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@Bricker](https://boards.straightdope.com/u/Bricker)\
**Post date:** [August 7, 2013, 2:15pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/2 "2013-08-07T14:15:10Z")

</div>

The linked article says:

> [@](#):
>
> Once Bob walks in with his Nokia 920 with the Wi-Fi turned on, his phone will try to connect to the bogus ACME1 Wi-Fi network. During the phony authentication process, the hacker will be able to intercept the encrypted domain credentials stored in Bob’s phone.
> 
> Now, that wouldn’t be a problem if Microsoft was using a cryptographic standard known to be resistant to attack, but Windows Phone uses an authentication protocol called PEAP-MS-CHAPv2 (Protected Extensible Authentication Protocol with Microsoft Challenge Handshake Authentication Protocol version 2) that packs some key cryptological weaknesses, which are exploited by this vulnerability.
> 
> So after the hacker nabs Bob’s login credentials, the baddie can simply capitalize on the weak encryption to obtain Bob’s credentials and then login to the real ACME1 with the same user privileges as Bob.

It’s not clear to me if the weakness is in the WPA2 encryption used by the WAP, or the passing of the workplace domain credentials, or both.

In other words, two things are going on here. The first is the authentication between the Windows phone and the Wireless Access point. This is WPA2, presumably. The second appears to be the effort by Bob to authenticate to his company’s Windows domain with his user name and password. (I suppose, if the company was using WPA2-Radius or something similar, those two credential sets could be identical).

So where is the weak point? I’m confused. Is it the Windows domain credentials or the WPA2 password?

---

<div class="post-metadata">

**Author:** ![deltasigma](https://avatars.discourse-cdn.com/v4/letter/d/e5b9ba/32.png) [@deltasigma](https://boards.straightdope.com/u/deltasigma)\
**Post date:** [August 7, 2013, 2:18pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/3 "2013-08-07T14:18:54Z")

</div>

No idea. I use an android phone myself. Just trying to help out here. 😕 🙂

---

<div class="post-metadata">

**Author:** ![Bricker](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@Bricker](https://boards.straightdope.com/u/Bricker)\
**Post date:** [August 7, 2013, 2:35pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/4 "2013-08-07T14:35:47Z")

</div>

Given this is a ultimately a factual question, I hope the OP won’t object to my asking the mods to move this to GQ.

---

<div class="post-metadata">

**Author:** ![deltasigma](https://avatars.discourse-cdn.com/v4/letter/d/e5b9ba/32.png) [@deltasigma](https://boards.straightdope.com/u/deltasigma)\
**Post date:** [August 7, 2013, 2:43pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/5 "2013-08-07T14:43:54Z")

</div>

Not at all.

edit: feel free to modify the title and OP as necessary as well.

---

<div class="post-metadata">

**Author:** ![Ellen\_Cherry](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ellen_cherry/32/3600_2.png) [@Ellen\_Cherry](https://boards.straightdope.com/u/Ellen_Cherry)\
**Post date:** [August 7, 2013, 3:01pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/6 "2013-08-07T15:01:36Z")

</div>

Moving thread to General Questions, from MPSIMS.

---

<div class="post-metadata">

**Author:** ![yoyodyne](https://avatars.discourse-cdn.com/v4/letter/y/a9a28c/32.png) [@yoyodyne](https://boards.straightdope.com/u/yoyodyne)\
**Post date:** [August 7, 2013, 3:28pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/7 "2013-08-07T15:28:46Z")

</div>

The phone OS isn’t set to use server certificates automatically. When it attempts to authenticate to the rogue AP without using certs, it sends a plaintext hash of the domain credentials. This hash can be broken due to a weakness in the encryption method and the domain credentials revealed, allowing domain login.

WPA2 isn’t involved in the vulnerability.

---

<div class="post-metadata">

**Author:** ![Bricker](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@Bricker](https://boards.straightdope.com/u/Bricker)\
**Post date:** [August 7, 2013, 3:40pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/8 "2013-08-07T15:40:13Z")

</div>

> [@yoyodyne](#):
>
> The phone OS isn’t set to use server certificates automatically. When it attempts to authenticate to the rogue AP without using certs, it sends a plaintext hash of the domain credentials. This hash can be broken due to a weakness in the encryption method and the domain credentials revealed, allowing domain login.
> 
> WPA2 isn’t involved in the vulnerability.

OK.

And apologies for what may be a foolish question, then, but in this scheme, the Windows phone is using domain credentials to authenticate to the WAP?

How can WPA _not_ be involved?

---

<div class="post-metadata">

**Author:** ![Sparky812](https://avatars.discourse-cdn.com/v4/letter/s/eb9ed0/32.png) [@Sparky812](https://boards.straightdope.com/u/Sparky812)\
**Post date:** [August 7, 2013, 3:48pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/9 "2013-08-07T15:48:30Z")

</div>

nevermind, ninja’d

---

<div class="post-metadata">

**Author:** ![yoyodyne](https://avatars.discourse-cdn.com/v4/letter/y/a9a28c/32.png) [@yoyodyne](https://boards.straightdope.com/u/yoyodyne)\
**Post date:** [August 7, 2013, 4:25pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/10 "2013-08-07T16:25:18Z")

</div>

It uses domain credentials to attempt to authenticate to a server, which then permits or denies access to the network. Basically personal WPA uses the pre-shared key for both encryption and network access authorization. Enterprise WPA splits them out, and after authorization the encryption key is automatically negotiated by the server and devices. There isn’t a pre-shared key.

In this case the WPA encryption isn’t where the issue lies, it’s in the methods used to encrypt and pass the domain credentials to the authentication server.

---

<div class="post-metadata">

**Author:** ![Really\_Not\_All\_That\_Bright](https://avatars.discourse-cdn.com/v4/letter/r/e8c25b/32.png) [@Really\_Not\_All\_That\_Bright](https://boards.straightdope.com/u/Really_Not_All_That_Bright)\
**Post date:** [August 7, 2013, 4:56pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/11 "2013-08-07T16:56:58Z")

</div>

Isn’t this a weakness that _any_ device configured to seek out broadcasting SSIDs shares?

---

<div class="post-metadata">

**Author:** ![yoyodyne](https://avatars.discourse-cdn.com/v4/letter/y/a9a28c/32.png) [@yoyodyne](https://boards.straightdope.com/u/yoyodyne)\
**Post date:** [August 7, 2013, 5:27pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/12 "2013-08-07T17:27:54Z")

</div>

Yes, any client that isn’t set to check the server certificate before attempting to authenticate will have the same issue.

---

<div class="post-metadata">

**Author:** ![ZenBeam](https://avatars.discourse-cdn.com/v4/letter/z/3ab097/32.png) [@ZenBeam](https://boards.straightdope.com/u/ZenBeam)\
**Post date:** [August 7, 2013, 5:36pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/13 "2013-08-07T17:36:01Z")

</div>

> [@yoyodyne](#):
>
> Yes, any client that isn’t set to check the server certificate before attempting to authenticate will have the same issue.

Will this affect my laptop, which is set to connect to my wireless router? Is there some way to check if it’s checking the server certificate?

---

<div class="post-metadata">

**Author:** ![yoyodyne](https://avatars.discourse-cdn.com/v4/letter/y/a9a28c/32.png) [@yoyodyne](https://boards.straightdope.com/u/yoyodyne)\
**Post date:** [August 7, 2013, 5:44pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/14 "2013-08-07T17:44:35Z")

</div>

> [@ZenBeam](#):
>
> Will this affect my laptop, which is set to connect to my wireless router? Is there some way to check if it’s checking the server certificate?

If you’re talking about your home router, you have nothing to worry about. It’s only if you’re trying to log into a Windows domain via WiFi.

This is pretty good discussion: [Revolution Wi-Fi: Is WPA2 Security Broken Due to Defcon MS-CHAPv2 Cracking?](http://revolutionwifi.blogspot.com/2012/07/is-wpa2-security-broken-due-to-defcon.html)

---

<div class="post-metadata">

**Author:** ![Bricker](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@Bricker](https://boards.straightdope.com/u/Bricker)\
**Post date:** [August 7, 2013, 5:54pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/15 "2013-08-07T17:54:58Z")

</div>

> [@yoyodyne](#):
>
> Yes, any client that isn’t set to check the server certificate before attempting to authenticate will have the same issue.

Wait a second.

How can the device check the server certificate BEFORE it’s negotiated the WPA connection?

Look, let’s say I buy a consumer-grade WAP from a retail store. I set it to use SSID **BrickerRulz** and WPA2-Personal, and I give it the password **GREZveblam487WirdFallNow**.

I plug that into my network, a network that contains only the WAP (192.168.50.10/24) and a router for my ISP access (internal interface 192.168.50.1/24; external interface who cares).

Now I use my laptop to connect to wireless network BrickerRulz, and provide the password GREZveblam487WirdFallNow. I’m not even using DHCP; I statically assign 192.168.50.3/24 to my wireless card and give it a default gateway of 192.168.50.1 and tell it to use DNS servers 192.168.50.2 and 8.8.8.8.

(1) Is this setup vulnerable to the flaw discussed above? Why or why not?  
(2) Can I browse the Internet successfully?

OK, now I plug my AD domain controller for domain B4EVER into my router; it’s address is 192.168.50.2/24 and it’s running DNS services. My laptop is a member of domain B4EVER.

(3) Is **this** setup vulnerable to the flaw discussed above? Why or why not?  
(4) Can my laptop successfully authenticate to the AD domain controller?

---

<div class="post-metadata">

**Author:** ![Bricker](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@Bricker](https://boards.straightdope.com/u/Bricker)\
**Post date:** [August 7, 2013, 5:59pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/16 "2013-08-07T17:59:00Z")

</div>

> [@yoyodyne](#):
>
> If you’re talking about your home router, you have nothing to worry about. It’s only if you’re trying to log into a Windows domain via WiFi.
> 
> This is pretty good discussion: [Revolution Wi-Fi: Is WPA2 Security Broken Due to Defcon MS-CHAPv2 Cracking?](http://revolutionwifi.blogspot.com/2012/07/is-wpa2-security-broken-due-to-defcon.html)

More specifically, it’s only an issue if you’re using RADIUS authentication with an AD domain as the name service for RADIUS.

Yes?

---

<div class="post-metadata">

**Author:** ![yoyodyne](https://avatars.discourse-cdn.com/v4/letter/y/a9a28c/32.png) [@yoyodyne](https://boards.straightdope.com/u/yoyodyne)\
**Post date:** [August 7, 2013, 6:07pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/17 "2013-08-07T18:07:08Z")

</div>

> [@Bricker](#):
>
> More specifically, it’s only an issue if you’re using RADIUS authentication with an AD domain as the name service for RADIUS.
> 
> Yes?

Yes.

---

<div class="post-metadata">

**Author:** ![Bricker](https://avatars.discourse-cdn.com/v4/letter/b/977dab/32.png) [@Bricker](https://boards.straightdope.com/u/Bricker)\
**Post date:** [August 7, 2013, 6:29pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/18 "2013-08-07T18:29:18Z")

</div>

> [@yoyodyne](#):
>
> Yes.

Well, that was easier than answering questions 1-4. 🙂

---

<div class="post-metadata">

**Author:** ![yoyodyne](https://avatars.discourse-cdn.com/v4/letter/y/a9a28c/32.png) [@yoyodyne](https://boards.straightdope.com/u/yoyodyne)\
**Post date:** [August 7, 2013, 6:41pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/19 "2013-08-07T18:41:08Z")

</div>

It did answer questions 1-4. 🙂

---

<div class="post-metadata">

**Author:** ![Gagundathar](https://avatars.discourse-cdn.com/v4/letter/g/a183cd/32.png) [@Gagundathar](https://boards.straightdope.com/u/Gagundathar)\
**Post date:** [August 7, 2013, 6:43pm UTC](https://boards.straightdope.com/t/windows-phone-devices-can-be-tricked-into-revealing-wi-fi-passwords/665587/20 "2013-08-07T18:43:04Z")

</div>

Thank you, **Bricker** and \*\*Yoyodyne \*\*for making this much easier to figure out!
