The MobileMe saga continues. The lack of SSL among the web applications, including email, calendars, contacts and everything in between, has caused panic among subscribers of the service. MobileMe uses the standard ‘http:’ protocol, as opposed to the more secure ‘https:’ that Gmail offers as an option. What does this mean and how does it affect you?
AppleInsider’s McLean went about analysing the web apps and made a big blunder in his article stating that SSL is not required and Mobileme is actually secure. Looking at the evidence provided, I will agree with Jeff Alfke’s comment, that McLean either isn’t very knowledgeable about data security and the importance of SSL or his system of email access is totally insecure.
Data transaction security in MobileMe’s web apps is based upon authenticated handling of JSON data exchanges between the self contained JavaScript client apps and Apple’s cloud, rather than the SSL web page encryption used by HTTPS.
This means that your emails and calendars will show up in your inbox only if you have gone through the authentication in the beginning. But, on digging a little deeper, it appears that anyone can read your email once you’ve logged in.
The only real web pages MobileMe exchanges with the server are the HTML, JavaScript, and CSS files that make up the application, which have no need for SSL encryption following the initial user authentication.
The web apps themselves are not authenticated and only the data that is transferred is authenticated. Note the use of the word authenticated instead of encrypted. Several bloggers have proved that using simple network sniffers like WireShark or tcpdump, the plaintext of the entire message, the calendar events and your contacts can easily be pilfered! So some hacker jack sitting across the room sharing your Wi-Fi network could take a sneek peek into your online life if he’s so inclined.
Another problem with the lack of SSL is that if your router is infected—with the DNS for me.com pointing to some phishing site, for example—there is absolutely no way for you, the user, to know the difference. Firefox will not show the yellow address bar and Safari won’t show the lock icon. So using something like a man-in-the-middle attack, the web app would be authenticated by the user and the hacked app would then act as an intermediary between your web app and the Apple servers.
An important point to note, however, is that this only pertains to the web apps. The IMAP support on the iPhone and desktop clients all transfer data over SSL so no one’s looking at that data.
Moral of the story: If you really care about data security and are secretly an undercover agent for the CID, stop using the web apps for a while, at least on an unsecured Wi-Fi network. If, on the other hand, you are like me and not overly (or even remotely, for that matter) paranoid about the security of your inbox (and usually leave the ‘Keep me logged in’ box checked), then continue using the web interface in all its Web 2.0 glory.