Your health, tax, and search data siphoned
Software-as-a-service springs SSL leak
Regcast training : Hyper-V 3.0, VM high availability and disaster recovery
Google, Yahoo, Microsoft's Bing, and other leading websites are leaking medical histories, family income, search queries, and massive amounts of other sensitive data that can be intercepted even when encrypted, computer scientists revealed in a new research paper.
Researchers from Indiana University and Microsoft itself were able to infer the sensitive data by analyzing the distinct size and other attributes of each exchange between a user and the website she was interacting with. Using man-in-the-middle attacks, they could glean the information even when transactions were encrypted using the Secure Sockets Layer, or SSL, protocol or the WPA, or Wi-fi Protected Access protocol.
"Our research shows that surprisingly detailed sensitive user data can be reliably inferred from the web traffic of a number of high-profile, top-of-the-line web applications" offered by Google, Yahoo, and Bing as well as the leading online providers of tax, health and investments services, which the researchers didn't name.
"An eavesdropper can infer the medications/surgeries/illnesses of the user, her annual family income and investment choices and money allocations, even though the web traffic is protected by HTTPS. We also show that even in a corporate building that deploys the up-to-date WPA/WPA2 wi-fi encryptions, a stranger without any credential can sit outside the building to glean the query words entered into employees' laptops, as if they were exposed in plain text in the air."
The paper showed how they were able to deduce the doctor and medical condition of a person who had entered the information into a site operated by "one of the most reputable companies of online services," which runs exclusively over an HTTPS channel. In the case of medical conditions, the details were leaked through the site's auto-suggestion feature, which updates potential entries in response to each keystroke.
The researchers discovered they could "disambiguate" the input by matching each keystroke to the size of the response in the suggestion list. Selections from the site's "Find a Doctor" service were inferred by using the user's IP address to guess her geographic location and then analyzing the packets as they flowed back and forth.
The researchers employed similar techniques to a user of an online tax-preparation application that asks simple questions and tailors future queries based on the answers. By scrutinizing the encrypted responses, they were able to determine the site was asking questions concerning student loan interest deductions, which applied only to tax payers who earned less than $145,000.
By compiling a list of the responses concerning other deductions, it was possible to accurately infer a user's annual income, the researchers said.
They also showed how the auto-suggestion features in Google, Yahoo!, and Bing can leak the search terms users enter, even when traffic is encrypted over WPA. That's because the resulting packets are easy to identify by their "web flow vectors."
The threat is significant because it stems from fundamental characteristics of software-as-a-service applications that have been in vogue for about a decade. Among other things, apps built on AJAX and other Web 2.0 technologies are usually "stateful," meaning they keep track of unique configuration information. Such data often has "low entropy," making it easy for attackers to make educated guesses about its contents.
While a variety of mitigations are available to prevent such attacks, the researchers warn they could come at a high cost. The most obvious solution is to "pad" responses with superfluous data that confuses attackers trying to make sense of the traffic. But the researchers showed the mitigation isn't always effective and they also point out that it adds a considerable amount of traffic to each transaction, which in turn drives up the costs of operation.
"Effective and efficient mitigations have to be application-specific: developers will need to identify the vulnerabilities first, and then specify mitigation policies accordingly," the researchers wrote. "This effort requires analysis of web application semantics, information flow and network traffic patterns."
The scientists are Shuo Chen of Microsoft Research; and Rui Wang, XiaoFeng Wang, and Kehuan Zhang of Indiana University at Bloomington's School of Informatics and Computing. A PDF of the paper is here. Princeton University computer science professor and Freedom to Tinker blogger Ed Felton has additional analysis here. ®
COMMENTS
So they are saying
1) Wi-fi is insecure..
2) Most Web masters deploy monkey level security for their SSL (more likely their managers MAKE them do it)
3) Web security is HARD man! (insert crying here)
I want to get paid to produce these common sense level reports. I am sure this is stuff that has been said over and over by the people on the front line, but requires a freaking consultant paid at millions before they will listen.
I say we sic the badgers on them !
Nice work
"They also showed how the auto-suggestion features in Google, Yahoo!, and Bing can leak the search terms users enter, even when traffic is encrypted over WPA. That's because the resulting packets are easy to identify by their 'web flow vectors.' [...] The most obvious solution is to 'pad' responses with superfluous data that confuses attackers trying to make sense of the traffic."
Um, no. The most obvious solution is to stop auto-suggesting, at least from the server end. You could presumably continue to auto-suggest on the client, so the end-user might not even notice that the facility had disappeared. Even if they did, it's hardly the end of the world to have to type stuff out in full.
Still, this is an unexpected leak, at least to me and probably also to the people who wrote these applications. Just as well independent security research isn't illegal, eh?
The sky is not falling - no surprise here!
As Michael points out -- no surprise that there are weaknesses in Web applications to conjecture information despite the fact that encryption is in place. We find quite typical here at VeriSign and some of the described attacks also require a man-in-the-middle attack (MITM) to be performed first. Extended Validation SSL Certificates can go a long way in defeating the effectiveness of MITM attacks by reliably identifying that the user is connected directly to the desired site and not by way of a malicious MITM proxy seeking to steal information.

IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
Steps to Take Before Choosing a Business Continuity Partner
Requirements Checklist for Choosing a Cloud Backup and Recovery Service Provider