Vulnerabilities / Threats
5/24/2011
01:37 PM
50%
50%

LinkedIn Faces Cookie Vulnerabilities

The social networking site is set to reduce the length of time before cookies expire and add HTTPS across its site.

How Firesheep Can Hijack Web Sessions
(click image for larger view)
Slideshow: How Firesheep Can Hijack WebSessions
LinkedIn users' accounts are vulnerable to hijacking, due to the manner in which the social networking site handles its website cookies.

That security warning comes from Rishi Narang, a security consultant at website scanning firm Hackers Locked, who published an analysis of the vulnerability on Saturday.

LinkedIn is much in the news lately, owing to its initial public offering on Thursday, which by the close of the day resulted in the company being valued at $8.9 billion. But is the company paying enough attention to the security of its users?

LinkedIn, like many websites, uses cookies to store, on a PC, session information relating to anyone who uses that PC to access LinkedIn. Such cookies make it easy for users to later access LinkedIn without having to enter a username or password. But according to Narang, LinkedIn needs to handle its cookies better.

All told, there are two cookie-related vulnerabilities, he said. The first stems from LinkedIn SSL cookies not using a secure flag, which means that session credentials are sent in plaintext. As a result, they're susceptible to a man-in-the-middle attack, which could intercept these credentials. Such an attack could be launched from a third-party website by remotely redirecting a user to the HTTPS log-in page for LinkedIn, and watching the relevant credentials being passed back and forth.

A fix, however, is relatively simple: LinkedIn should use the secure flag on any cookies that are used with an HTTPS page, such as the log-in page, said Narang. "If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic," he said. "If the secure flag is not set, then the cookie will be transmitted in clear text if the user visits any HTTP URLs within the cookie's scope." Another security improvement would be for LinkedIn to restrict credentials to a specific IP address, as Gmail does. That way, if an attacker stole a credential and attempted to use it from another PC, it wouldn't work.

The second vulnerability, he said, is due to LinkedIn setting its cookies to not expire for one year--an eternity, in website time--and not canceling cookies if a user logs out. "As a result of valid cookies, an attacker can sniff the cookies from [a] clear-text session," as detailed with the prior vulnerability, said Narang. With cookies in hand, an attacker could then authenticate as the other user. "He can then compromise and modify the information available at the user profile page," he said.

Accordingly, this vulnerability rates largely as a nuisance, since LinkedIn doesn't store people's financial information. On the other hand, in the wrong hands, a LinkedIn account hijacking or defacement could be quite embarrassing. Furthermore, intercepting people's LinkedIn credentials is relatively easy--if they're using an unsecured, public Wi-Fi hotspot--by using a tool such as Firesheep.

LinkedIn said it's working on related improvements, but in the short term, recommended users avoid unsecured networks. "Whether you are on LinkedIn or any other site, it's always a good idea to choose trusted and encrypted Wi-Fi networks or VPNs whenever possible," said a LinkedIn spokesperson via email. "If one isn't available, we already support SSL for logins and other sensitive Web pages."

Going forward, he said, LinkedIn plans to support SSL--as in, HTTPS pages--across the entire site. As with Facebook, users will need to opt in. Furthermore, "we are going to reduce the lifespan of the cookies in question from 12 months to 90 days," said the spokesperson.

"LinkedIn takes the privacy and security of our members seriously, while also looking to deliver a great site experience, and we believe these two changes will allow us to strike that balance," he said.

In this new Tech Center report, we profile five database breaches--and extract the lessons to be learned from each. Plus: A rundown of six technologies to reduce your risk. Download it here (registration required).

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-1750
Published: 2015-07-01
Open redirect vulnerability in nokia-mapsplaces.php in the Nokia Maps & Places plugin 1.6.6 for WordPress allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the href parameter to page/place.html. NOTE: this was originally reported as cross-sit...

CVE-2014-1836
Published: 2015-07-01
Absolute path traversal vulnerability in htdocs/libraries/image-editor/image-edit.php in ImpressCMS before 1.3.6 allows remote attackers to delete arbitrary files via a full pathname in the image_path parameter in a cancel action.

CVE-2015-0848
Published: 2015-07-01
Heap-based buffer overflow in libwmf 0.2.8.4 allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted BMP image.

CVE-2015-1330
Published: 2015-07-01
unattended-upgrades before 0.86.1 does not properly authenticate packages when the (1) force-confold or (2) force-confnew dpkg options are enabled in the DPkg::Options::* apt configuration, which allows remote man-in-the-middle attackers to upload and execute arbitrary packages via unspecified vecto...

CVE-2015-1950
Published: 2015-07-01
IBM PowerVC Standard Edition 1.2.2.1 through 1.2.2.2 does not require authentication for access to the Python interpreter with nova credentials, which allows KVM guest OS users to discover certain PowerVC credentials and bypass intended access restrictions via unspecified Python code.

Dark Reading Radio
Archived Dark Reading Radio
Marc Spitler, co-author of the Verizon DBIR will share some of the lesser-known but most intriguing tidbits from the massive report