Perimeter
6/11/2012
03:57 PM
Amy DeCarlo
Amy DeCarlo
Commentary
Connect Directly
RSS
E-Mail
50%
50%

LinkedIn: Making Insecure Connections

The recent breach of millions of LinkedIn passwords highlights an all-too-common issue

We spend a considerable amount of time in the security industry talking about sophisticated security protections and innovative practices that can be applied to protect critical information. Biometrics, cryptography, secure tokens, and a variety of other technologies can go a long way toward assuring organizations their data is safe. Yet for all the emphasis on innovations in security and safeguarding the highest value data, too often the basics are left uncovered.

The breach of a reported 6.5 million LinkedIn passwords last week is a prime example of what at least initially appears to be a failure at three levels: in policy, in practice, and in communication.

LinkedIn, which doesn’t have a chief information officer, much less a chief information security officer, clearly applied what appears to be a substandard policy to securing passwords of users, many of which may be high-value targets in and of themselves given the power and influence of many of the professionals associated with those access codes. The breach, which was discovered when the passwords showed up on a Russian hacking forum last week, exposed whatever cryptographic controls the social business network used to secure the passwords was far too simplistic.

Communications from LinkedIn about the breach were also unclear. In a blog post written by Vicente Silveira, a director at the company, LinkedIn admitted that “a small subset of the hashed passwords was decoded and published.” It wasn’t able to quantify how many. While the company is investigating the incident, the company’s ambiguity about the breach -- or apparent security expertise or leadership -- is hardly a confidence-inducing move. In the meantime, LinkedIn cancelled the passwords it believed were “at the greatest risk.” Also in a somewhat confusing move, the company says it “is disabling the passwords of any other members that we believe could potentially be affected.”

LinkedIn dug a deeper hole for itself by admitting that it isn’t sure whether any other data was compromised. Nor apparently does the company seem to understand that just because the hackers haven’t apparently been able to crack the cryptographic code for all the passwords that they won’t be able to do so eventually. After all, they have the most important element in their possession already: the passwords themselves.

Most data breaches like the one that befell LinkedIn are too commonplace to make headlines. What distinguished this from the run-of-the-mill password hack attack was the target. Essentially, the breach revealed surprisingly poorly executed security controls by a company that until now has been trusted by millions of professionals to keep them connected.

If anything positive comes of the incident, it is that it serves a reminder to everyone about the importance of being vigilant about managing their own passwords well. Simple tips like resetting passwords frequently and not reusing passwords can go a long way toward protecting their data, and with it, their identities.

Amy DeCarlo is principal analyst for security and data center services at Current Analysis

Amy brings 17 years of IT industry experience to her position as Principal Analyst, Security and Data Center Services. Amy assesses the managed IT services sector, with an emphasis on security and data center solutions delivered through the cloud including on demand ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
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-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.