An Ars story from earlier this month reported that iPhones expose the unique identifiers of recently accessed wireless routers, whichgenerated no shortage of reader outrage. What possible justification does Apple have for building this leakage capability into its entire line of wireless products when smartphones, laptops, and tablets from competitors don't? And how is it that Google, Wigle.net, and others get away with publishing the MAC addresses of millions of wireless access devices and their precise geographic location? <\/p>\n
Some readers wanted more technical detail about the exposure, which applies to three access points the devices have most recently connected to. Some went as far as to challenge the validity of security researcher Mark Wuergler's findings. \"Until I see the code running or at least a youtube I don't believe this guy has the goods,\" one Ars commenter wrote. <\/p>\n
According to penetration tester Robert Graham, the findings are legit. <\/p>\n
In the service of our readers, and to demonstrate to skeptics that the privacy leak is real, Ars approached Graham and asked him to review the article for accuracy and independently confirm or debunk Wuergler's findings. <\/p>\n
\"I can confirm all the technical details of this 'hack,'\" Graham, who is CEO of Errata Security, told Ars via e-mail. \"Apple products do indeed send out three packets that will reveal your home router MAC address. I confirmed this with my latest iPad 3.\" <\/p>\n
He provided the image at the top of this post as proof. It shows a screen from Wireshark, a popular packet-sniffing program, as his iPad connected to a public hotspot at a Starbucks in Atlanta. Milliseconds after it connected to an SSID named \"attwifi\" (as shown in the section labeled #1), the iPad broadcasted the MAC address of his Linksys home router (shown in the section labeled #2). In section #3, the iPad sent the MAC address of this router a second time, and curiously, the identifier was routed to this access point even though it's not available on the local network. As is clear in section #4, the iPad also exposed the local IP address the iPad used when accessing Graham's home router. All of this information is relatively simple to view by anyone within radio range. <\/p>\n
The image is consistent with one provided by Wuergler below. Just as Wuergler first claimed, it shows an iPhone disclosing the last three access points it has connected to. <\/p>\n
Mark Wuergler, Immunity Inc. <\/p>\n
Graham used Wireshark to monitor the same Starbucks hotspot when he connected with his Windows 7 laptop and Android-based Kindle Fire. Neither device exposed any previously connected MAC addresses. He also reviewed hundreds of other non-Apple devices as they connected to the network, and none of them exposed previously accessed addresses, either. <\/p>\n
As the data makes clear, the MAC addresses were exposed in ARP (address resolution protocol) packets immediately after Graham's iPad associated with the access point but prior to it receiving an IP address from the router's DHCP server. Both Graham and Wuergler speculate that Apple engineers intentionally built this behavior into their products as a way of speeding up the process of reconnecting to access points, particularly those in corporate environments. Rather than waiting for a DHCP server to issue an IP address, the exposure of the MAC addresses allows the devices to use the same address it was assigned last time. <\/p>\n<\/p>\n
Link: An Ars story from earlier this month reported that iPhones expose the unique identifiers of recently accessed wireless routers, whichgenerated no shortage of reader outrage. What possible justification does Apple have for building this leakage capability into its entire line of wireless products when smartphones, laptops, and tablets from competitors don't? And how is it that Google, Wigle.net, and others get away with publishing the MAC addresses of millions of wireless access devices and their precise geographic location Continue reading
\nAnatomy of a leak: how iPhones spill the ID of networks they access<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"