Attacks/Breaches
11/9/2010
01:58 PM
50%
50%

Tools Gut Firesheep Cookie Hijacking Attack

BlackSheep, FireShepherd, and HTTPS Everywhere released to block controversial Firefox plug-in.

How Firesheep Can Hijack Web Sessions
(click image for larger view)
Slideshow: How Firesheep Can Hijack Web Sessions

Scared by the recent arrival of Firesheep, a controversial plug-in for Firefox that allows attackers to hijack your web sessions? The cookie-stealing tool, downloaded at least 600,000 times to date, works against users of a number of Web 2.0 websites, including Facebook, Twitter, and Flickr.

Now, however, free tools are appearing to help users defend themselves.

On Monday, SaaS security firm Zscaler released BlackSheep, a free Firesheep countermeasure. (As with Firesheep, Windows users must first install Winpcap.) BlackSheep works by making HTTP requests using fake variables to the websites watched by Firesheep. BlackSheep then detects and blocks Firesheep clients at work on the local network when they attempt to reuse the fake variables.

Meanwhile, Gunnar Atli Sigurdsson, a 21-year-old engineering students at the University of Iceland, released FireShepherd for Windows, "a small console program that floods the nearby wireless network with packets designed to turn off Firesheep." The tool has the added benefit of blocking Firesheep for anyone else using the same Wi-Fi connection.

Another workaround is HTTPS Everywhere, from the Tor Project and Electronic Freedom Foundation, which forces websites to SSL-encrypt every page. The only caveat is that websites must offer HTTPS.

Countermeasures aside, controversy continues to rage over whether Firesheep itself is good or bad. The goal of releasing it, according to its creator, Eric Butler, was to expose the lack of security inherent to using unencrypted Wi-Fi networks.

"Facebook is constantly rolling out new 'privacy' features in an endless attempt to quell the screams of unhappy users, but what's the point when someone can just take over an account entirely?" said Butler. Indeed, the necessary packet-sniffing tools, including free utilities such as NetStumbler and Kismet, have been available for years -- and Firesheep blockers won't even detect them.

Accordingly is it "mission accomplished" for publicizing Wi-Fi insecurity? "People have been living under the impression that capturing a session by stealing a cookie can only be done by skilled hackers with special tools. This has now changed," said F-Secure's chief research officer, Mikko Hypponen.

"What can users do right now? Force SSL on if you can. Don't use Wi-Fis without encryption. Or, use a VPN," said Hypponen. "If you have a VPN, always turn it on when you are on a hotspot, even if you're not 'working' but just surfing Facebook. All good VPN products will encrypt all of the traffic, even to Facebook."

Why not simply SSL-enable for Facebook, Twitter, and everything else under the sun? Many sites do use SSL, but only for encrypting logon information. With the exception of Gmail, few use SSL for the entire session.

Previously, using SSL took a bite out of performance. But today, said Google software engineer Adam Langley, "SSL/TLS is not computationally expensive anymore." In other words, "you too can afford to enable HTTPS for your users."

According to statements made by Facebook and Twitter, they're working on it.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-6090
Published: 2015-04-27
Multiple cross-site request forgery (CSRF) vulnerabilities in the (1) DataMappingEditorCommands, (2) DatastoreEditorCommands, and (3) IEGEditorCommands servlets in IBM Curam Social Program Management (SPM) 5.2 SP6 before EP6, 6.0 SP2 before EP26, 6.0.3 before 6.0.3.0 iFix8, 6.0.4 before 6.0.4.5 iFix...

CVE-2014-6092
Published: 2015-04-27
IBM Curam Social Program Management (SPM) 5.2 before SP6 EP6, 6.0 SP2 before EP26, 6.0.4 before 6.0.4.6, and 6.0.5 before 6.0.5.6 requires failed-login handling for web-service accounts to have the same lockout policy as for standard user accounts, which makes it easier for remote attackers to cause...

CVE-2015-0113
Published: 2015-04-27
The Jazz help system in IBM Rational Collaborative Lifecycle Management 4.0 through 5.0.2, Rational Quality Manager 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Team Concert 4.0 through 4.0.7 and 5.0 through 5.0.2, Rational Requirements Composer 4.0 through 4.0.7, Rational DOORS Next Generation...

CVE-2015-0174
Published: 2015-04-27
The SNMP implementation in IBM WebSphere Application Server (WAS) 8.5 before 8.5.5.5 does not properly handle configuration data, which allows remote authenticated users to obtain sensitive information via unspecified vectors.

CVE-2015-0175
Published: 2015-04-27
IBM WebSphere Application Server (WAS) 8.5 Liberty Profile before 8.5.5.5 does not properly implement authData elements, which allows remote authenticated users to gain privileges via unspecified vectors.

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.