Perimeter
Guest Blog // Selected Security Content Provided By Sophos
What's This?
10/26/2010
02:35 PM
Dark Reading
Dark Reading
Security Insights
50%
50%

Cookies, Social Media And FireSheep

We've been seeing a lot of interest in FireSheep, the FireFox add-on that lets you spy on websites. How bad is it really?

We've been seeing a lot of interest in FireSheep, the FireFox add-on that lets you spy on websites. How bad is it really?To back the train up, let me explain what the add-in actually does for the benefit of the not-so-technical reader. When you go to a coffee shop or anywhere that has public WiFi, you share that connection with every other person using it. So the traffic all goes out over the same IP address. If a patron logs into most websites, then he or she will get a session ID and a cookie. If one can spy on the contents of that cookie, then the "hacker" can use that ID and the additional info to send traffic as that patron. Yes, usernames and passwords are encrypted on login with https and/or SSL, but then most sites switch back to plain, old unencrypted HTTP. This is generally seen as a VERY BAD THING if you are a privacy advocate.

Now none of this is new, different, or original. There have been sniffing techniques as long as there have been cookies. However, a well-meaning researcher by the name of Eric Butler has changed the game by making this technique extremely simple and accessible to the average person. Now I get what his aim was: He tried to show how insecure websites are. We security folks have been banging the drum on this for ages. I'm hoping sites like Facebook and Twitter will take notice. But will they?

Putting aside the security hat for a moment, let's look at these sites. Social networking sites have a business plan. That plan is to connect people and get them to share ideas, content, photos, etc., as freely as possible. Security and privacy simply are not at the top of the business plan. They now have to skate the line of trying to satisfy security experts and privacy advocates, while still holding to their business plan of allowing the sharing of information. Now does that mean personally identifiable info (PII) should be on display? Not really, but you willingly provide that information when you sign up for these sites (unless you give false information). These sites have a responsibility to protect your PII, but you have the choice of whether to provide it in the first place. Now that said (security hat goes back on), social networks most certainly DO have an obligation to ensure the person logged into the account really is that person and not someone masquerading as him or her. And, yes, they do need to start securing the whole session and not just the logging in portion of the session.

On a side note, someone asked us at Sophos if we think Firefox should start vetting add-ins to prevent them from ever being downloaded. Should they? Probably. Can they? That's a question I can't answer. Being an open community means there is such great range of innovation and tools to help, but at the same time that means any bad guy can easily get in and spoil things.

Beth Jones is a Senior Threat Researcher in SophosLabs North America. She manages the day-to-day research and analysis activities of incoming suspicious malware threats and potentially unwanted applications that arrive in the Lab via Sophos customers, partners, and prospects.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-4807
Published: 2014-11-22
Sterling Order Management in IBM Sterling Selling and Fulfillment Suite 9.3.0 before FP8 allows remote authenticated users to cause a denial of service (CPU consumption) via a '\0' character.

CVE-2014-6183
Published: 2014-11-22
IBM Security Network Protection 5.1 before 5.1.0.0 FP13, 5.1.1 before 5.1.1.0 FP8, 5.1.2 before 5.1.2.0 FP9, 5.1.2.1 before FP5, 5.2 before 5.2.0.0 FP5, and 5.3 before 5.3.0.0 FP1 on XGS devices allows remote authenticated users to execute arbitrary commands via unspecified vectors.

CVE-2014-8626
Published: 2014-11-22
Stack-based buffer overflow in the date_from_ISO8601 function in ext/xmlrpc/libxmlrpc/xmlrpc.c in PHP before 5.2.7 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code by including a timezone field in a date, leading to improper XML-RPC encoding...

CVE-2014-8710
Published: 2014-11-22
The decompress_sigcomp_message function in epan/sigcomp-udvm.c in the SigComp UDVM dissector in Wireshark 1.10.x before 1.10.11 allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted packet.

CVE-2014-8711
Published: 2014-11-22
Multiple integer overflows in epan/dissectors/packet-amqp.c in the AMQP dissector in Wireshark 1.10.x before 1.10.11 and 1.12.x before 1.12.2 allow remote attackers to cause a denial of service (application crash) via a crafted amqp_0_10 PDU in a packet.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?